Skip to main content

​
Documentation Corrections

A sweep of the documentation site against the live API. No API behavior changed: these entries correct places where the docs had drifted.
If you copied code samples from these docs before this date, check your hard-coded x402 amounts. The previously documented 50000 ($0.05) amount for /v1/entity/check was wrong and will now be rejected as insufficient payment.

​
Pricing corrected

Superseded: these were the prices on 5 September 2026. The current prices are on Pricing, and the enhanced tier on these endpoints was retired on 2026-09-24. The section is left as it was published, because a changelog entry records what was said on a date.
Per-call prices across all pages now match Pricing. The most visible change is /v1/entity/check, previously documented at 0.01/0.01 / 0.05 / $0.15 across the cached, fresh, and enhanced quality tiers: Every x402 amount field, X-Payment-Amount header sample, and executable tier-price table in the guides was updated to the 6-decimal equivalents.

​
enterprise tier removed

Superseded: a key’s tier sets per-minute and rolling 24-hour rate limits, not a number of calls you buy (see Rate Limits), and /v1/keys/upgrade/{tier} is a POST. The section is left as it was published.
The API key tier ladder is free / sandbox, indie, starter, growth, pro. There is no enterprise tier: it has been removed from the rate-limit and error-handling tables. Pro’s monthly quota is 250,000 calls, not 50,000. Only free and sandbox keys can be provisioned directly through POST /v1/keys/create. All other tiers are reached by paying via x402 against GET /v1/keys/upgrade/{tier}. See Authentication.

​
MCP tool names

Superseded by September 7: two of the five names below are wrong. The MCP server answers to get_trust_score and get_risk_score, not trust_score and risk_score. The paragraph is left as it was published, because a changelog entry records what was said on a date.
The manifest at /.well-known/mcp.json declares check_entity. Documentation examples that called it check_entity_trust have been corrected. The five tools are check_entity, check_agent, trust_score, verify_wallet, and risk_score.

​
Discovery response shape

The /.well-known/x402.json examples now match the live response. Endpoint entries carry price_usdc, price_raw, and category. The listing does not include a quality_tiers object: per-tier prices come from Pricing or from the amount in the 402 response.