{
  "fixes": {
    "slug": "invofox",
    "name": "Invofox",
    "listing": "https://www.anchorterminal.com/tools/invofox",
    "markdown": "# Fix list: Invofox\n\nFrom Anchor Terminal's listing at https://www.anchorterminal.com/tools/invofox, the October 2026 research run, assessed 8 October 2026. Grade D, 46.8 out of 100.\n\nThis is everything the published grade says the listing lacks, the biggest possible gain to the total first. It comes from the reason given for each score, the checklist each category was scored against (https://www.anchorterminal.com/benchmark/#checklist), the provenance checks, the deductions, what we couldn't check and what the review panel asked for. A fix counts at the next check, once it's public.\n\nFor a coding agent working on Invofox: work through the items below in the product, its docs and its public pages. Each category gives the reason for its score, with the points each checklist item earned, and the checklist itself, so the gap is the items that earned less than their points. Change the product, not the wording, and keep a note of what you changed and where it's published.\n\n## 1. Reliability, 30 out of 100, up to 14 more on the total\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability):\n\nHosted APIs, MCP servers, models and platforms.\n\n- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.\n\nLocal packages, SDKs, frameworks and stdio MCP servers.\n\n- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.\n\nProtocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors.\n\n## 2. Security \u0026 auth, 45 out of 100, up to 9.6 more on the total\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-security):\n\n- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.\n\nModels are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing.\n\n## 3. Payments \u0026 pricing, 30 out of 100, up to 8.8 more on the total\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-payments):\n\nThe published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).\n\n- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.\n- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for \"contact sales\" or prices behind a login.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).\n\nPayment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.\n\nOpen-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol.\n\n## 4. Maintenance \u0026 community, 30 out of 100, up to 6.1 more on the total\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance):\n\n- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.\n\nModels are read for deprecation notice periods and model churn rather than release counts.\n\n## 5. Agent ergonomics, 64 out of 100, up to 5.9 more on the total\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics):\n\n- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.\n\nModels are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs.\n\n## 6. Schema \u0026 documentation, 70 out of 100, up to 4.9 more on the total\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-schema):\n\nAPIs and MCP servers.\n\n- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.\n\nModels are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference.\n\n## 7. Transparency \u0026 trust, 55 out of 100, up to 3.9 more on the total\n\nMade of editorial 40, provenance 69.\n\nWhy it scored 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).\n\nThe checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency):\n\n- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).\n\nThe other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two.\n\nProvenance checks not met in full (half of this category, computed from checked facts):\n\n- Domain age: invofox.com, registered 2021-05-10 (5 years) (11 of 15)\n- Terms of service: read, states 1 of the 7 things a reader expects (4.9 of 10)\n- Privacy policy: read, states 6 of the 8 things a reader expects (8.5 of 10)\n- Status page: not found (0 of 10)\n- Changelog: not found (0 of 10)\n\n## What we couldn't check\n\nWhat we couldn't read counted as absent. Publishing it on a page a plain HTTP fetch can read (not only in a browser) lets the next check count it.\n\n- 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\n- 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\n- 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\n- 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\n- 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\n- Data and ID verification is marketed, and no verification endpoint is in the API reference, so no `kyc` capability is listed\n- Whether an API key can be revoked or rotated, and whether a status page exists under another host, was not established\n- The integration guide says custom Document Types are defined by contacting support, while the launch post says users can define what to extract themselves\n\n## Weaknesses\n\n- No status page found. status.invofox.com does not resolve, and neither the site nor the docs link to one\n- No rate limit numbers. The vendor's own AI briefing says rate limits and page limits per file are not publicly documented\n- No public changelog and no official SDK. The only package is an n8n community node at 0.1.0\n- Documents are retained by default and used to tune models. Zero retention is opt-in on Scale and Enterprise only\n- The General Terms and Conditions that the published DPA relies on were not found on the site\n\n## What costs an agent a turn today\n\nThe notes we give agents before they call it. Each one is a workaround an agent shouldn't need.\n\n- Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types\n- 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\n- Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded\n- Handle the `file.rejected` webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely\n- 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\n\n## When it's done\n\nSend what changed and where it's published as a dispute (https://www.anchorterminal.com/builders/#disputes, or `POST https://www.anchorterminal.com/api/v1/contact` with `\"kind\": \"dispute\"`). Disputes are answered in public, and the listing is checked again by the same checklist. Paying for an audit or a listing claim changes nothing here.\n",
    "grade": "D",
    "score": 46.8,
    "assessed": "2026-10-08",
    "run": "October 2026 research run",
    "categories": [
      {
        "key": "reliability",
        "name": "Reliability",
        "score": 30,
        "maxGain": 14,
        "reason": "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).",
        "checklist": [
          "Hosted APIs, MCP servers, models and platforms.",
          "- 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own).\n- 0 to 30, the incident record for the last 90 days on that page. 30 for a clean record or trivial incidents only, 20 for minor incidents only, 10 for one major outage (an hour or more of a core API down, or errors across the board), 0 for several. 5 when there's no history we could read, and the note says so.\n- 15, rate limits documented with numbers.\n- 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved.\n- 10, an SLA published for any paid tier.\n- 10, the surface agents use is generally available, not beta or preview.",
          "Local packages, SDKs, frameworks and stdio MCP servers.",
          "- 20, installs from an official package with supported runtimes stated.\n- 25, a public CI and test suite, passing on the default branch.\n- 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered).\n- 15, semver discipline and breaking changes called out in a changelog.\n- 15, version 1.0 or later, or declared stable.",
          "Protocols are read from their reference implementations, the public facilitators or servers, spec stability and test vectors."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-reliability"
      },
      {
        "key": "security",
        "name": "Security \u0026 auth",
        "score": 45,
        "maxGain": 9.6,
        "reason": "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).",
        "checklist": [
          "- 0 to 30, the credential model. 30 for OAuth 2.1 with scopes, or scoped and revocable keys with rotation. 20 for plain revocable API keys. 10 for one all-powerful key. 10 off when a secret can travel in a URL query string as a documented option.\n- 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions.\n- 0 to 15, prompt-injection posture where the tool returns untrusted content (documented mitigations or guidance). A tool that returns no untrusted content gets 10.\n- 0 to 15, audit logs or per-call visibility for the operator.\n- 0 to 20, a security programme. security.txt or a disclosure policy, a bug bounty, SOC 2 or ISO 27001, advisories handled in public.",
          "Models are read for retention, whether API data trains models (and whether that's off by default), zero-retention options and certifications. Frameworks for telemetry defaults, approval hooks, guardrails and sandboxing."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-security"
      },
      {
        "key": "payments",
        "name": "Payments \u0026 pricing",
        "score": 30,
        "maxGain": 8.8,
        "reason": "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).",
        "checklist": [
          "The published rubric, also on the [x402 page](https://www.anchorterminal.com/x402/).",
          "- 40, a machine payment protocol (x402, MPP or L402) on the tool's own endpoints. 10 to 30 when it covers only some endpoints or only goes through a third party, and the note says which.\n- 20, per-call or per-unit pricing published without a login. 10 for public plan-only pricing, 0 for \"contact sales\" or prices behind a login.\n- 20, a free tier or trial that doesn't need a card.\n- 20, autonomous onboarding, meaning an agent can get access without a person signing up in a browser (keyless use, x402, a programmatic key API).",
          "Payment platforms and agent wallets rarely charge for their own API over a machine protocol, so the first line has steps for them, and the highest one that applies counts. 40 when x402, MPP or L402 runs on all their own endpoints, 30 when it runs on part of their own API, 25 when their merchants can accept one, 20 for running a facilitator, 15 for paying as a buyer, and 0 when the only protocol is their own. Merchant acceptance sits above a facilitator because the platform's own customers can charge agents through it, while a facilitator settles for sellers who wire up the protocol themselves. The counter-argument (a facilitator does more for the protocol as a whole) has a point. Each note says which step applied.",
          "Open-source software you run yourself is scored on its hosted or paid option if it has one. A free, self-hosted package with nothing to buy gets 20, 20 and 20 for the last three lines, and 0 to 40 for the first only if it ships a payment protocol."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-payments"
      },
      {
        "key": "maintenance",
        "name": "Maintenance \u0026 community",
        "score": 30,
        "maxGain": 6.1,
        "reason": "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).",
        "checklist": [
          "- 0 to 30, time since the last release, or the last published model or API change for a closed service. 30 within 30 days, 20 within 90, 10 within 180, 0 older.\n- 20, at least three releases or dated changelog entries in the last 90 days.\n- 0 to 25, responsiveness. Issues and pull requests answered on GitHub (the open issues and how recent the replies are). For closed services, a public changelog and a support or community channel that answers, 0 to 15.\n- 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models).\n- 10, package health, current dependencies and CI.",
          "Models are read for deprecation notice periods and model churn rather than release counts."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-maintenance"
      },
      {
        "key": "ergonomics",
        "name": "Agent ergonomics",
        "score": 64,
        "maxGain": 5.9,
        "reason": "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).",
        "checklist": [
          "- 0 to 25, context cost. For MCP, the number and size of the tool definitions (25 for ten or fewer compact tools, 15 for 11 to 30, 5 for more than 30, plus up to 10 back for toolsets, dynamic loading or read-only subsets). For APIs, whether responses can be sized (field selection, limits, summaries).\n- 20, pagination, filtering and output-size controls.\n- 20, actionable, documented error responses, codes and messages an agent can recover from.\n- 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations.\n- 15, sensible defaults, few required parameters, and official SDKs in at least two languages.",
          "Models are read for tool use, structured output, prompt caching, context length, batch and SDKs. Frameworks for how much code and how many defaults a tool-calling agent with MCP needs."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-ergonomics"
      },
      {
        "key": "schema",
        "name": "Schema \u0026 documentation",
        "score": 70,
        "maxGain": 4.9,
        "reason": "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).",
        "checklist": [
          "APIs and MCP servers.",
          "- 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool).\n- 10, llms.txt or Markdown docs served for agents.\n- 0 to 20, descriptions that say what a tool is for, when to use it and when not to, read from the tool definitions in the source or the API reference.\n- 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs.\n- 0 to 15, examples and documented error responses.\n- 15, versioning and a public changelog.",
          "Models are read from the API reference, the OpenAPI file, llms.txt, the structured-output and tool-use docs and the model cards. Frameworks from docs a model can follow, typed interfaces, examples and the API reference."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-schema"
      },
      {
        "key": "transparency",
        "name": "Transparency \u0026 trust",
        "score": 55,
        "maxGain": 3.9,
        "reason": "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).",
        "blend": "editorial 40, provenance 69",
        "checklist": [
          "- 0 to 30, source availability and licence clarity. 30 for open source under an OSI licence, 15 for closed with clear terms, 0 for unclear terms.\n- 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors).\n- 0 to 20, a deprecation policy or notices with dates.\n- 0 to 20, telemetry disclosed with an opt-out (local software), or subprocessors and data locations disclosed (hosted).",
          "The other half of Transparency and trust is the provenance score, computed from checked facts (below). The category score is the mean of the two."
        ],
        "checklistUrl": "https://www.anchorterminal.com/benchmark/#checklist-transparency"
      }
    ],
    "provenance": [
      {
        "label": "Domain age",
        "value": "invofox.com, registered 2021-05-10 (5 years)",
        "points": 11,
        "max": 15
      },
      {
        "label": "Terms of service",
        "value": "read, states 1 of the 7 things a reader expects",
        "points": 4.9,
        "max": 10
      },
      {
        "label": "Privacy policy",
        "value": "read, states 6 of the 8 things a reader expects",
        "points": 8.5,
        "max": 10
      },
      {
        "label": "Status page",
        "value": "not found",
        "points": 0,
        "max": 10
      },
      {
        "label": "Changelog",
        "value": "not found",
        "points": 0,
        "max": 10
      }
    ],
    "unchecked": [
      "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"
    ],
    "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"
    ],
    "agentNotes": [
      "Ask the owner for an API key and the Document Type id or alias from app.invofox.com. No API endpoint lists Document Types",
      "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",
      "Expect 404 from GET /documents/{id} for the first seconds. Poll from 5 seconds with doubling, and stop at approved, pendingCorrection or discarded",
      "Handle the `file.rejected` webhook or check the import. A rejected file never produces a document, so polling the document waits indefinitely",
      "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"
    ],
    "recheck": "https://www.anchorterminal.com/builders/#disputes"
  },
  "meta": {
    "attribution": "Anchor Terminal (https://www.anchorterminal.com)",
    "docs": "https://www.anchorterminal.com/docs/",
    "generatedAt": "2026-10-08",
    "license": "CC-BY-4.0",
    "method": "https://www.anchorterminal.com/benchmark/",
    "methodology": "0.4",
    "openapi": "https://www.anchorterminal.com/openapi.json",
    "preview": false,
    "run": "2026-10-01",
    "runLabel": "October 2026 research run"
  }
}