For agents
Every machine-readable description of this service, in one place. If you are a person setting up a client, the MCP page has the configuration to paste instead.
Fetch one of these
- OpenAPI 3.1 https://api.docufinery.com/openapi.json
- Every endpoint, parameter, response and error code. The authoritative contract.
- MCP endpoint https://api.docufinery.com/mcp
- Streamable HTTP transport. Nine tools, each stating its price in its description. Every result carries credits_used.
- llms.txt /llms.txt
- Short index: what this is, what a pack costs, what each operation costs.
- llms-full.txt /llms-full.txt
- Everything in one fetch, including all ten products with their endpoints.
- Facts https://api.docufinery.com/facts
- The same claims and prices as prose plus JSON-LD, for quoting in an answer.
- Postman collection https://api.docufinery.com/postman/collection.json
- Importable, with one variable to set.
- Sitemap /sitemap.xml
- Every page on this origin.
What it costs, before you call
Credits are bought once and never expire. There is no subscription and no feature gating: packs differ only in volume, from $4.99 upward. A new account gets 25 credits with no card.
Every operation publishes its price before you spend anything. Credits are held before the work and settled after it, a failure refunds in full and automatically, and the two operations whose cost depends on the file — parsing and table extraction — classify it and tell you the price before charging. Full table on the pricing page.
Authentication and limits
Send X-API-Key on every request; the MCP endpoint also accepts Authorization: Bearer. Rate limits are per key, not per account, so one runaway loop cannot starve another workload. Limits are published in llms.txt and enforced at exactly those numbers.
Errors have a stable shape: {"error": {"code": "...", "message": "..."}}. Branch on code, never on the HTTP status or the message text.
On /.well-known
There is no ratified /.well-known convention for MCP servers or for llms.txt, so this site does not invent one. A path that looks standard and is not produces a URL nobody fetches and a false impression that something was published.
llms.txt lives at the root of each origin, which is what llmstxt.org specifies. The MCP endpoint is advertised here and on the MCP page. Where a real convention exists — security.txt, RFC 9116 — it is served once there is a contact address to put in it, which is an open decision rather than an oversight.