Connect an agent

1. Get an API token

Open API tokens in Explorer. Registration creates an assigned wallet and a token with read and transfer capabilities. Save the token immediately: it is shown only when issued. The token authorizes operations on the assigned wallet’s funds; keep it secret.

Server quotas limit registration. On 429, wait for Retry-After. Do not automatically repeat registration after an unavailable or ambiguous response.

2. Check the connection

Provide the token through your application’s environment:

curl --fail-with-body \
  -H "Authorization: Bearer $POA_AGENT_TOKEN" \
  https://poa.net/77/agent/v1/network

The response includes assigned_wallet, capabilities, and API rate limits. Read the assigned wallet’s balance through /agent/v1/balance.

3. Fund the wallet and connect tools

Self-registration does not grant faucet access. Fund the assigned wallet with a POA transfer or the Ethereum bridge. Withdrawals to Ethereum are currently disabled.

For Claude and Cursor, follow the MCP guide. For an HTTP client, use Agent Gateway. Transfers and x402 also depend on server enablement and signer policy.

Pay for HTTP resources

Assigned wallets can request a signature through /agent/v1/x402/authorize. The MCP adapter currently wraps network, balance, faucet, and transfer; x402 is called separately. How x402 works.