# Zerion API - Wallet Transaction Simulation

> Zerion API - Wallet Transaction Simulation is a paid API for AI agents from api.zerion.io, paid per call via x402, $0.01/call, status unknown (last checked 2026-10-01).

Simulates a blockchain transaction for a given wallet and chain, returning predicted outcomes before execution

## Facts

- Endpoint: POST https://api.zerion.io/v1/wallets/simulation/transaction?utm_source=zero.xyz
- Price: $0.01/call
- Payment: x402
- Status: unknown
- Last checked: 2026-10-01
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/zerion-api-wallet-transaction-simulation-c996c13f
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_ZECnAat_AsF-dW7iuhtDE

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 zerion-api-wallet-transaction-simulation-c996c13f -d '<json body>'
```

Example prompt: Before I submit this swap transaction on Ethereum mainnet (chain ID 1), can you simulate it for my wallet 0xAbC...123 and tell me what the expected outcome will be — token changes, approvals, and whether it's likely to succeed?

## When to prefer this

Use this endpoint when an AI agent or app needs to preview the outcome of a blockchain transaction before committing it on-chain — especially for DeFi swaps, NFT purchases, token approvals, or any high-stakes transaction where verifying expected results and safety is critical. Prefer this over live execution when the goal is risk assessment or user confirmation flows.

## Known failure modes

- Invalid wallet address format returns 400 bad request
- Unsupported chain ID returns 422 or error response
- Malformed transaction object causes simulation failure
- Network congestion or RPC timeout may cause 503
- Insufficient input fields (missing address or transaction) returns 400
- Transaction simulation itself may return a reverted/failed state in attributes

## How this service works

Interpreted wallet data for more than 40 chains and Solana: portfolios, DeFi positions, PnL, transactions and NFTs. REST for apps, x402 pay-per-call for agents.

## Output

Returns a JSON object with a data field containing a resource id, resource type, and attributes describing the predicted outcome of the simulated transaction — including expected state changes, token flows, and success/failure indicators — along with a self-referencing links object.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "address": {
   "type": "string",
   "description": "Wallet address"
  },
  "chain_id": {
   "type": "string",
   "description": "Chain ID"
  },
  "transaction": {
   "type": "object",
   "description": "Transaction to simulate"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "json",
 "example": {
  "data": {
   "id": "<resource id>",
   "type": "<resource type>",
   "attributes": {}
  },
  "links": {
   "self": "https://api.zerion.io/v1/..."
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/zerion-api-wallet-transaction-simulation-c996c13f/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from api.zerion.io](https://www.zero.xyz/host/api.zerion.io/llms.txt)