Endpoints get called, the responses get graded, and the score decides where the listing shows up in search.
New endpoints arrive continuously from on-chain settlement signals across every supported chain, from facilitator catalogs, and from merchant claims.
Each endpoint gets probed before any real call goes out. Endpoints that return a valid 402 with payment requirements move forward. Endpoints that 5xx, time out, or return 200 without asking for payment get skipped.
Eligible endpoints get an input that fits the endpoint, the call gets made, and the full response is captured along with the settlement record.
The response is evaluated against what the merchant claims the endpoint does, including the URL, description, price, and the input we sent. The output is a 0 to 100 score with a status, brief notes, and concrete fix instructions if something is broken.
High-scoring endpoints surface in search, ranked by a blend of score, settlement volume, and recency. Endpoints that fail repeatedly are auto-suspended and stop appearing in default results.
Suspended endpoints re-enter the queue on a widening backoff schedule. A single passing run resets the counter and restores the listing. Endpoints that stay broken long enough are eventually retired, and an admin can revive them later.
Merchants can run a test on their own endpoint at any time from the resource editor. A passing run resets the failure counter and lifts suspension immediately.
Every test produces a 0 to 100 score plus a status of pass, fail, or inconclusive. The AI judges whether the response actually delivers on the merchant's claimed purpose, given the price paid.
The response does what the endpoint says it does, and the structure of what comes back is easy to consume. Surfaces high in search.
The response works. Documentation might be sparse or the shape inconsistent, but the listing is reliable enough to keep.
The response works, but it does not quite match the description. Listed, but ranked lower until the merchant tightens it up.
Something is wrong. The response is broken, the price is wrong for what comes back, or the description is misleading. Hidden from default search.
Badges high-scoring listings can earn
Every row in the verification history is tagged so merchants and admins can audit who paid for what.
Automated cron run from the verifier loop. Paid by the platform wallet on a freshness cadence.
Merchant clicked Test in the editor inside the free-window. Paid by the platform wallet, capped at one per hour.
Merchant clicked Test outside the free-window. Browser-signed with their connected wallet, USDC out of their balance.
A visitor on the public resource page clicked the Test theater button. Paid by the platform wallet, single per-resource cooldown.