Pay in 60 seconds

A · Cheapest path — $0.01 (proven on-chain)

First external paid call is confirmed. Empty JSON {} is canary-safe (defaults to sample company 514744887). See /proof and BaseScan TX.

1. Inspect the challenge (expect HTTP 402)

   Do not pay yet — read the PaymentRequired terms.

   curl -i https://israel-counterparty-intelligence.vercel.app/v1/company-changes/mainnet \
     -H 'content-type: application/json' \
     --data '{}'

2. Pay with an x402 client, then retry

   Sign the returned terms with a buyer-controlled wallet and retry the identical POST. Cap is $0.01 USDC (atomic 10000).

B · Second canary — $0.05 (still open)

Demonstrates a non-one-shot path. second_external_paid_call is still null until an external payer settles and the operator persists SECOND_EXTERNAL_PAID_CALL_TX (env / Upstash) — /health does not auto-update from the chain alone.

1. Inspect the $0.05 challenge (expect HTTP 402)

   Atomic amount 50000 USDC units on Base.

   curl -i https://israel-counterparty-intelligence.vercel.app/v1/verify/mainnet \
     -H 'content-type: application/json' \
     --data '{"company_number":"514744887"}'

2. Settle with buyer wallet, never the receiver

   After a successful paid response, success is the product JSON. A later /health update for second_external_paid_call requires durable recording — do not assume instant public status.

What success looks like

• HTTP 200 with the paid product payload (not 402 / not 503). Challenge-only curls should return 402 until signed.
• On-chain USDC transfer to the receiving wallet on Base. First path already proven — /proof.
• Optional: /health may later show second_external_paid_call after env persistence. Today: checking…

Links

• /mcp.json MCP metadata · connect /mcp
• /health Machine-readable payment status
• /proof First external settle on BaseScan
• /x402-buyer-quickstart.md Longer buyer guide
• /trusted-wallet-guide.md Independent wallet route
• /agents.md Agent playbook