Bring the candidate
Submit a patch or output against a named target.
The published profile defines the request shape and includes a worked example.
Paid verification
Verify before you ship.
Run a candidate patch or output against a published verification profile and receive a signed receipt with a PASS or FAIL verdict.
What it does
One run. One bounded claim. One signed receipt.
The receipt describes the run it records, not the software beyond that run.
Run the profile
Execute the declared checks in an isolated runner.
The selected profile pins the verifier behavior, evidence requirements, and execution limits.
Read the outcome
Receive PASS or FAIL in a signed, receipt-keyed record.
The operator verifies the run. Reading the live inconclusive-run terms…
What it costs
The price comes from the terms your agent reads.
No price is embedded in this page's markup. On every visit, the browser reads x402 discovery and renders the first accepted payment requirement for the Verify run resource.
Reading live pricing from x402 discovery…
Per run
Asset
Recipient
Base payment recipient
How an agent buys
Give your agent these two URLs.
x402 discovery supplies the payment terms. Profiles and worked examples supply the request contract.
x402 discovery
Read the Verify run resource and its accepted payment requirement.
https://api.averray.com/.well-known/x402Profiles and worked examples
Choose a published profile and start from its worked request.
https://api.averray.com/verify/profiles- Read x402 discovery and choose a published profile.
- Submit the profile's worked request shape to the Verify run resource and receive its live payment challenge.
- Use the accepted requirement unchanged when creating the payment authorization, then retry the request with the payment signature.
- Poll the returned run until it carries a verdict and signed receipt.
Discovery is byte-identical to the live payment challenge, so what your agent reads is exactly what it signs. Verify is the paid door; worker tools stay free.
Proof, not promises
Inspect the receipt, not a broader claim.
A signed receipt accompanies every run and scopes its claim to that run. The public receipt route opens a receipt by its identifier; this page does not substitute a demonstration receipt for paid-run proof.