RReadinessAPI
ProductAPI docsOpenAPIScore a spec
Public beta · Last updated July 20, 2026

Privacy

ReadinessAPI minimizes what it retains. Raw OpenAPI specifications are processed in memory and are not intentionally persisted, while a paid report derived from a specification may be cached for a bounded retry window.

Your data lifecycle

Raw specification

Processed in memory to produce the requested result.

Not intentionally persisted.
Operational metadata

Request ID, route, status, duration, input-size bucket, rules version, and error code.

Bounded; client addresses are pseudonymized with HMAC-SHA256.
Paid derived report

Findings, patches, MCP candidates, hashes, and contract-derived fragments.

Cached for up to 24 hours for safe retries.
Settlement record

Status, network, atomic amount, transaction hash, and a one-way payment hash; payer addresses and authorization payloads are excluded.

Retained for the configured reconciliation period, currently up to 180 days.
Application logs

Operational events needed to diagnose service health.

No raw specification or detected secret values.

Browser URL imports

URL imports happen in your browser. The browser fetches the public HTTPS file and sends its text to the scoring endpoint. The HTTP API does not fetch specification URLs or resolve remote references.

Paid retries

Successful paid reports and hashed payment identifiers are retained in Redis for up to 24 hours to make identical retries safe and detect conflicting reuse. Reports can contain findings, schemas, and fragments derived from the submitted contract.

Payment reconciliation

When settlement telemetry is enabled, daily exportable records contain the settlement status, network, amount, transaction hash, and a truncated one-way hash of the payment payload. Raw wallet authorizations and payer addresses are not written to this ledger.

Public beta warning

Do not submit confidential contracts during the beta. Never place credentials, private keys, access tokens, or other secrets in an OpenAPI document.

Limits and controls

Input size, processing time, imports, references, and output are bounded. Read the API limits and privacy controls for the current technical constraints.

Ready to evaluate a non-confidential contract?

Return to the free score →
RReadinessAPI

Contracts that agents can trust.

CommunityReport an issueProductAPI docsOpenAPIPrivacyTermsBeta status