Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

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://agent-docs-1e97d0hf1-taikoxyz.vercel.app/SKILL.md and deploy a contract to Taiko"

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 — Osaka EVM notes (what differs from Ethereum) 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.md containing every address, RPC URL, and command pattern an agent needs.
  • Machine-readable docs. Vocs auto-generates llms.txt, llms-full.txt, and .md variants 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
ResourceURLUse
Agent skill file/SKILL.mdOne-file reference for agents
Docs index/llms.txtPage listing with descriptions
Full docs/llms-full.txtEntire site as plain text
Any page as markdownAppend .md to any page URLRaw markdown for any page

Registering Agents on Taiko

Taiko supports ERC-8004 on both Taiko and Taiko Hoodi, contract addresses for IdentityRegistry and ReputationRegistry can be found here.

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

  • Pass --broadcast. Without it, forge create only simulates the deployment and nothing lands on-chain. This is the most common reason a "successful" deploy has no contract.
  • Test on Hoodi first. Chain ID 167013, RPC https://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. Taiko runs the Osaka EVM, and builds for older targets also run. Set evm_version = "osaka" (solc 0.8.29 or newer) via FOUNDRY_PROFILE=taiko to use CLZ, P256VERIFY, and the BLS12-381 precompiles from Solidity and to keep verification metadata consistent.
  • Include SKILL.md in every prompt. Agents have no persistent memory of past sessions. Re-inject the skill file each time.