Tx Simulate
by x402engine.app in Onchain & crypto
x402engine — Simulate EVM transactions before sending — get gas estimates, execution traces, and revert reasons
https://x402engine.app/api/tx/simulate- Price
- $0.01
- per call in USDC
- Uptime
- 100%
- last 30 days
- Response time
- 293 ms
- 532 ms slowest 5%
- Last check
- Passed
- 2 h ago, next any minute now
Reliability
Status and outage history · Atom feed · Watch with other listings
How to call it
POST https://x402engine.app/api/tx/simulate
Each call costs $0.01 in USDC on Base, paid with the request over x402.
Run a free test callOne unpaid request, the way an agent sends it. You see the payment challenge it gets back. Nothing is charged.
Example request
From the listing.
POST https://x402engine.app/api/tx/simulate
content-type: application/json
{
"from": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"network_id": "1",
"to": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
"value": "0"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
data | string | No | Transaction calldata (hex string) |
from | string | Yes | Sender address |
gas | number | No | Gas limit |
network_id | string | Yes | Network ID (1=mainnet, 8453=Base, 10=Optimism, etc.) |
to | string | Yes | Recipient/contract address |
value | string | No | ETH value in wei |
Example response
The listing has no example response.
Call it from code
The curl command shows the payment challenge. The JavaScript and Python versions pay and call, and never pay more than $0.01.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://x402engine.app/api/tx/simulate' \
-H 'content-type: application/json' \
--data-raw '{"from":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","network_id":"1","to":"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48","value":"0"}'
# x402 v2 sends the challenge base64-encoded in the PAYMENT-REQUIRED header (v1 sends it in the body).
# To read the header:
curl -sS -g -o /dev/null -D - -X POST 'https://x402engine.app/api/tx/simulate' \
-H 'content-type: application/json' \
--data-raw '{"from":"0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045","network_id":"1","to":"0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48","value":"0"}' \
| grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decodeJavaScript: pay and call
// npm i @x402/fetch @x402/evm viem
import { wrapFetchWithPayment, x402Client } from "@x402/fetch";
import { registerExactEvmScheme } from "@x402/evm/exact/client";
import { privateKeyToAccount } from "viem/accounts";
// Pays at most $0.01 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.01" });
registerExactEvmScheme(client, { signer: privateKeyToAccount(process.env.EVM_PRIVATE_KEY) });
const pay = wrapFetchWithPayment(fetch, client);
// Not sure it's safe to pay? ToolVet checks it first for $0.005. Pay for that from a separate
// client: this one is capped at $0.01 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fx402engine.app%2Fapi%2Ftx%2Fsimulate&method=POST
const res = await pay("https://x402engine.app/api/tx/simulate", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"from": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"network_id": "1",
"to": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
"value": "0"
}),
});
console.log(res.status, await res.text());Python: pay and call
# pip install "x402[requests,evm]"
import os
from eth_account import Account
from x402 import x402ClientSync
from x402.http.clients import x402_requests
from x402.mechanisms.evm import EthAccountSigner
from x402.mechanisms.evm.exact.register import register_exact_evm_client
# Pays at most $0.01 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.01"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://x402engine.app/api/tx/simulate",
json={
"from": "0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045",
"network_id": "1",
"to": "0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48",
"value": "0",
},
)
print(res.status_code, res.text)Security scan
No findings
We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.
Recent checks
| When | Result | HTTP | Time | Price |
|---|---|---|---|---|
| 2 h ago | Passed | 402 | 223 ms | $0.01 |
| 6 h ago | Passed | 402 | 507 ms | $0.01 |
| 11 h ago | Passed | 402 | 187 ms | $0.01 |
| 15 h ago | Passed | 402 | 302 ms | $0.01 |
| 19 h ago | Passed | 402 | 359 ms | $0.01 |
Show 10 older checks
| 23 h ago | Passed | 402 | 319 ms | $0.01 |
| 27 h ago | Passed | 402 | 296 ms | $0.01 |
| 32 h ago | Passed | 402 | 288 ms | $0.01 |
| 36 h ago | Passed | 402 | 182 ms | $0.01 |
| 40 h ago | Passed | 402 | 336 ms | $0.01 |
| 44 h ago | Passed | 402 | 319 ms | $0.01 |
| 2 days ago | Passed | 402 | 293 ms | $0.01 |
| 2 days ago | Passed | 402 | 278 ms | $0.01 |
| 2 days ago | Passed | 402 | 265 ms | $0.01 |
| 3 days ago | Passed | 402 | 301 ms | $0.01 |