Skip to content
x401 identity proof demo

Prove first. Pay second. Launch with trust.

This demo shows how ResolveBots can add x401 identity proof in front of an x402 paid launch-seeding offer. It is intentionally a mock wallet flow, but the route returns real HTTP 401 and 402 responses with protocol-shaped headers.

Open API route

401: identity required

The seller route challenges the agent with `PROOF-REQUIRED`, asking for a verified launch-buyer credential.

Wallet presentation

The demo wallet returns `PROOF-PRESENTATION` with personhood, organization, intent, challenge, and issuer fields.

402: payment required

Once proof is satisfied, the route asks for x402 payment, then grants access to the paid ResolveBots intake package.

1

Request protected offer

Call the seller route with no credential. It should return HTTP 401 plus `PROOF-REQUIRED`.

2

Present verified buyer proof

Decode the challenge and retry with a mock verifiable presentation in `PROOF-PRESENTATION`.

3

Simulate x402 settlement

After proof succeeds, satisfy the payment step and unlock the service package.

Production version: replace the mock wallet with a real DC API/OpenID4VP wallet, use the x401 trust list issuer constraints, and send the 402 leg to the existing Darrylbots x402 paid intake endpoint.

Ready 
Press Run demo to start the x401 + x402 handshake.