Moovmoov.io

ScoredJul 24, 2026, 10:27 AM

Moov's API design and agent discoverability are strong foundations — partners and agents can find the APIs without a sales conversation. However, the program's weakest area is agent understanding: operations lack clear purpose descriptions, there is no agent instructions file, and docs are not structured for machine consumption, meaning AI agents cannot reliably interpret or act on Moov's API surface.

API DesignA clean, typed, well-governed API contract agents can reason about4 pass1 warn0 fail100A+
SignalPointsFindingsRationale
passMachine-readable, versioned contractvia spec25/25Versioning declared (info.version="v2026.07.00") and header-versioning detected. Investigated: spec 100%, docs 100%.A current OpenAPI version with a declared versioning scheme lets agents reason about the contract.
passAuth declared & discoverablevia spec25/25Authentication required (global or on every operation). Investigated: spec 100%, docs 100%.Agents can only authenticate when auth is declared, scoped, and discoverable.
warnSchema coverage & depthvia sdk24.9/25181/182 (99%) public params are fully typed (no any/**kwargs). Analyzer reports not all methods have a derivable input schema. Investigated: sdk 100%, spec 67%.Typed, complete request/response schemas are what make agent function-calling possible.
passSecurity & governance hygienevia spec15/15No credential-shaped strings detected in spec. Investigated: spec 100%, wellknown 0%.No leaked secrets, no critical lint violations, no OWASP API Top-10 spec smells, and a published vulnerability-disclosure channel.
passExample coveragevia docs10/10Code samples in 4 language(s) across docs (top: shell, javascript, go); 3/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 100%, spec 0%.Examples carry shape semantics schemas under-specify — for humans and agents alike.
Developer ExperienceThe context both developers and agents need to integrate fast — onboarding, code samples, complete descriptions and worked examples3 pass0 warn2 fail59D
SignalPointsFindingsRationale
passCode samples in docsvia docs18/18Code samples in 4 language(s) across docs (top: shell, javascript, go); 3/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.Multi-language samples shorten time-to-first-call.
passDescription completenessvia spec15/1576% description completeness (target 90%+). Investigated: spec 100%, sdk 87%.Complete descriptions are the context humans and agents need to use endpoints.
passChangelog publishedvia spec13/13changelog documented in the docs site at https://docs.moov.io/changelog/. Investigated: spec 100%, docs 100%, sdk 100%.A published changelog lets partners track changes without surprise.
failSelf-service developer portalvia docs0/29No signup page detected across conventional paths (/signup, /sign-up, /register, /get-started, /console/signup, /dashboard/signup, /try, /try-free, /free, /free-trial, /start, /start-free). Investigated: docs 0%.Self-serve key/account creation is the fast first call for partners, with no sales gate.
failQuickstart presentvia docs0/25No quickstart/getting-started page found at the conventional paths. Investigated: docs 0%.A quickstart is the fastest path from landing page to first successful call.
Agent DiscoveryPartners and their agents can find your APIs — llms.txt, registries, crawlable and reachable docs1 pass3 warn0 fail85A
SignalPointsFindingsRationale
passRegistry & SDK presencevia docs28/28Indexed on Context7 (websites/moov_io_api, 2460 snippets). Investigated: docs 100%, cli 100%, sdk 83%, mcp 0%, wellknown 0%.Listing in MCP registries and publishing SDKs puts the API where agents and their tooling look.
warnllms.txt present, valid & comprehensivevia docs22.5/30No llms.txt directive found in HTML of any of 50 sampled pages. Investigated: docs 75%, sdk 0%.A valid, comprehensive llms.txt is the machine-readable entry point for agents.
warnDocs reachable, not hard auth-gatedvia docs22.5/30Server ignores Accept: text/markdown header (0/50 sampled pages return markdown). Investigated: docs 75%.Agents can only index and fetch docs they can reach — past auth gates and over correct HTTP semantics.
warnCrawlable / AEOvia wellknown9/12Sitemap lastmod coverage 5% or newest entry older than 90 days. Investigated: wellknown 75%.Bots allowed plus a fresh sitemap make docs findable by agent crawlers.
Agent UnderstandingAgents can correctly interpret your APIs — machine-readable errors, consistent descriptions, structured data, parseable docs1 pass2 warn3 fail59D
SignalPointsFindingsRationale
passMachine-readable errors (RFC 9457)via docs28/2812 distinct 4xx/5xx response codes documented. Investigated: docs 100%, sdk 100%, spec 50%.RFC 9457 problem details and a documented error-code inventory let agents parse failures without burning tokens.
warnAgent-navigable, token-efficient docsvia docs18.3/226 of 50 pages have substantive content differences between markdown and HTML (avg 7% missing). Investigated: docs 83%.Server-rendered, clean, small-footprint docs are what an agent can cheaply fetch and parse correctly.
warnDescription consistency across surfaces0.8/7Mean pairwise description similarity across 3 surfaces (spec, docs, sdk) is 4% (threshold 35% for full credit).Every surface tells the same story about what the product is.
failOperation purpose clarityvia spec0/250% of operations are agent-inferable. Investigated: spec 0%.Agents select the right endpoint from its summary + operationId; clear, named operations make tool-selection reliable — the strongest driver of correct tool choice.
failAgent instructions file (AGENTS.md)via wellknown0/10No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.An AGENTS.md gives coding agents explicit setup, auth, and usage instructions to interpret and operate the API — beyond llms.txt's link index.
failDocs structured datavia docs0/8Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.Structured data (JSON-LD/schema.org) on docs pages gives agents an unambiguous parse target and is what answer engines cite. Detected on the JS-rendered head (Firecrawl) for a bounded page budget, so JS-injected JSON-LD is now caught; pages we can't render are excluded rather than failed.
Agent UsabilityAgents have the context to use your APIs reliably, not just find them4 pass0 warn1 fail92A+
SignalPointsFindingsRationale
passIdempotency documentedvia spec27/27idempotency documented in the docs site at https://docs.moov.io/guides/money-movement/idempotency/. Investigated: spec 100%, docs 100%, sdk 0%.Documented idempotency lets agents retry safely.
passRate-limit signalingvia spec22/22rate-limit behavior documented in the docs site at https://docs.moov.io/api/rate-limits/. Investigated: spec 100%, docs 100%.Machine-readable rate-limit headers let agents throttle adaptively.
passPagination documented & consistentvia spec22/22Pagination params detected on 45 list endpoint(s). Investigated: spec 100%, docs 100%.Consistent, documented pagination lets agents traverse collections.
passSandbox separationvia sdk20/20Sandbox environments are exposed (sandbox). Investigated: sdk 100%, spec 0%, docs 0%.An isolated environment lets agents exercise destructive operations safely.
failRunnable collection with test scriptsvia platform0/9No public Postman workspace discovered for the org. Investigated: platform 0%.A public, maintained collection with assertions is runnable truth agents validate against.
Resources Discovered

The public resources we found for Moov — the evidence behind the score. All discovered from public sources; nothing here requires access to your systems.

Agent hintsContext7 (2,460)
APIs analyzed1Moov API
Want to improve your results?