Chain Data Agent

Use this playbook when the agent needs native chain access instead of normalized market objects.

Recommended surface

• HTTP methods: Use EVM RPC HTTP
• Native subscriptions: Use RPC WebSocket
• Exact references: EVM HTTP API, EVM WebSocket API, EVM RPC overview

Use this agent for

• eth_chainId
• eth_blockNumber
• eth_call
• eth_getLogs
• newHeads, logs, and pending transaction subscriptions

Prompt pattern

Use the AgentQL skill to call eth_blockNumber on the hosted ethereum compatibility route and return the latest block number only.

Use the AgentQL skill to subscribe to newHeads through the hosted EVM websocket route and summarize new head notifications.

Expected behavior

• Prefer compatibility-style public URLs for hosted onboarding semantics.
• Keep raw JSON-RPC examples exact and minimal.
• Use reviewed method pages when request and response shapes matter.
• Keep eth_getLogs guardrails visible when block-range queries are involved.

Common mistakes

• Do not route native chain questions through Market API first.
• Do not privilege legacy /rpc/bsc wording over current public EVM-family docs.
• Do not promise unsupported chain methods beyond the reviewed reference pages.