FAQ

Still stuck? Start on the tx inspector, try demo mode, or read the API docs.

What is agentbits in one sentence?

A read-only inspector and JSON API that turns Taiko transaction hashes and Uniswap v4 hook addresses into human summaries plus agentSummary strings for MCP / LLM tools — with honest source: rpc | fixture labels.

How is agentbits different from taiko-explorer MCP?

The official taiko-ai taiko-explorer server is built for depth: fetch ABIs, decode calldata with contract interfaces, static analysis. agentbits is built for narrative safety: dual Human / Agent panels, stable one-line summaries, demo fixtures, and v4 hook bit grids — so agents can cite Taiko activity without inventing semantics. Use both: explorer for raw decode, agentbits for explainable copy.

Do I need taiko-ai installed to use agentbits?

No. agentbits runs standalone (npm run dev on port 3004). In production agent workflows you will often run taiko-ai and agentbits side by side — taiko-ai for data and bridge paths, agentbits for “what did this tx mean?” See the About comparison table.

What is Demo fixture vs Decode live RPC?

Demo fixture returns a deterministic sample transfer — instant, no network, labeled source: fixture. Use it for screenshots, CI, or when RPC is down. Decode live RPC calls Taiko JSON-RPC for a real hash and labels source: rpc. Never mix them up in grant or user-facing copy.

Which networks are supported?

Taiko mainnet (chain ID 167000, Taikoscan) and Taiko Hoodi (167013, Hoodi explorer). Pick the network in the inspector or pass network=mainnet|hoodi to the API.

How do v4 hook addresses work?

Uniswap v4 encodes which lifecycle callbacks a hook may implement in the lowest 14 bits of the hook contract address — not in storage you read separately. Example: address ending in …0080 → mask 0x0080 → beforeSwap. Try the Hook decoder. Always verify bytecode onchain; bits only describe declared permissions.

Can I share a decode with a link?

Yes. Transactions: /?hash=0x…&network=mainnet. Demo: /?demo=1&network=mainnet. Hooks: /hooks?address=0x…. The page auto-runs decode when the URL loads.

How do agents call agentbits programmatically?

Use the HTTP API (GET /api/decode, GET /api/hook, GET /api/health) or run the stdio MCP server (npm run mcp) with tools decode_taiko_tx and decode_v4_hook. Prefer the agentSummary field in LLM context; keep explorerUrl for human verification.

Which RPC endpoints does agentbits use?

Defaults: https://rpc.mainnet.taiko.xyz and https://rpc.hoodi.taiko.xyz. Override with TAIKO_MAINNET_RPC and TAIKO_HOODI_RPC in .env.local (see .env.example).

Is wallet connection required?

No. Everything is read-only via JSON-RPC and local decode logic. agentbits never asks for private keys or sends transactions.

Will you add ERC-8004 agent registry support?

Not in the current MVP UI. ERC-8004 (onchain agent identity) is a natural follow-up for grant-funded work: decode registry registrations and agent metadata txs on Taiko once the ecosystem matures — still read-only.

Is this TaikoProofs or a swap bot?

Neither. TaikoProofs focuses on ZK proving / batch visualization. DeFi-Cli-style tools execute swaps for agents. agentbits only explains txs and hook permission bits — it does not prove blocks or trade.

Where is the source code?

This repository is MIT licensed. Set NEXT_PUBLIC_AGENTBITS_REPO in .env.local to show a GitHub link in the footer. Integration notes live in docs/agent-integration.md and skills/agentbits/SKILL.md.

Not affiliated with Taiko Labs · Complements taiko-ai