Agent Quickstart
Give your AI agent everything it needs to deploy contracts, bridge tokens, and interact with Taiko.
One prompt
Claude Code
claude -p "Read https://docs.taiko.xyz/SKILL.md and deploy a contract to Taiko"If you are an LLM reading this page, fetch https://docs.taiko.xyz/SKILL.md for the complete agent reference, or read https://docs.taiko.xyz/llms-full.txt for all documentation.
What the agent gets
The SKILL.md file gives your agent:
- Network config — RPC endpoints, chain IDs, and explorer URLs for mainnet and testnet
- Contract addresses — Bridge, ERC20Vault, SignalService, token contracts on L1 and L2
- EVM compatibility — Shanghai version requirements and Foundry profile configuration
- Common tasks — Deploy, verify, bridge, read state — with copy-paste commands
- Behavioral rules — Correct defaults so the agent doesn't guess wrong
Why Taiko is agent-friendly
- Standard EVM tooling. Foundry, Hardhat, viem, ethers.js all work out of the box. No custom plugins or SDKs required.
- SKILL.md. A single file at
/SKILL.mdcontaining every address, RPC URL, and command pattern an agent needs. - Machine-readable docs. Vocs auto-generates
llms.txt,llms-full.txt, and.mdvariants of every page for LLM consumption. - Sub-cent transaction fees. Agents can transact frequently without burning through budgets — ideal for high-volume, autonomous workflows.
- 2-second block times. Fast finality keeps agents responsive, with 1-second blocks coming soon.
Machine-readable docs
Every page is available as raw Markdown by appending .md to the URL:
/quickstart/deploy.md| Resource | URL | Use |
|---|---|---|
| Agent skill file | /SKILL.md | One-file reference for agents |
| Docs index | /llms.txt | Page listing with descriptions |
| Full docs | /llms-full.txt | Entire site as plain text |
| Any page as markdown | Append .md to any page URL | Raw markdown for any page |
Registering Agents on Taiko
Taiko supports ERC-8004 on both Taiko Alethia and Taiko Hoodi, contract addresses for IdentityRegistry and ReputationRegistry can be found here.
Tack: IPFS storage for agents
Tack is an agent-native IPFS pinning and retrieval service. One endpoint, no API keys, no accounts — your agent can store and retrieve files autonomously using x402 micropayments.
Get started with Tack →Starter prompts
Try these with your agent after loading the skill:
- "Deploy a Counter contract to Taiko Hoodi testnet"
- "Bridge 0.1 ETH from Ethereum to Taiko using cast"
- "Add Taiko mainnet and testnet to my wagmi config"
- "What's different about Taiko compared to Ethereum?"
- "Verify my contract at 0x... on Taikoscan"
Best practices
- Always use
FOUNDRY_PROFILE=taiko. This ensures Shanghai EVM compilation. Forgetting this is the most common deployment failure. - Test on Hoodi first. Chain ID
167013, RPChttps://rpc.hoodi.taiko.xyz. Use testnet for iteration before mainnet deployment. - Verify addresses against SKILL.md. Contract addresses can change across upgrades. Always fetch the latest SKILL.md rather than relying on cached values.
- Pin the EVM version. Even if your Solidity version supports Cancun, Taiko requires Shanghai. Always set
evm_version = "shanghai". - Include SKILL.md in every prompt. Agents have no persistent memory of past sessions. Re-inject the skill file each time.