x402 trust layer for autonomous buyers

Before your agent pays another agent, make it verify the route.

_MAKO is a paid preflight API for agent commerce. Buyer agents send a target service, task, and max USDC budget. They get back a callable verdict, route plan, schema check, settlement readiness, and signed receipt.

View agent API Inspect x402 routes

RoutePOST /api/agent-commerce/verify

Price0.25 USDC

Railx402 on Base

buyer-agent x402 verifier

01 Target

Read .well-known/x402.json

02 Score

Price, schema, route, network

03 Plan

Return exact method, URL, body

04 Receipt

Hash or app-wallet signature

POST /api/agent-commerce/verify
payment: x402 exact 0.25 USDC

{
  "target_url": "https://agent.example",
  "intended_task": "buy governance data",
  "max_price_usdc": 0.25,
  "risk_mode": "strict"
}

Buyer agents Call with confidence

Know whether a paid endpoint is callable before spending budget.

Seller agents Prove readiness

Expose clean x402 metadata, schema, price, and settlement behavior.

Registries Add runtime proof

Use discovery as an input, then verify the specific route and task.

Built for agents, not dashboards.

The response is structured so another agent can decide, call, skip, or ask for a fallback without a human review step.

Request

{
  "target_url": "https://mako.pollinateresearch.com",
  "intended_task": "governance proposal signal",
  "max_price_usdc": 0.25,
  "required_output": "json",
  "risk_mode": "strict"
}

Response

{
  "verdict": "callable",
  "score": 100,
  "recommended_route": "GET /api/governance/proposal-signal",
  "price_usdc": 0.05,
  "schema_valid": true,
  "settlement_ready": true,
  "warnings": [],
  "call_plan": {
    "method": "GET",
    "url": "https://mako.pollinateresearch.com/api/governance/proposal-signal"
  },
  "receipt": {
    "message_hash": "0x42ed...",
    "signature_scheme": "sha256"
  }
}

Three ways agents use _MAKO.

Start with deterministic x402 checks. Add EigenCloud attestation and app-wallet signatures as the verifier hardens.

Paid route preflight

Buyer agent checks a target endpoint, price, network, schema, and Bazaar metadata before spending USDC.

Seller readiness monitor

Seller agents prove their endpoint is discoverable, protected, priced, and returning useful machine-readable metadata.

Vertical proof routes

Governance and treasury routes show what a verified paid agent should return: structured data, source links, and receipts.

Web3 trust surface

Payment first, verification immediately after.

_MAKO does not replace marketplaces. It checks a specific route for a specific buyer-agent task. The verifier currently returns deterministic receipts and is shaped for EigenCloud app-wallet signatures and verifiable execution.

Discovery.well-known/x402.json

Payment402 exact USDC

SchemaBazaar input/output

ReceiptHash or EIP-191 signature

Live _MAKO routes already fit the verifier.

These are agent-callable proof routes behind the same x402 surface.

Agent commerce Verifier API

Paid preflight for target x402 services. Returns verdict, route, score, warnings, and receipt.

Governance data Proposal signal

Low-cost route for agents that need recent Snapshot proposal metadata and urgency flags.

Ops data Treasury watch

Read-only public wallet analysis and signer context packets remain available for human teams.

Human buyer path

Need the DAO ops pilot instead?

Agents can buy the API routes directly through x402. Human teams can still start a Governance + Treasury Watch pilot with Base USDC checkout.

1. Scope governance sources and wallets 2. Pay exact Base USDC 3. Get a pilot packet for review