# Fix list: Rutter Accounting API From Anchor Terminal's listing at https://www.anchorterminal.com/tools/rutter, the October 2026 research run, assessed 1 October 2026. Grade C, 55.8 out of 100. This 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. For a coding agent working on Rutter Accounting API: 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. ## 1. Security & auth, 36 out of 100, up to 11.2 more on the total Why it scored 36: client_id and client_secret by HTTP Basic auth, one pair for the whole organisation, plus a per-connection access_token that the docs only ever pass as a query parameter, so it lands in URLs and logs. We deducted 5 rather than 10 because the token is useless without the client secret (15). No read-only credentials or scopes found (3). Returns ledger and commerce data with third-party text and no injection guidance. Each call reaches only the connection its access_token names, which limits what an injected prompt can reach (5). Integration management and observability tools on the paid plan, which we couldn't inspect (8). A Vanta trust centre mentions encryption at rest and in transit and access logging, but we couldn't see certifications, a disclosure policy or a bug bounty, and there's no security.txt per the 30 September check (5). The checklist (https://www.anchorterminal.com/benchmark/#checklist-security): - 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. - 0 to 20, read-only or least-privilege modes, and confirmation or approval for destructive actions. - 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. - 0 to 15, audit logs or per-call visibility for the operator. - 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. ## 2. Payments & pricing, 20 out of 100, up to 10 more on the total Why it scored 20: No x402, MPP or L402 (0). Production is "Get a custom quote" (0). Starter is free for 30 days with sandbox data and QuickBooks, Xero, FreshBooks and Zoho Books, no card (20). Browser signup (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-payments): 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. - 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. - 20, a free tier or trial that doesn't need a card. - 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. ## 3. Reliability, 67 out of 100, up to 6.6 more on the total Why it scored 67: Statuspage at status.rutterapi.com with API, Rutter Link and per-platform components (20). Several majors in September. High latency and errors on the API from 20:21 UTC on 3 September to 21:10 on 4 September, 5xx errors and slow responses from 17:25 to 20:43 on 14 September, write errors for about 100 minutes on 1 September and delayed QuickBooks Online syncs for 12 hours on 1 and 2 September (0). 500 requests per 10 seconds per paid organisation, 100 for free, test and sandbox (15). 429 for Rutter's own limit and 452 when the platform throttles, an Idempotency-Key header for safe retries and async or prefer_sync writes. No Retry-After mentioned (12). 99.9 per cent monthly uptime SLA on the pricing page (10). GA (10). The checklist (https://www.anchorterminal.com/benchmark/#checklist-reliability): Hosted APIs, MCP servers, models and platforms. - 20, a public status page with component history (Statuspage, Instatus, BetterStack or the vendor's own). - 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. - 15, rate limits documented with numbers. - 15, documented 429 or overload handling (Retry-After, backoff guidance), and idempotency keys or safe-retry guidance where writes are involved. - 10, an SLA published for any paid tier. - 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. - 25, a public CI and test suite, passing on the default branch. - 0 to 25, open crash or regression issues relative to activity (25 for few and handled, 0 for many, old and unanswered). - 15, semver discipline and breaking changes called out in a changelog. - 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. ## 4. Agent ergonomics, 67 out of 100, up to 5.4 more on the total Why it scored 67: Cursor pagination on lists. We found no field selection or summary options (12). next_cursor paging, with no other list filters checked (14). Structured errors that separate Rutter's failures from the platform's, so an agent can tell a bad request from a throttled ledger (18). Idempotency-Key on writes, and response_mode prefer_sync returns within 30 seconds or falls back to a 202 with an async_response (18). No official SDK, a required version header, and the connection token as a query parameter on every call (5). The checklist (https://www.anchorterminal.com/benchmark/#checklist-ergonomics): - 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). - 20, pagination, filtering and output-size controls. - 20, actionable, documented error responses, codes and messages an agent can recover from. - 20, idempotency or safe retries, and for MCP the `readOnlyHint` and `destructiveHint` annotations. - 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. ## 5. Transparency & trust, 51 out of 100, up to 4.3 more on the total Made of editorial 26, provenance 75. Why it scored 51: Closed service. Terms and privacy policy are PDFs on Google Drive that we couldn't read, and the site names no legal entity beyond "Rutter" (7). We found no retention, storage or deletion statement we could read. The trust centre covers encryption and access logs only (5). A versioning policy, four supported dated versions back to 2023-02-07 and an upgrade guide with breaking changes per version, but no sunset dates found (14). No subprocessor list or data locations found (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-transparency): - 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. - 0 to 30, data handling and retention statements that agree with each other (privacy policy, DPA, retention periods, subprocessors). - 0 to 20, a deprecation policy or notices with dates. - 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. Provenance checks not met in full (half of this category, computed from checked facts): - Endpoint on the vendor's domain: production.rutterapi.com is not on rutter.com (0 of 15) - security.txt: not found (0 of 10) ## 6. Schema & documentation, 79 out of 100, up to 3.4 more on the total Why it scored 79: OpenAPI spec per API version at docs.rutter.com/rest//spec, which the listing had as missing (25). llms.txt returns 404 and there are no Markdown docs (0). Reference pages per endpoint with platform coverage tables, though they don't say when to prefer one route (14). Typed request and response models, and POST input validation rules exposed per platform for expenses and bills (12). Errors carry error_type, error_code, error_message and error_metadata, with 450, 451, 452 and 550 marking a platform's own 400, 401, 429 and 500 (13). Dated versions in the X-Rutter-Version header, an upgrade guide listing breaking changes per version and a weekly changelog (15). The checklist (https://www.anchorterminal.com/benchmark/#checklist-schema): APIs and MCP servers. - 25, a machine-readable contract (a public OpenAPI file or similar; for MCP, typed JSON Schema inputs on every tool). - 10, llms.txt or Markdown docs served for agents. - 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. - 0 to 15, typed inputs with enums, constraints and required fields, and no free-form JSON blobs. - 0 to 15, examples and documented error responses. - 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. ## 7. Maintenance & community, 62 out of 100, up to 3.3 more on the total Why it scored 62: Changelog entry on 24 September 2026 (30). 14 dated entries since 2 July, one most weeks (20). Closed service with a weekly changelog, a help centre and 24/7 support on the paid plan (12). No official SDKs and no MCP server (0). No packages to judge (0). The checklist (https://www.anchorterminal.com/benchmark/#checklist-maintenance): - 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. - 20, at least three releases or dated changelog entries in the last 90 days. - 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. - 15, presence in the official MCP registry under a verified namespace (MCP servers), or current official SDKs (APIs and models). - 10, package health, current dependencies and CI. Models are read for deprecation notice periods and model churn rather than release counts. ## What we couldn't check What 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. - The legal entity, retention terms and subprocessors, which sit in Google Drive PDFs we couldn't read - Whether access_token can be sent in a header instead of the query string - Which endpoints honour Idempotency-Key and how long keys are kept - Rutter's certifications (SOC 2 or otherwise), not visible on the trust centre we fetched ## Weaknesses - Production prices are quote-only - Terms and privacy policy are Google Drive PDFs, and no legal entity is named on the site - The per-connection access_token travels as a URL query parameter - Four API incidents in September 2026, including about 25 hours of high latency and errors on 3 and 4 September - No SDK, llms.txt or MCP server from the vendor ## What costs an agent a turn today The notes we give agents before they call it. Each one is a workaround an agent shouldn't need. - Send X-Rutter-Version: 2024-08-31 on every call - Send an Idempotency-Key on every create so a retry after a timeout doesn't write twice - Use response_mode=prefer_sync and handle the 202 async_response anyway - Treat 452 as the ledger throttling you and 429 as Rutter's 500-per-10-seconds organisation limit - Keep access_token out of logged URLs. The docs only show it as a query parameter ## What the review panel asked for - publish llms.txt - list which endpoints honour Idempotency-Key - access_token in a header - read-only credentials ## When it's done Send 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.