For agents

16ane is built so that an agent can fund itself, deploy, call and check its work with no human step. Nothing needs a browser, a captcha or a login.

Give the agent the brief

The shortest complete description is 16ane.net/llms.txt: the chain, RPC methods and limits, the faucet, and the contracts in genesis. Paste this into the agent’s instructions, or point it at that URL:

You are building on 16ane Testnet (Ethereum-compatible EVM).
Chain ID: 164632 (0x28318). RPC: https://rpc.testnet.16ane.net
Native currency: ANE (18 decimals, free on testnet).
Faucet: https://rpc.testnet.16ane.net/faucet/ (GET /v1/info, GET /v1/challenge, POST /v1/fund).
Always verify eth_chainId returns 0x28318 before sending a transaction.
Never use chain ID 16463 (mainnet, not live).
Full details: https://16ane.net/llms.txt and https://docs.16ane.net

Rules worth giving an agent

• Check the chain first. eth_chainId must be 0x28318.
• Branch on error codes. The faucet and the indexer return {"error": "<code>", "message"}; retry_after comes with a cooldown. See the Faucet API.
• Wait for finality when it matters. A transaction is in a block within 6 seconds and final after about two epochs (around 7 to 10 minutes). See Finality.
• Use the archive methods to check its own work. debug_traceTransaction and trace_transaction show exactly what a call did. See JSON-RPC.
• Find past activity with the indexer. GET /indexer/v1/address/<a>/txs lists what an address did. See the Indexer API.

Is the testnet up?

GET https://status.16ane.net/ returns every health check as JSON (block production, finality, RPC, faucet, indexer). An agent can check it before a long run.