Chain Simulation

blockchain

Serving

Pre-sign EVM transaction simulation: an eth_call with state overrides previewing the revert reason and asset deltas before you sign. POST /v1/chain with the call {to, data, ...} and get the outcome as one JSON object. Deterministic per state instant. Pay per request in USDC; no account, no API key.

Endpoint: POST https://agent.pocket.network/v1/chain-simulation
Price per call: $0.005 USD
Networks payable on: Base (eip155:8453)
Protocol: rest

Calling it

The first call returns 402 Payment Required with the terms. Sign for those terms and retry the same request with the payment attached.

Example request

Derived from the published request schema.

curl -X POST https://agent.pocket.network/v1/chain-simulation \
  -H 'content-type: application/json' \
  -d '{"to":"string","data":"string","from":"string","chain_id":0}'

Example response

This service declares its response shape in prose rather than as fields, so there is nothing more specific to sample.

{}

Try it

Make one real paid call from your own wallet — about $0.005 on Base (eip155:8453). The wallet signs; nothing here holds a key. You'll see exactly what the service answers.

No browser wallet found. Install MetaMask, Rabby, or Coinbase Wallet to try a call here.

EndpointRequest body

Supported methods

Methods the registry lists for this service. The portal forwards any call as sent; the supplier decides what it answers, and a delivered answer is settled.

Methods Chain Simulation accepts, and whether each reads or writes.
Method	Effect
`GET /v1/health`	read
`GET /v1/version`	read
`POST /v1/chain`	read

Schemas

Published by the service itself. The example above is generated from these.

Request schema

{
  "type": "object",
  "description": "The call to simulate before signing.",
  "properties": {
    "to": {
      "type": "string",
      "description": "Target contract address, 0x-prefixed."
    },
    "data": {
      "type": "string",
      "description": "Calldata, 0x-prefixed (0x for none)."
    },
    "from": {
      "type": "string",
      "description": "Optional sender address."
    },
    "chain_id": {
      "type": "integer",
      "description": "EVM chain id (default 1)."
    }
  },
  "required": [
    "to"
  ]
}

Response schema

{
  "type": "object",
  "description": "For POST /v1/chain, a JSON object with the simulated outcome: success or revert reason, asset deltas, and the chain_id. The exact shape is the service's own and is not pinned here; errors return a JSON object with an `error` field, and the GET routes return their own small JSON documents."
}

Request body used in the example: { "to": "string", "data": "string", "from": "string", "chain_id": 0 }