x402 V2 · MACHINE PAYMENTS · VERIFIED RESULTS

An AI agent can receive a 402, pay, and continue.

HumanMirror now exposes Outcome, One and Flow through x402 V2 in parallel with Nexus credits and Stripe. The server verifies payment authorization before execution and settles only after the HumanMirror result has passed its deterministic verification.

Machine manifest Observed reputation

Base mainnet is live. HumanMirror now advertises real USDC x402 V2 challenges on Base mainnet. Coinbase CDP handles facilitator verification and settlement; the public payout address is configured and no private wallet key is stored in the HumanMirror application.

Outcome$0.010

/api/x402/outcome/

One$0.012

/api/x402/one/

Flow$0.024

/api/x402/flow/

Protocol sequence

1. POST the HumanMirror request with no payment header
2. Receive HTTP 402 + PAYMENT-REQUIRED
3. Sign the selected x402 payment requirement
4. Retry with PAYMENT-SIGNATURE
5. HumanMirror asks the facilitator to verify authorization
6. HumanMirror executes and verifies the requested result
7. Only after verified success, HumanMirror requests settlement
8. Receive HTTP 200 + PAYMENT-RESPONSE + verified result

Production payment semantics. HumanMirror verifies the x402 authorization before execution and requests settlement only after the requested result succeeds. Failed HumanMirror execution is not settled. Base Sepolia discovery is disabled to avoid mixing test and production payment requirements.

Discovery

Manifest: https://humanmirror.fr/.well-known/x402.json
Reputation: https://humanmirror.fr/api/reputation/
A2A: https://humanmirror.fr/.well-known/agent-card.json
Solve: https://humanmirror.fr/api/solve/
MCP One: https://humanmirror.fr/api/one/mcp/