# Invofox > Invofox is a hosted API that extracts structured, validated JSON from PDFs and images such as invoices, payslips, bank statements and custom document types, with a classifier and a splitter. Results arrive by webhook or polling. - Canonical: https://www.anchorterminal.com/tools/invofox - Markdown: https://www.anchorterminal.com/tools/invofox.md (~6,900 tokens) - Slim: https://www.anchorterminal.com/tools/invofox.min.md (~1,680 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/invofox.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-08 ## Overview **Grade D · 46.8/100 · rank #557 of 629 · #10 in Document parsing & extraction · not agent-ready · confidence medium** ## Assessment Three public OpenAPI 3.1 files, llms.txt and Markdown docs describe an asynchronous upload and webhook flow, and the free plan covers 500 pages without a card. No status page, rate limit numbers, changelog or official SDK were found, and documents are retained by default, with zero retention limited to Scale and Enterprise. ## Facts | Field | Value | | --- | --- | | Vendor | Invofox, Inc. (https://www.invofox.com) | | Kind | HTTP API | | Category | Document parsing & extraction (https://www.anchorterminal.com/categories/document-extraction) | | Transport | HTTP | | Endpoint | `https://api.invofox.com` | | Auth | API key · API key in an `x-api-key` header, created by a person under API and Webhooks in the dashboard at app.invofox.com after a self-serve sign-up. Each key is scoped to one environment, which is configured as TEST or PRODUCTION. The ingest OpenAPI file also defines an `x-access-token` header for browser sessions. No OAuth, and no scoped or read-only keys were found. Webhooks can be signed with HMAC, sent in an `x-invofox-signature` header. | | Pricing | Freemium ($500 / mo) · Free plan of 500 pages with REST API access, self-serve sign-up and no card. Starter is from $500 a month billed annually for up to 5,000 pages a month, with email support and a stated 99.9% uptime SLA. Scale and Enterprise are custom. Billing is per page, with no per-page or overage rate published. The YC launch post of 5 October 2026 mentions 1,500 free pages for new users, which the pricing page does not show (https://www.invofox.com/en/pricing.md, checked 2026-10-08). | | x402 | No · No x402, MPP or L402 in the docs, the three OpenAPI files or the pricing page (checked 2026-10-08). | | Licence | Proprietary hosted service. The n8n community node on GitHub is MIT | | Docs | https://developers.invofox.com/documentation/start-here | | llms.txt | https://developers.invofox.com/llms.txt | | Last release | 2026-10-05 | | Free tier | 500 pages, REST API access, no card | | Plan with API access | All plans, including Free | | API | REST at https://api.invofox.com. Main reference with 25 operations (documents, companies, providers, clients, users), ingest with 7 under /v1/ingest, and seven webhook events, all OpenAPI 3.1 | | Flow | Asynchronous. POST /v1/ingest/uploads (multipart) or /v1/ingest/by-url, then the `document.processed` webhook or polling GET /documents/{id} | | Document types | Pre-trained types named on the site include invoices, receipts, utility bills, payslips, purchase orders, bank statements and tax forms, plus custom types. The type id or alias comes from the dashboard, or `useClassifier` detects it | | Splitter | `useSplitter` returns one document per logical document in a PDF. Each file in a ZIP archive is processed as its own document | | Page references | A `geometry` object gives a page index and an eight-coordinate box per field. GET /documents/{id}/ocr returns lines and words, and /text returns plain text | | File types | PDF, JPEG, PNG, TIFF and ZIP, up to 100 MB a file per the ingest reference | | Rate limits | No numbers published. 429 responses carry RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After | | Webhooks | document.created, processed, approved and discarded, file.processed and rejected, import.processed. Optional HMAC signature, 30-second timeout, up to three retries | | MCP server | Documentation search only, one `searchDocs` tool at https://developers.invofox.com/_mcp/server. None for document processing | | SDKs | None official found. An n8n community node, n8n-nodes-invofox 0.1.0 (3 July 2026, MIT), and a Zapier integration | | Data retention | Documents retained by default, period not stated. Zero retention is opt-in on Scale and Enterprise. The DPA allows three months of access after termination | | Deployment | Hosted, with EU or US regions stated. On-premises for Enterprise | | Certifications | SOC 2 Type II, ISO 27001:2022, GDPR and HIPAA compliance stated on the site. Trust centre on Vanta at trust.invofox.com | | Capabilities | docs.extract, docs.ocr, docs.classify | | Tags | hosted, freemium, no-card, openapi, llms-txt, webhooks, async-jobs, api-key, closed-source, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/invofox.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-08 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 30 | 6.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 70 | 11.4 | | Agent ergonomics | 13% | 16.2 | 64 | 10.4 | | Security & auth | 14% | 17.5 | 45 | 7.9 | | Payments & pricing | 10% | 12.5 | 30 | 3.8 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 30 | 2.6 | | Transparency & trust (editorial 40, provenance 69) | 7% | 8.8 | 55 | 4.8 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **46.8 → D** | ### Why each score - Reliability 30: No public status page found. status.invofox.com does not resolve and neither the site nor the docs link to one (0 of 20). No readable incident history (5 of 30). No rate limit numbers, and the vendor's AI briefing says rate limits are not publicly documented (0 of 15). The main OpenAPI file documents 429 with RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After headers, and the docs ask for exponential backoff, but uploads take no idempotency key (10 of 15). The pricing page lists a 99.9% uptime SLA on Starter with no SLA document found (5 of 10). The API is in production use and self-serve since 5 October 2026 (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 70: Three public OpenAPI 3.1 files, main (25 operations), ingest (7) and webhooks (7 events) (25). llms.txt on both the site and the docs, and every docs page has a Markdown twin (10). The guides say when to use webhooks or polling and how rejected files behave, but 11 of the 25 main operations have no description (12 of 20). States, confidence and error codes are enums and `limit` has a maximum of 500, while `info` is a JSON string inside multipart and `filter` is a JSON string in the query (9 of 15). Examples in curl, Python and Node.js and tables of error codes, with inconsistencies. A sample shows ERR_PASSWORD_PROTECTED, which is missing from the code table, the main file's error text says 50 MB and 10 pages where the ingest file says 100 MB, and webhook samples show version 1.0 and 1.2 (9 of 15). Ingest paths carry /v1 and webhook events a version field, and no public changelog was found (5 of 15). - Agent ergonomics 64: The document list accepts `select` with dot-notation field paths, and OCR geometry and plain text sit on separate endpoints, so responses can be kept small (20 of 25). `skip`, `limit` up to 500 (default 50), `sort` and a `filter` with seven operators, including on `clientData` (18 of 20). ERR_ codes for request errors, file rejections and field validation, though several error schemas hold only a `code` string (14 of 20). No idempotency key on uploads. `clientData` carries a caller id, webhook events have an `id` for deduplication, and delivery retries up to three times (6 of 20). An upload needs a file and a Document Type id that comes from the dashboard, or the classifier flag. No official SDK was found, and the testdrive repository describes one as coming soon (6 of 15). - Security & auth 45: API keys in an `x-api-key` header, created in the dashboard and scoped to one environment, which is either TEST or PRODUCTION. Revocation and rotation are not described in the docs we read (20 of 30). Environment scoping is the only least-privilege control found. The same key reaches the delete endpoints for users, companies, providers and clients, with no read-only key or confirmation (6 of 20). The API returns text taken from untrusted documents and no prompt-injection guidance was found (0 of 15). Document and import lists record channel and creator, and no audit log is documented (5 of 15). security.txt is valid until 1 June 2027 with security@invofox.com. The site states SOC 2 Type II, ISO 27001:2022, GDPR and HIPAA compliance and links a Vanta trust centre we could not read without JavaScript. No bug bounty found (14 of 20). - Payments & pricing 30: No x402, MPP or L402 (0). Plan prices are public, Free at $0 for 500 pages and Starter from $500 a month billed annually for up to 5,000 pages, but no per-page or overage rate is published and Scale and Enterprise are custom (10 of 20). The free plan needs no card (20). A person signs up in a browser at app.invofox.com and creates the key in the dashboard (0). - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 30: No changelog or versioned release was found. The dated signals are the self-serve launch on 5 October 2026 and a docs sitemap last modified on 7 October 2026, which we score as 20 of 30, our call for a recent change with no release record. No three dated releases in the last 90 days (0). Community support on Free and email support on Starter, replies not sampled, no public changelog (3 of 15). No official SDK. The vendor's only package is the n8n community node n8n-nodes-invofox 0.1.0 of 3 July 2026 (3 of 15). That repository has CI and publish workflows (4 of 10). - Transparency & trust 55: Closed service. The published terms are a website legal notice, and the General Terms and Conditions that the DPA cites were not found on the site. The DPA and NDA are public (12 of 30). The zero-retention page says the standard pipeline keeps documents and that real documents tune the model, with no default retention period stated. Zero retention is opt-in for Scale and Enterprise. The DPA allows three months of access after termination and gives 48 hours for breach notice (15 of 30). Five operations and several fields are marked deprecated in the OpenAPI files with replacements named and no removal dates (5 of 20). The DPA points to a sub-processor list in the trust centre, which we could not read, with 15 days' notice of changes. The site states EU and US processing regions (8 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (20 items): https://www.anchorterminal.com/fixes/invofox.md (JSON https://www.anchorterminal.com/fixes/invofox.json) ### What we couldn't check - unchecked: the trust centre at trust.invofox.com renders only with JavaScript, so the sub-processor list, certificates and any status link there were not read - unchecked: no account was opened and no API call was made with a key. An unauthenticated GET https://api.invofox.com/documents returned 401 with code ERR_CREDENTIALS_REQUIRED - The General Terms and Conditions cited by the DPA (clauses 10.4 and 13.2) were not found on the public site, so the terms on using customer data for the vendor's own purposes are unread - The YC launch post of 5 October 2026 says new users get 1,500 free pages for the launch. The pricing page and its Markdown twin say 500 - The site describes a Document Parsing API that returns Markdown with the same auth and upload. No such endpoint is in the three OpenAPI files, so `docs.parse` is left out of the capabilities - Data and ID verification is marketed, and no verification endpoint is in the API reference, so no `kyc` capability is listed - Whether an API key can be revoked or rotated, and whether a status page exists under another host, was not established - The integration guide says custom Document Types are defined by contacting support, while the launch post says users can define what to extract themselves ### Sources - site llms.txt: (seen 2026-10-08) - pricing (Markdown, last updated 2026-08-05): (seen 2026-10-08) - pricing page: (seen 2026-10-08) - docs llms.txt: (seen 2026-10-08) - integration guide: (seen 2026-10-08) - AI agent page, docs MCP server and product briefing: (seen 2026-10-08) - OpenAPI, main: (seen 2026-10-08) - OpenAPI, ingest: (seen 2026-10-08) - OpenAPI, webhooks: (seen 2026-10-08) - webhook implementation: (seen 2026-10-08) - information retrieval, errors and polling: (seen 2026-10-08) - rejected files and error codes: (seen 2026-10-08) - classifier: (seen 2026-10-08) - glossary, environments, keys and roles: (seen 2026-10-08) - docs sitemap with last-modified dates: (seen 2026-10-08) - zero-retention page: (seen 2026-10-08) - secure processing page: (seen 2026-10-08) - service agreements, DPA and NDA: (seen 2026-10-08) - legal notice, privacy and cookies: (seen 2026-10-08) - security.txt: (seen 2026-10-08) - trust centre (JavaScript only, not read): (seen 2026-10-08) - YC launch post, 5 October 2026: (seen 2026-10-08) - YC company page: (seen 2026-10-08) - n8n community node repository: (seen 2026-10-08) - testdrive sample repository: (seen 2026-10-08) - RDAP for invofox.com: (seen 2026-10-08) ## Who's behind it (provenance 69/100, checked 2026-10-08) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Invofox, Inc. (Delaware), with a registered branch in Spain | 20/20 | | Domain age | invofox.com, registered 2021-05-10 (5 years) | 11/15 | | Endpoint on the vendor's domain | api.invofox.com | 15/15 | | Terms of service | read, states 1 of the 7 things a reader expects | 4.9/10 | | Privacy policy | read, states 6 of the 8 things a reader expects | 8.5/10 | | Status page | not found | 0/10 | | Changelog | not found | 0/10 | | security.txt | valid | 10/10 | The DPA names INVOFOX, Inc., registered with the Delaware Division of Corporations under number 7218056, 251 Little Falls Drive, Wilmington, DE 19808. The legal notice names INVOFOX INC, BRANCH IN SPAIN, C/ Aranjuez 2, 28039 Madrid, tax ID W0265699I. The terms link is a website legal notice. The General Terms and Conditions for the platform, which the DPA cites, were not found on the public site. www.invofox.com/.well-known/security.txt gives security@invofox.com and expires on 1 June 2027. The apex invofox.com returns 404 for the same path. status.invofox.com does not resolve, and no status page or changelog is linked from the site or the docs. RDAP for invofox.com gives a registration date of 2021-05-10. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.invofox.com/en/legal/#terms), read 2026-10-08, gives no date, states 1 of the 7 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Names the governing law or courts. - Not found in the text. States a limit on its liability. - Not found in the text. Says how the agreement or account can be ended. - Not found in the text. Says how changes to the terms are announced. - Not found in the text. Lists what users may not do. **Privacy policy** (https://www.invofox.com/en/legal/), read 2026-10-08, gives no date, states 6 of the 8 things a reader expects. - Not found in the text. Gives the date it was last updated. - Not found in the text. Says what personal data is collected. - Says whether personal data is sold or shared for advertising. Says it does not sell personal data. - Gives a privacy contact. Names a data protection officer. - Says where data is transferred or stored. Relies on standard contractual clauses and the Data Privacy Framework. ## Live (updated 2026-10-08 19:08 UTC) - Right now: up, HTTP 200, 210 ms, checked 2026-10-08 19:08 UTC (get on `https://api.invofox.com`) - Uptime 24h 100.0% (42 probes) · 30 days 100.0% (42 probes) · p50 55 ms · p95 151 ms - security.txt: none - Watching pricing - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/invofox.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Starter plan | $500 | per month (plan) | from $500, billed annually, up to 5,000 pages a month | | Starter at its 5,000-page cap | $100 | per 1,000 pages | derived from the plan price, no per-page rate is published | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Three public OpenAPI 3.1 files (main 25 operations, ingest 7, seven webhook events), plus llms.txt and a Markdown twin of every docs page - Free plan of 500 pages with REST API access and no card, by self-serve sign-up opened on 5 October 2026 - The document list takes `select` field projection, `filter` operators, `sort`, and `skip` and `limit` up to 500 - 429 responses carry RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset and Retry-After headers, per the main OpenAPI file - security.txt valid until 1 June 2027, and the vendor states SOC 2 Type II and ISO 27001:2022 certification ## Weaknesses - No status page found. status.invofox.com does not resolve, and neither the site nor the docs link to one - No rate limit numbers. The vendor's own AI briefing says rate limits and page limits per file are not publicly documented - No public changelog and no official SDK. The only package is an n8n community node at 0.1.0 - Documents are retained by default and used to tune models. Zero retention is opt-in on Scale and Enterprise only - The General Terms and Conditions that the published DPA relies on were not found on the site ## Before you call it (notes for agents) 1. Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types 2. Upload with POST /v1/ingest/uploads as multipart, with `info` as a JSON string. Send `"useClassifier": true` in place of `type` to have the type detected 3. Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded 4. Handle the `file.rejected` webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely 5. Do not retry an upload blindly. There is no idempotency key, so send your own id in `clientData` and look it up with `filter` first ## Connect First request: ```bash curl -s -X POST "https://api.invofox.com/v1/ingest/uploads" \ -H "x-api-key: $INVOFOX_API_KEY" \ -F "files=@invoice.pdf" \ -F 'info={"type":"","clientData":{"internalId":"inv-1234"}}' ``` Through letme (picks today, calling later): https://letme.dev/invofox. letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Extend API + MCP | B | 62.9 | 291 | docs.ocr, docs.extract, docs.classify | no | https://www.anchorterminal.com/tools/extend.md | | Reducto API + MCP | B | 62.9 | 292 | docs.ocr, docs.extract, docs.classify | no | https://www.anchorterminal.com/tools/reducto.md | | Mindee API | C | 61.3 | 325 | docs.ocr, docs.extract, docs.classify | no | https://www.anchorterminal.com/tools/mindee.md | | LlamaParse API + MCP | C | 59.2 | 384 | docs.ocr, docs.extract, docs.classify | no | https://www.anchorterminal.com/tools/llamaparse.md | | Veryfi API + MCP | C | 55.2 | 456 | docs.ocr, docs.extract, docs.classify | no | https://www.anchorterminal.com/tools/veryfi.md | | Nanonets API + MCP | E | 42.6 | 586 | docs.ocr, docs.extract, docs.classify | no | https://www.anchorterminal.com/tools/nanonets.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - Self-serve access is new. The YC launch post of 5 October 2026 says that until then trying Invofox generally meant talking to the team first (source: ) - Processing is asynchronous. An upload returns ids, and results come by the `document.processed` webhook or by polling GET /documents/{id}, which can answer 404 for the first seconds (source: ) - The MCP server at developers.invofox.com/_mcp/server has one read-only tool, `searchDocs`, which searches the documentation. It does not process documents (source: ) - The standard pipeline retains documents and uses them to tune the model. Zero retention is opt-in and limited to Scale and Enterprise (source: ) - The vendor's own AI briefing says maximum pages per file and API rate limits are not publicly documented (source: ) - PUT /documents/{id} sends corrected values back, and the docs say every correction feeds model training (source: ) - YC lists Invofox in the Summer 2022 batch, based in Madrid with a team of 12 (source: ) ## Compare - [Invofox vs OpenDocRouter](https://www.anchorterminal.com/compare/invofox-vs-opendocrouter.md): D 46.8 vs C 56.6 - [Adobe PDF Services / PDF Extract API vs Invofox](https://www.anchorterminal.com/compare/adobe-pdf-extract-vs-invofox.md): C 55.9 vs D 46.8 - [Extend API + MCP vs Invofox](https://www.anchorterminal.com/compare/extend-vs-invofox.md): B 62.9 vs D 46.8 - [Invofox vs LlamaParse API + MCP](https://www.anchorterminal.com/compare/invofox-vs-llamaparse.md): D 46.8 vs C 59.2 - [Invofox vs Mindee API](https://www.anchorterminal.com/compare/invofox-vs-mindee.md): D 46.8 vs C 61.3 - [Invofox vs Mistral OCR API](https://www.anchorterminal.com/compare/invofox-vs-mistral-ocr.md): D 46.8 vs C 58.8 - [Invofox vs Nanonets API + MCP](https://www.anchorterminal.com/compare/invofox-vs-nanonets.md): D 46.8 vs E 42.6 - [Invofox vs Reducto API + MCP](https://www.anchorterminal.com/compare/invofox-vs-reducto.md): D 46.8 vs B 62.9 - [Invofox vs Unstructured API + MCP](https://www.anchorterminal.com/compare/invofox-vs-unstructured.md): D 46.8 vs D 46.9 - [Invofox vs Veryfi API + MCP](https://www.anchorterminal.com/compare/invofox-vs-veryfi.md): D 46.8 vs C 55.2 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on invofox.com or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "invofox", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Invofox on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Invofox on Anchor Terminal](https://www.anchorterminal.com/badges/invofox.svg)](https://www.anchorterminal.com/tools/invofox) ``` Plain link: ```html Invofox on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Invofox is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/invofox-dark.png - Light: https://www.anchorterminal.com/assets/share/invofox-light.png