Free · public paid-path check

Check your paid path in 3 minutes.

01DISCOVERY 02PAYMENT 03DELIVERY 04SETTLEMENT

Submit one public paid endpoint. We return a concise finding on discovery and payment-challenge shape. No account, no card, no sales call.

Freeno card, no account
One public routediscovery and payment shape
Signed evidenceconcise written finding
Free public-route preflight

Start with one route.

Submit one public paid endpoint. We inspect discovery and payment challenge shape and send one concise finding. No sales call and no credentials.

Public routes only. Do not submit passwords, tokens, private endpoints, or personal data.
What we test

The full revenue path.

A healthy server can still lose a payment. We test the commercial mechanism, not just uptime.

01 Discovery

Can buyers and agents find it?

  • Machine-readable metadata
  • MCP, OpenAPI, and .well-known consistency
  • Valid GET and POST examples
02 Payment

Can they understand and pay?

  • Protocol-valid 402 responses
  • Price, asset, recipient, and scope
  • CORS, redirects, and middleware order
03 Delivery

Does payment produce the result?

  • Proof bound to the paid route
  • Safe retry behavior
  • No paid 404, 422, or 500 response
04 Reconciliation

Can you prove the revenue?

  • Payment and route correlation
  • External versus internal classification
  • Fees, costs, and ledger evidence
Why this is different

Evidence cannot be prompted into existence.

AI can write a plausible report. It cannot recreate a protocol challenge, timestamped response hash, verifier signature, or authorized funded payment observed at a specific time. Those observations are the deliverable. Read Evidence Report 001 to see the exact proof boundaries.

What you receive

Evidence you can verify.

Evidence matrix

Route-by-route results with timestamps, response evidence, and reproducible steps.

Signed receipts

Tamper-evident receipts with canonical hashes, a persistent verifier identity, and offline verification.

Root cause and fix

The first material failure, the exact file or configuration change, and a scoped implementation estimate.

For serious paid agent surfaces

Need continuous verification?

The free preflight is a public-route snapshot. If you operate a paid API or MCP surface that needs continuous monitoring across releases, tell us the shape of the problem.

Start a conversation