# Fix list: Validic Inform From Anchor Terminal's listing at https://www.anchorterminal.com/tools/validic, the October 2026 research run, assessed 14 October 2026. Grade C, 57.9 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 Validic Inform: 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, 30 out of 100, up to 12.3 more on the total Why it scored 30: One organisation token per organisation, sent as `?token=` in the URL as the only documented option, with no scopes or rotation found (10 less 10, 0 of 30). End users grant each source through the marketplace, but no read-only token exists and `DELETE` on a user is permanent with no confirmation (6 of 20). Responses are mostly numeric device readings, with user notes as the free-text field (9 of 15). The developer dashboard and a connection events endpoint give some visibility, with no audit log found (5 of 15). ISO 27001 and HITRUST claimed, annual third-party penetration testing, no security.txt or bug bounty (10 of 20). 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. Agent ergonomics, 50 out of 100, up to 8.1 more on the total Why it scored 50: Responses are sized by date range (30 days at most), `source` filters and a `latest` endpoint, with no field selection (14 of 25). Organisation-wide and per-user reads, list metadata and stream filters by resource and event type (14 of 20). Inform errors are `{status, error}` with no detail, and an over-long date range returns a bare 400 (8 of 20). No idempotency keys. `uid` is chosen by the caller, sign-up returns `USER_EXISTS`, and streams can be replayed (8 of 20). Few required parameters. No server SDK, only mobile SDKs and an MIT sample repository (6 of 15). 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. ## 3. Payments & pricing, 40 out of 100, up to 7.5 more on the total Why it scored 40: Read with the hosted rubric. No x402, MPP or L402 (0). The plan page names a free tier and negotiated Enterprise pricing, with Business coming soon and no unit prices (5 of 20). The Developer tier needs no card or contract (20). Sign-up, verification and provisioning are API calls an agent can make, but the six-digit code arrives by email and the terms ask for a person's acceptance (15 of 20). 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. ## 4. Reliability, 73 out of 100, up to 5.4 more on the total Why it scored 73: Read with the hosted lines and scored on the Inform REST and Streaming APIs. status.validic.com is a Statuspage site with 43 components and incident history (20). No incident between 16 July and 14 October 2026; the latest, a legacy SDK notice, opened 17 October 2025 (30). The REST default limit is 2,000 requests per token per hour (15). No 429 or Retry-After guidance and no idempotency keys were found; the sign-up guide gives a polling interval for provisioning (3 of 15). The free tier states no SLA and Enterprise has a custom one, with none published (0). The Streaming API is generally available but the free tier's REST API is labelled a preview (5 of 10). The service agreement forbids monitoring availability for benchmarking, which we record as a fact. 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. ## 5. Schema & documentation, 75 out of 100, up to 4.1 more on the total Why it scored 75: Each reference page carries an OpenAPI 3.1 fragment, with no full specification file found. The fragments declare an `api_key` query parameter while the docs and paths use `token` (18 of 25). llms.txt indexes the docs, every page is served as Markdown, and plain-text agent guides cover sign-up and a quickstart (10). The guides say when to use REST and when Streaming, and flag pitfalls such as the internal `id` (15 of 20). Data types and metric names are listed in prose, with no enums in the fragments read (7 of 15). Examples throughout and error codes listed for sign-up, but Inform errors carry no detail (10 of 15). Versioned hosts (`api.v2`) and dated release notes on help.validic.com (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. ## 6. Transparency & trust, 71 out of 100, up to 2.5 more on the total Made of editorial 53, provenance 88. Why it scored 71: Closed service with a public Online Service Agreement (13 August 2025) and MIT sample apps (17 of 30). The privacy policy (20 January 2026) says data is erased after a retrieval period of typically 30 days from contract end, the API reference says deleted users' data is kept 7 years under HIPAA, and Inform stores member data de-identified to Safe Harbor. The data security policy dates from 20 January 2022 (20 of 30). Release notes date the end of support for Suunto, Under Armour and Misfit, and the agreement promises notice of an App discontinuance as soon as practicable, with no API notice period (8 of 20). US AWS data centres are stated, with no sub-processor list (8 of 20). 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): - Terms of service: read, states 7 of the 7 things a reader expects, and has 1 clause that costs points (8 of 10) - security.txt: not found (0 of 10) ## 7. Maintenance & community, 74 out of 100, up to 2.3 more on the total Why it scored 74: Inform Platform release notes dated 12 October 2026 (30). Inform Platform, Mobile SDK and HealthBridge release notes dated 12 October, 8 October and 25 September 2026 among others (20). Closed service with dated public release notes and a support portal; we did not test support response (10 of 15). Mobile SDK v2 release notes dated 8 October 2026, no server SDK and no entry in the official MCP registry (8 of 15). The inform-quickstart repository has a test workflow badge and its last commit on 10 July 2026 (6 of 10). 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. - unchecked: the content of individual release notes, so breaking changes in 2026 could not be ruled out - unchecked: whether 429 responses carry Retry-After, and the Streaming API's limits - unchecked: whether the organisation token can be rotated or revoked from the developer dashboard, which sits behind a login - The 'MCP & Sparks AI tooling' named on the Enterprise plan has no public documentation, so it was not graded ## Weaknesses - The organisation token is sent as `?token=` in the URL, the only documented option - Errors return only a status and a phrase, and a date range over the limit gives a bare 400 - The free tier holds synthetic data only, and the REST API there is a preview - No server-side SDK and no full OpenAPI file, only fragments on each reference page ## 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. - Show the developer the free-tier terms and wait for acceptance before calling `POST /auth/register` - Send `Authorization: ` to sign-up calls, but pass the organisation token as `?token=` on Inform calls - Use the customer `uid` in URLs, never Validic's internal `id`, which returns a silent 404 - Keep date ranges to 30 days or less and page month by month for backfills - Unwrap `data` on list responses and treat an empty array as normal on a new account ## 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.