# EVM Smart Contract Read Call

> EVM Smart Contract Read Call is a paid API for AI agents from 194-28-85-99.sslip.io, paid per call via x402, $0.001/call, status down (last checked 2026-11-17).

Executes a read-only call to an EVM smart contract function on a specified chain and returns the decoded result

## Facts

- Endpoint: GET https://194-28-85-99.sslip.io/api/v1/evm/call?utm_source=zero.xyz
- Price: $0.001/call
- Payment: x402
- Status: down
- Last checked: 2026-11-17
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/evm-smart-contract-read-call-fd67263d
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_M2kUU_guuo1I4rL4Aiq6g

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 evm-smart-contract-read-call-fd67263d
```

Example prompt: Can you call the totalSupply() function on the USDC contract at 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 on the Base chain and give me the decoded result?

## When to prefer this

Use this endpoint when you need to query on-chain EVM smart contract state without signing a transaction — ideal for reading balances, supplies, prices, or any view/pure function. Prefer this over generic blockchain RPC providers when you want a pay-per-call model with no API key setup and automatic x402 payment support. Best for autonomous agents that need on-demand contract reads across multiple EVM chains including Base.

## Known failure modes

- Invalid contract address returns an error or empty result
- Unsupported chain identifier causes a 400 error
- Malformed function signature (sig) causes decoding failure
- Arguments (args) not matching function ABI cause revert
- Block number too far in the past may be unavailable depending on node
- Payment not provided or invalid signature causes HTTP 402 response
- Signature reuse or expired tx age causes payment rejection

## How this service works

Crypto market data and web tools for autonomous agents: read web pages, PDFs and YouTube transcripts, check domains and tokens. Every `/api/v1/*` call is paid per call: **$0.003** for simple reads, **$0.005-$0.01** for aggregates, **$0.02-$0.03** for token risk checks and reports (USDC or USDT). Each route's price is in `x-payment-info`.

**x402 agents:** pay automatically. The 402 response carries a standard `PAYMENT-REQUIRED` header (x402 v2, USDC on Base or Solana, USDT on Solana); retry with `PAYMENT-SIGNATURE`.

**Manual (legacy) flow:** call the endpoint, read the HTTP 402 JSON (`pay_to`, `asset`, `price`), send the USDT transfer, then repeat the call with header `X-Payment-Tx: <signature>`. One signature pays for one call; signatures older than the `max_tx_age_seconds` value are rejected.

Machine-readable spec: `/openapi.json`. LLM summary: `/llms.txt`. MCP server: `POST /mcp`.

## Output

Returns a JSON object containing the chain identifier, decoded return values as an array, the function signature called, the 4-byte selector, and the raw hex result from the contract call.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "$schema": "https://json-schema.org/draft/2020-12/schema",
 "required": [
  "input"
 ],
 "properties": {
  "input": {
   "type": "object",
   "required": [
    "type",
    "method"
   ],
   "properties": {
    "type": {
     "type": "string",
     "const": "http"
    },
    "method": {
     "enum": [
      "GET"
     ],
     "type": "string"
    },
    "queryParams": {
     "type": "object",
     "required": [
      "to",
      "sig"
     ],
     "properties": {
      "to": {
       "type": "string"
      },
      "sig": {
       "type": "string"
      },
      "args": {
       "type": "string"
      },
      "block": {
       "type": "string"
      },
      "chain": {
       "type": "string"
      },
      "returns": {
       "type": "string"
      }
     }
    }
   },
   "additionalProperties": false
  },
  "output": {
   "type": "object",
   "required": [
    "type"
   ],
   "properties": {
    "type": {
     "type": "string"
    },
    "example": {
     "type": "object"
    }
   }
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "chain": "base",
  "decoded": [
   4123456789012345
  ],
  "function": "totalSupply()",
  "selector": "0x18160ddd",
  "result_hex": "0x..."
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/evm-smart-contract-read-call-fd67263d/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from 194-28-85-99.sslip.io](https://www.zero.xyz/host/194-28-85-99.sslip.io/llms.txt)
