1. Challenge integrity
The unauthenticated request returns a clear HTTP 402 challenge with stable payment requirements.
- Correct status code
- Machine-readable accepts/payment fields
- No CDN error page replacing the challenge
Position: directories and edge platforms can show that a paid resource exists. ResolveBots checks whether a buyer agent can discover it, pay it, parse it, and use what comes back.
Checklist
What an edge-launched x402 endpoint must survive.
These checks are intentionally practical. A seller that passes them is easier for buyer agents, directories, and reviewers to trust.
2. Header preservation
The edge path preserves the payment headers needed by the facilitator and origin.
- Payment header reaches verification layer
- Response headers survive the CDN
- No middleware strips signed payment fields
3. Cache behavior
The edge does not cache payment-required responses or paid payloads in a way that confuses buyers.
- 402 challenge cache policy is intentional
- Paid fulfillment is not leaked by cache
- Retry path behaves consistently
4. Discovery trail
Agents can find the route, price, chain, and schema without a human reading a launch post.
- OpenAPI or manifest present
- Canonical endpoint URL reachable
- Directory metadata matches live behavior
5. Fulfillment shape
The paid response returns a useful payload, not a login wall, HTML error, empty scalar, or ambiguous redirect.
- Parseable JSON when promised
- Output size and category are clear
- Errors are explicit and non-deceptive
6. Receipt discipline
The seller can explain what was paid for, what was returned, and how a buyer can verify the transaction.
- Payment receipt available when appropriate
- Provider response path documented
- Refund/failure posture stated plainly
ResolveBots scoring
Edge-specific checks for proof and readiness reviews.
Use the free checklist first. Then run a machine proof check or ask for a paid readiness review when the endpoint is launch-critical.
| Question | Why it matters | ResolveBots path |
|---|---|---|
| Does the edge return the expected 402 challenge? | Buyer agents need a clean payment requirement, not a CDN wrapper. | Endpoint Proof Check |
| Does a paid retry reach origin and return usable output? | The real buyer question starts after payment. | Endpoint Readiness Review |
| Does discovery metadata match live behavior? | Directories cannot compensate for stale or mismatched route data. | Discovery Audit |
| Does the seller want first credible agent buyers? | Launch seeding only works when seeded traffic is labelled and measured. | Launch Seeding Pilot |