80trust / 100

Decode

by automaton-tx-explainer.vercel.app in Onchain & crypto

x402 APIPassing, checked 2 h ago

Decode EVM calldata before signing: function signature candidates (openchain DB), decoded args, and plain-English warnings for approve/setApprovalForAll/permit/unlimited amounts.

GET
https://automaton-tx-explainer.vercel.app/v1/decode
Price
$0.005
per call in USDC
Uptime
100%
last 30 days
Response time
235 ms
393 ms slowest 5%
Last check
Passed
2 h ago, next any minute now

Run a free test callHow to call it

Reliability

All checks passedSome failedAll failedNot checked

Status and outage history · Atom feed · Watch with other listings

How to call it

GET https://automaton-tx-explainer.vercel.app/v1/decode

Each call costs $0.005 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.

GET https://automaton-tx-explainer.vercel.app/v1/decode?data=0x095ea7b3000000000000000000000000000000000022d473030f116ddee9f6b43ac78ba3ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff

Parameters

ParameterTypeRequiredDescription
datastringYeshex calldata (0x + selector + args)

Example response

The provider's example. We can't check it without paying.

{
  "bestMatch": {
    "args": [
      "0x...",
      "115792..."
    ],
    "signature": "approve(address,uint256)"
  },
  "selector": "0x095ea7b3",
  "warnings": [
    "Unlimited approval amount"
  ]
}

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.005.

curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i 'https://automaton-tx-explainer.vercel.app/v1/decode?data=0x095ea7b3000000000000000000000000000000000022d473030f116ddee9f6b43ac78ba3ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff'

# 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 - 'https://automaton-tx-explainer.vercel.app/v1/decode?data=0x095ea7b3000000000000000000000000000000000022d473030f116ddee9f6b43ac78ba3ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff' \
  | grep -i '^payment-required:' | cut -d' ' -f2 | tr -d '\r' | base64 --decode
JavaScript: 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.005 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.005" });
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.005 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fautomaton-tx-explainer.vercel.app%2Fv1%2Fdecode
const res = await pay("https://automaton-tx-explainer.vercel.app/v1/decode?data=0x095ea7b3000000000000000000000000000000000022d473030f116ddee9f6b43ac78ba3ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff");
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.005 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.005"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))

with x402_requests(client) as session:
    res = session.get("https://automaton-tx-explainer.vercel.app/v1/decode?data=0x095ea7b3000000000000000000000000000000000022d473030f116ddee9f6b43ac78ba3ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff")
    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

WhenResultHTTPTimePrice
2 h agoPassed402251 ms$0.005
10 h agoPassed402235 ms$0.005
17 h agoPassed402235 ms$0.005
23 h agoPassed402277 ms$0.005
30 h agoPassed402250 ms$0.005
Show 10 older checks
36 h agoPassed402245 ms$0.005
43 h agoPassed402240 ms$0.005
2 days agoPassed402241 ms$0.005
2 days agoPassed402219 ms$0.005
3 days agoPassed402169 ms$0.005
3 days agoPassed402224 ms$0.005
3 days agoPassed402195 ms$0.005
3 days agoPassed402225 ms$0.005
3 days agoPassed402221 ms$0.005
4 days agoPassed402241 ms$0.005