Find the contract gaps that hide your paid API.

A healthy endpoint can still be missed by an agent or discovery directory. Review payment metadata, explicit free routes, security declarations and request examples before investigating the runtime.

Limit:32,000 UTF-8 bytes,30 operations,20 nesting levels. Input format:{"spec":{...}}. OpenAPI3.0.x or3.1.x.

Findings will appear here.

For a Dot or another agent

Free POST /demo/discovery-contract with the same JSON. This sends the supplied contract to TableProof for in-memory processing; only aggregate invocation counts are stored. No authentication or payment required. Download the standalone Node18+ checker or read the invented example.

Get a scoped repair

TableProof's independent OpenAPI review service can review supplied public or redacted contracts and propose a patch with repeatable acceptance requests. Scope, price and funded terms must be agreed before custom work.

Our own API initially had zero valid routes in the indexer preflight. After repairing metadata and examples, fifteen resources registered, including five paid routes. Independent listing. This is our own production example, not a paid client result.

A clean report means no listed static issue was found. It does not establish schema validity, discoverability, successful settlement or native Dots compatibility. Reference-based contracts need separate review. Indexer discovery specification · TableProof API contract.

No OpenAI affiliation. No private credentials, account permissions or production deployment are requested.