B20 activation check
GET /api/b20-activation-checkIs B20 live on Base mainnet? Send GET /api/b20-activation-check with no required fields (1 optional) and pay $0.002 per call over x402 or MPP (there is no free tier). It returns a JSON object with registry and features.
Queries the Activation Registry precompile for base.b20_asset and base.b20_stablecoin (or a custom feature id). Honest pre-launch too: reports not-activated until the registry flips.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
feature | string | no | optional: a single feature string to check (default: both known B20 features) |
Example request
curl -i "https://agent402.tools/api/b20-activation-check"
Without payment this returns HTTP 402 Payment Required with the exact price for b20-activation-check; any x402 v2 or MPP client pays it and retries.
Watch a call get paid
GET /api/b20-activation-check$0.002 USDCPAYMENT-SIGNATUREon 14 chains200 OKAgent402-ReceiptEd25519Example response
{
"registry": "0x8453000000000000000000000000000000000001",
"features": [
{
"feature": "base.b20_asset",
"featureId": "0xcdcc…",
"activated": false
}
]
}| Field | Type | Always present | In the example |
|---|---|---|---|
registry | string | yes | 0x8453000000000000000000000000000000000001 |
features | array of objects | yes | 1 item in the example |
From an MCP client
catalog.call {
"slug": "b20-activation-check",
"params": {}
}The hosted connector at https://agent402.tools/mcp needs a payment for b20-activation-check; the stdio package pays it from a wallet or from an AGENT402_CREDITS_KEY issued earlier. Local install: npx -y agent402-mcp@0.14.0.
Errors and behavior
- Every field is optional. An input the tool rejects returns an HTTP 4xx whose body carries
error,tool,expected,requiredandexample. - A paid call that ends in any status of 400 or above is not charged over x402, MPP or a prepaid credits key: settlement runs after the tool and only on a successful response. The exception is a Tempo push credential, a transfer the buyer sent before the call: it settles before the tool runs, so if the tool then fails the payment is recorded as a refund owed to the paying wallet.
- Wallet-only: this tool reaches the network or stored state, so it has no proof-of-work tier. A prepaid card-credits key issued earlier (
Authorization: Bearer a402_...) also pays it. - A
POSTwith a JSON body to /api/b20-activation-check is served as this GET, with the body as the input. - An
Idempotency-Keyheader makes a retried paid call replay the first 200 instead of charging again (an answer larger than 1 MB is not replayed).
Paid call (JavaScript agent)
import { wrapFetchWithPayment } from "@x402/fetch";
import { x402Client } from "@x402/core/client";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
const client = new x402Client();
client.setSpendControls?.({ maxAmountPerPayment: "$0.002" }); // refuse any quote above this tool's price
registerExactEvmScheme(client, { signer: privateKeyToAccount(KEY) });
const payFetch = wrapFetchWithPayment(fetch, client);
const res = await payFetch("https://agent402.tools/api/b20-activation-check");Related tools
B20 feature id
Pure-CPU helper: turn a B20 feature string (e.g. base.b20_asset) into its bytes32 feature id and ready-to-send.
New B20 tokens
Recently deployed B20 tokens on Base: scans the factory's B20Created logs over a block window, locates each new token.
Verify B20 token
Boolean verdict with reasons: is this address a real factory-issued B20 on Base?
B20 payment memos
Payment memos attached to B20 transfers: pairs each Memo(address,bytes32) log with its Transfer at the previous log.
B20 token info
ERC-20 metadata plus B20 signals for any Base address: name, symbol, decimals, total supply, best-effort paused/cap.
Audit report (one wallet's paid history, signed)
An audit report of your own wallet's paid history here, ready to hand to an auditor: every paid call over a window of up.