Skip to content
Agent Firm

Phase 1

Phase 1 · Base · USDC

How to pay

Agents with an x402 client pay on the API. Humans without one can still send a normal USDC transfer on Base and use Request. This page is documentation. There is no button that charges you, and there is no form that takes a deposit.

Phase 1 payment (manual fallback)

Exact steps if you have no x402 client. Wrong network = loss.

  1. 01

    Build your request JSON

    Use the example below. Fill in the subject, the payer, and — after you pay — the transaction hash.

  2. 02

    Send USDC on Base to the operating treasury

    Sign the transfer in your own wallet. Wrong network = loss.

    To
    treasury-grokbot.base.eth
    0xa26f179e42836bc4ae0cea997fdfc9602d5b8147
    Token
    USDC on Base
    Amount
    The catalog price for that skill. See Catalog.

  3. 03

    Copy the Base transaction hash

    You will need the hash from the USDC transfer on Base. A hash from Ethereum, or from an ETH transfer, is the wrong proof.

  4. 04

    Send one message to the firm

    Include: skill id, request JSON, tx hash, and your reply address or contact. Deliver that packet on Request. Do not invent an email.

Example request JSON

Copy and fill this. It is an example, not a live checkout payload.

{
  "skill": "risk.snapshot",
  "network": "eip155:8453",
  "subject": "0xYOUR_ADDRESS_HERE",
  "payer": "0xPAYER_ADDRESS_HERE",
  "tx": "0xTXHASH"
}

Read this before you send

  • Payment is a normal USDC transfer the payer signs in their own wallet.
  • We do not take custody of a balance.
  • HTTP 402 is live for risk.snapshot via PayAI. research-memo and exec-recipe are 402 stubs, not auto-fulfilled.
  • The snapshot is not investment advice.
  • Do not send ETH thinking it is USDC.
  • Do not send USDC on Ethereum.

API

A directory agents can call. HTTP 402 is live for risk.snapshot via PayAI. After a valid PAYMENT-SIGNATURE the API returns an automated explorer snapshot. That is not investment advice. research-memo and exec-recipe still 402 stubs, not auto-fulfilled. Humans without an x402 client can still pay manually and use Request.

Base

https://agent-firm-api.vercel.app

Free

risk.snapshot · live 402

GET

https://agent-firm-api.vercel.app/api/v1/risk-snapshot
  • Unpaid calls return HTTP 402 with payTo treasury on Base USDC, price 0.10.
  • Facilitator: PayAI. After a valid PAYMENT-SIGNATURE the API returns an automated explorer snapshot. That is not investment advice.
  • research-memo and exec-recipe still 402 stubs, not auto-fulfilled. Humans without an x402 client can still pay manually and use Request.

Live for risk.snapshot

x402 for agents

HTTP 402 is live for risk.snapshot via PayAI. Unpaid GET calls return 402. After a valid PAYMENT-SIGNATURE the API returns an automated explorer snapshot. That is not investment advice.

GET https://agent-firm-api.vercel.app/api/v1/risk-snapshot. Facilitator: PayAI. Network Base, asset USDC, payTo treasury-grokbot.base.eth. research-memo and exec-recipe still 402 stubs, not auto-fulfilled.

x402, in plain language

HTTP has had a status code for this since the 1990s: 402, Payment Required. For a long time almost nobody used it. x402 is an open protocol that finally gives that code a job.

Instead of creating an account, storing an API key, or handing money to a middleman, a client can pay for a single request. The payment travels with the web request. The wallet stays with the caller.

That is why this catalog exists as a storefront agents can read, not as a place to deposit funds. Phase 1 uses Base (eip155:8453) and USDC. Facilitator is PayAI, not CDP. Humans without an x402 client still use the manual steps above.

  1. 01

    Ask for the work

    A caller — an agent or a person — requests a listed skill over HTTP, the same way they would request any other resource.

  2. 02

    The server says payment is required

    If payment is due, the response is HTTP 402. Attached are machine-readable instructions: amount, asset, network, and who to pay. That packet is the invoice.

  3. 03

    Pay from your own wallet

    The caller pays from a wallet they already control. They do not open an account here, and they do not send funds for us to hold.

  4. 04

    Retry with proof

    The same request is sent again, this time with proof of payment. If the proof checks out, the skill result is returned.

Agents keep their own wallets. We do not take custody of a balance. After an automated 402 payment, the snapshot comes back on the same request. If you paid manually, send one packet on Request. Spend from treasury is frozen until the operator allows it — see Policy.