AGATE 1.0 · free check · no key, no gas

Is the arriving agent a customer or a scraper?

Merchants are blocking agents because a scraper and a buyer look identical at the firewall. AGATE answers the question in one free call: signed intent, wallet standing, delivered-work history. Then you decide whether to take the order, take the payment first, or refuse it.

Why a blocklist is the wrong answer

A block stops the scraper and loses the sale, because both arrive the same way. What a merchant actually needs is one bit it can act on: is this agent spending its own settled money, and has anyone paid it for work it delivered? That is what this returns.

Try it live

What you send

POST https://x402-agent-pay.com/agate/verify
Content-Type: application/json

{
  "agent": { "wallet": "0x...", "name": "shopper-agent" },
  "intent": { "action": "book_appointment",
              "target": "bright-angel-lodge",
              "amount_usdc": 0.10,
              "expires_at": "2026-11-16T20:15:00Z" },
  "signature": "0x...  EIP-191 personal_sign over the canonical intent string"
}

The signature is checked for free and costs no gas. Canonical string: AGATE1|<action>|<target>|<amount %.6f>|<expires_at epoch>|<wallet lowercase>

What you get back

{
  "decision": "allow_with_limit",
  "agent": { "tier": "UNTRUSTED" },
  "limits": { "max_usdc": 1.0, "requires_prepayment": true },
  "checks": [ { "id": "intent_signature", "status": "pass" }, ... ],
  "why": "Intent is sound but the wallet has no delivered-work history ...",
  "receipt": { "verify_id": "agate_...", "verify_url": "..." }
}

The three answers, and what to do with each

DecisionMeaningWhat the merchant does
ALLOWSigned intent from a wallet with delivered-work historyServe the request normally, settle after delivery
ALLOW WITH LIMITSound intent, thin history, or above the tier ceilingTake payment first, release the order after it clears
DENYA hard check failed: no signature, bad wallet, sybil flag, expired intentRefuse, and tell the agent which check failed

Ceilings: UNTRUSTED 1.00 USDC, STANDARD 5.00, TRUSTED 25.00 per transaction. A refusal is a diagnosis, not a wall: every deny names the check and what would fix it.

Wire it in

# before you fulfil
curl -s -X POST https://x402-agent-pay.com/agate/verify \
  -H 'Content-Type: application/json' \
  -d '{"agent":{"wallet":"0x..."},"intent":{"action":"book_appointment","target":"my-shop","amount_usdc":0.10}}'

# decision == allow            -> fulfil now
# decision == allow_with_limit -> require the x402 payment to clear first
# decision == deny             -> 403 with denied_by[]

How it sits next to the facilitator

Two different questions, both free to ask. AGATE answers should I trust this agent before it spends? The facilitator at x402-agent-pay.com/facilitator answers did this payment clear, and can I settle it? AGATE is the check before the money moves, the facilitator is the settlement after. You can use either alone, and they are cheaper together because a refusal never reaches the settlement step.

What it will not do

Machine-readable

Spec: /agate/spec · Receipts: GET /agate/verify?receipt=<verify_id> · AgentWorld native copy: agentworld.me/api/agate/verify