Taiko · Type-1 EVM · Agents

About agentbits

Open-source, read-only infrastructure that explains what happened on Taiko — for people and for the agents that assist them.

The problem we solve

Taiko is a Type-1 based rollup EVM (mainnet chain 167000, Hoodi testnet 167013). Agents can already fetch balances, ABIs, and calldata through official tooling — but they often mis-explain what a transaction did or what a v4 hook address permits.

agentbits adds a narrow, trustworthy layer: paste a transaction hash or hook address, get a human-readable story plus machine-friendly fields — always with a source badge (rpc vs fixture).

Who it is for

Grant reviewers & educators
Demo fixtures work offline; live RPC decodes are labeled honestly with source badges.
Agent builders
Stable JSON and compact agentSummary strings for Cursor / Claude MCP workflows on Taiko.
Hook & dApp developers
Decode v4 hook permission bits from deploy addresses before you trust lifecycle callbacks.

What you can do today

Tx inspector — decode mainnet or Hoodi txs via JSON-RPC; see status, selector labels (ERC-20, Universal Router, multicall, and more), value in ETH, and Taikoscan links.
Hook decoder — read the lowest 14 bits of a Uniswap v4 hook deploy address (e.g. mask 0x0080 → beforeSwap).
HTTP API — documented JSON with stable agentSummary and humanSummary fields.
MCP server — stdio tools decode_taiko_tx and decode_v4_hook (see README).

How agentbits fits next to taiko-ai

taiko-ai is the official MCP stack for Taiko: bridge quotes, balances, and taiko-explorer (ABI fetch, calldata decode, static analysis). agentbits does not replace that stack — it adds explainability and safety-oriented copy agents can cite without inventing swap routes or permissions.

Question	taiko-ai / explorer	agentbits
What is my balance?	✓	—
Decode calldata with contract ABI	✓	partial (selector labels)
Plain-English + agentSummary narrative	—	✓
v4 hook address bit grid	—	✓
Offline demo fixture for screenshots	—	✓

More detail in the FAQ.

What agentbits is not

Not a wallet, signer, or bridge UI — no keys, no custody.
Not a DEX or swap executor (see DeFi-Cli and similar agent swap tooling elsewhere).
Not TaikoProofs — we do not visualize ZK proving batches or prover dashboards.
Not a replacement for Taikoscan — we link out for full receipts and logs.

Honesty & open source

Live decodes call Taiko JSON-RPC (configurable via TAIKO_MAINNET_RPC / TAIKO_HOODI_RPC). Demo mode uses a deterministic fixture and never pretends to be on-chain data. The project is MIT licensed and not affiliated with Taiko Labs.

A funded grant phase would add public hosting, deeper Taiko-specific decoders, and tighter taiko-ai integration docs — without changing the read-only scope.

Official references

MIT licensed · Not affiliated with Taiko Labs · Complements public taiko-ai repositories.