A payment rail your agent can find without you

AgentQubit — Fri, 13 Nov 2026 00:33:22 +0000

Most "AI + crypto" projects are built for a human with a wallet and a browser tab. An agent has neither. It has an HTTP client, a JSON parser, and a task.

So the first thing AQB ships is not a landing page — it is /.well-known/agent-coin.json.

curl -s https://yss787976-ai.github.io/agent-coin/.well-known/agent-coin.json

That returns chain id, token, vault, registry and pool addresses, plus a card hash the agent can verify. No sign-up, no dashboard, no email.

Why an agent needs a token at all

Agent-to-agent work has a settlement problem. Cards need a human. Bank rails need KYC. Most stablecoins assume a person holds the keys.

AQB is a fixed-supply (900e9) ERC-20 on Base where every unit is backed 1:1 by USDC sitting in an on-chain vault. Minting happens against deposited USDC, redemption burns the token and returns the USDC. There is no oracle and no algorithmic peg to break.

Transfers are gated: a token transfer only succeeds to a registered agent or a whitelisted pool. That keeps the holder set machine-shaped instead of becoming a wallet-dust collection.

Post-quantum by default

Harvest-now-decrypt-later is a real risk for long-lived agent identities. Registration uses ML-DSA-65 (FIPS 204) keys; payers are derived as ML-KEM-768 stealth addresses, so a payment does not leak a static receiving key. An ECDSA fallback path exists so agents on ordinary wallets are not locked out.

The loop

npx -y @aqb-foundation/aqb-agent --help          # tools
npx @aqb-foundation/aqb-agent register --pq      # once
npx @aqb-foundation/aqb-agent pay --to 0xAGENT --amount 0.25 --memo "ocr batch"
npx @aqb-foundation/aqb-agent redeem --amount 0.25

The same tools are exposed over MCP:

{ "mcpServers": { "aqb": { "command": "npx", "args": ["-y", "@aqb-foundation/aqb-agent", "mcp"] } } }

It is listed in the official MCP registry as io.github.yss787976-ai/aqb-agent.

What is honest about it so far

Liquidity is small (a few hundred dollars). Treat it as a working rail, not a market.
Contracts are source-verified on BaseScan and Sourcify, MIT, 6 of them, but the project is days old.
There is no fiat off-ramp. USDC in, USDC out.

If your agent pays for API calls, OCR, translation or compute, the interesting part is not the token — it is that discovery, payment and redemption all fit in one script with no human in the loop.

Repo: https://github.com/yss787976-ai/agent-coin
Discovery: https://yss787976-ai.github.io/agent-coin/for-agents/

DEV Community: AgentQubit

A payment rail your agent can find without you

Why an agent needs a token at all

Post-quantum by default

The loop

What is honest about it so far