# Eth Call – Ink Network Contract Read

> Eth Call – Ink Network Contract Read is a paid API for AI agents from agent-data-tools.revmesh2074.workers.dev, paid per call via x402, $0.01/call, status unknown (last checked 2026-11-20).

Executes a read-only eth_call on the Ink (Kraken L2) blockchain, returning raw ABI-encoded output from any view or pure contract function without submitting a transaction.

## Facts

- Endpoint: GET https://agent-data-tools.revmesh2074.workers.dev/ink/call?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-11-20
- Activations on Zero: 0
- Provider: agent-data-tools.revmesh2074.workers.dev
- Website: https://agent-data-tools.revmesh2074.workers.dev
- Tags: x402
- Canonical page: https://www.zero.xyz/c/agent-data-tools-revmesh2074-workers-dev-eth-call-ink-network-9030bbbb
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_DrNx9dETS655NQL7gWXtH

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability agent-data-tools-revmesh2074-workers-dev-eth-call-ink-network-9030bbbb
```

Example prompt: Can you call the totalSupply view function on the USDC contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on Ink — use calldata 0x18160ddd — and tell me the raw result?

## When to prefer this

Use this endpoint when you need to read any arbitrary view or pure function on the Ink (Kraken L2) blockchain that does not have a dedicated higher-level tool available. It is ideal for reading token state (balances, supplies, allowances), querying DeFi protocol variables, or verifying contract state without broadcasting a transaction. Prefer dedicated endpoints (e.g. token supply or NFT balance tools) for common ERC-20/721 calls; use this for custom or less common contract functions on Ink specifically.

## Known failure modes

- 422 Unprocessable Entity — contract call reverted; response includes revert reason string
- Invalid `to` address format — malformed hex address causes a 400 error
- Invalid `data` field — malformed or truncated calldata may cause revert or bad decode
- Contract does not exist at address — call returns empty bytes (0x)
- Calldata exceeds 8 KB limit — rejected before execution
- Network latency or Ink RPC unavailability — may return 5xx temporarily

## How this service works

eth_call: read-only contract call on Ink at the latest block, without a transaction or gas: send ABI-encoded calldata, or a function signature such as balanceOf(address) with args and the call is encoded and its result decoded for you. Use to read any view function that has no dedicated tool (the example reads USDC totalSupply). Calldata up to 8 KB; a call that reverts is 422 with the reason, uncharged.

## Output

Returns a JSON object containing the hex-encoded result of the contract call (`result`), the block number at which the call was executed (`block`), the chain name (`chain`), the chainId, the number of result bytes (`resultBytes`), and echoed-back `to` and `data` fields. If the call reverts, returns HTTP 422 with the revert reason (and no charge).

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "required": [
  "to",
  "data"
 ],
 "properties": {
  "to": {
   "type": "string",
   "description": "0x contract address to call"
  },
  "args": {
   "type": "string",
   "description": "Arguments for a function signature in data: comma separated, or a JSON array for arrays and tuples"
  },
  "data": {
   "type": "string",
   "description": "0x ABI-encoded calldata (4-byte selector plus arguments), or a function signature: totalSupply(), balanceOf(address), or with its result types, balanceOf(address) returns (uint256)"
  },
  "from": {
   "type": "string",
   "description": "Optional 0x sender address for calls that check msg.sender"
  },
  "returns": {
   "type": "string",
   "description": "Result types to decode when data is a signature without them, for example uint256 or address,uint8"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "to": {
   "type": "string"
  },
  "data": {
   "type": "string"
  },
  "block": {
   "type": "number"
  },
  "chain": {
   "type": "string"
  },
  "result": {
   "type": "string"
  },
  "chainId": {
   "type": "number"
  },
  "resultBytes": {
   "type": "number"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/agent-data-tools-revmesh2074-workers-dev-eth-call-ink-network-9030bbbb/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from agent-data-tools.revmesh2074.workers.dev](https://www.zero.xyz/host/agent-data-tools.revmesh2074.workers.dev/llms.txt)
