FOR AI AGENTS · BOT OPERATORS · MCP AND x402 BUYERS

Buy only the agent check you need.

Before your agent moves money, writes data or calls a consequential tool, assess the proposed action. HumanMirror provides bounded policy/risk screening and evidence tools. It does not control your wallet or authorize actions on your behalf.

Three steps to an auditable call

01 · DISCOVER

Inspect the contract

Check the documented request schema, pricing and network. Read the live 402 payment challenge before authorizing funds. Verify the payTo address and requested asset against your own allowlist.

Machine-readable service manifest ↗
02 · DECIDE

Apply your own limits

Start with Safe Preflight for a proposed action. Use your own spend caps, policy and human authorization. A returned ALLOW is a bounded advisory decision, not a guarantee of economic, contractual or execution safety.

Preflight product and example ↗
03 · VERIFY

Keep the result

Preserve your normalized input, payment evidence, idempotency key (when supported), result and proof fields. Verify any receipt separately. Never assume payment settlement means an action's output has been delivered.

Developer documentation ↗

Pricing without a sales call

Safe Preflight is published at 0.010 USDC on Base through x402. Other machine routes have their own published prices. The HTTP 402 response and current service manifest are authoritative for a specific paid request.

Inspect payment terms without a wallet

Before buying, send a synthetic POST to /api/x402/safe-preflight/ with Content-Type application/json and a body containing the required input field. Do not attach PAYMENT-SIGNATURE or credentials. Inspect any returned HTTP 402 terms, recipient, network, asset and amount against your independently approved policy. A 402 inspection does not authorize a purchase or prove delivery. The published schema is at OpenAPI. A paid-but-undelivered incident is documented in issue 695.

If a paid response is interrupted

Keep the original HTTP method, resource URL, normalized JSON request, Idempotency-Key (if supplied), payer, network, asset, amount, payTo, authorization nonce and its validity window. Keep the payment response or transaction hash only if you actually received one; a timed-out buyer may have neither. Never generate a new payment authorization just to recover a lost response.

Existing replay option: where the paid route supports the Idempotency-Key contract, resend the identical method, URL, request body and original Idempotency-Key without PAYMENT-SIGNATURE or X-PAYMENT. A completed saved result may be returned with X-HumanMirror-Idempotent-Replay: true. An in-progress operation may respond 409 with Retry-After; an unknown result may return a new 402. Neither response proves the original authorization has settled, and a new 402 is not permission to pay again.

Important limit: recovery using payer + EIP-3009 nonce alone is not currently documented as a supported HumanMirror retrieval API. If your buyer lost its Idempotency-Key, record the nonce and ask support to reconcile the settlement and delivery separately. A settled payment is not proof of a completed verdict or delivered application result. A used authorization alone is not proof that the application result was delivered. Do not retry an expired market action or release wallet funds without your principal's renewed authorization.

Contact HumanMirror support ↗

Building a customer-owned agent swarm?

OmniDome provides agent discovery and separately scoped components for customer-authorized collaboration. Hosted cross-customer autonomous execution must be verified independently; a local or synthetic test is not a claim of customer adoption.

Explore OmniDome ↗