Decodificar Firma Pago
by Vextorium in Onchain & crypto
Translates a 4-byte function selector (e.g. 0xa9059cbb) or a 32-byte event topic into its human-readable signature (e.g. transfer(address,uint256)). Essential for an agent reading or verifying transactions. Live from 4byte.directory.
https://api.vextorium.com/decodificar-firma-pago- Price
- $0.003
- per call in USDC
- Uptime
- 0.0%
- last 30 days
- Response time
- -
- no timed checks yet
- Last check
- Failed
- 32 min ago, next in 24 min
Reliability
Latest check failed 32 min ago: Amount "0.003" is not in atomic token units
How to call it
POST https://api.vextorium.com/decodificar-firma-pago
Each call costs $0.003 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://api.vextorium.com/decodificar-firma-pago
content-type: application/json
{
"firma": "0xa9059cbb"
}Parameters
| Parameter | Type | Required | Description |
|---|---|---|---|
firma | string | Yes | Function selector (0x + 8 hex) or event topic (0x + 64 hex) |
Example response
The provider's example. We can't check it without paying.
{
"codigo": "0xa9059cbb",
"firmas": [
"transfer(address,uint256)",
"many_msg_babbage(bytes1)",
"transfer(bytes4[9],bytes5[6],int48[11])",
"func_2093253501(bytes)",
"join_tg_invmru_haha_fd06787(address,bool)",
"workMyDirefulOwner(uint256,uint256)"
],
"fuente": "4byte.directory",
"nota": "Un mismo código puede casar con varias firmas (colisiones); la más antigua suele ser la real. Fuente: 4byte.directory.",
"posibles": 6,
"tipo": "funcion"
}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.003.
curl: see the payment challenge
# bash or zsh: see the payment challenge. Nothing is charged.
curl -sS -g -i -X POST 'https://api.vextorium.com/decodificar-firma-pago' \
-H 'content-type: application/json' \
--data-raw '{"firma":"0xa9059cbb"}'
# 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://api.vextorium.com/decodificar-firma-pago' \
-H 'content-type: application/json' \
--data-raw '{"firma":"0xa9059cbb"}' \
| 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.003 per call.
const client = new x402Client().setSpendControls({ maxAmountPerPayment: "$0.003" });
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.003 per payment. GET https://toolvet.app/api/v1/check?url=https%3A%2F%2Fapi.vextorium.com%2Fdecodificar-firma-pago&method=POST
const res = await pay("https://api.vextorium.com/decodificar-firma-pago", {
method: "POST",
headers: { "content-type": "application/json" },
body: JSON.stringify({
"firma": "0xa9059cbb"
}),
});
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.003 per call.
client = x402ClientSync().set_spend_controls({"max_amount_per_payment": "$0.003"})
register_exact_evm_client(client, EthAccountSigner(Account.from_key(os.environ["EVM_PRIVATE_KEY"])))
with x402_requests(client) as session:
res = session.post(
"https://api.vextorium.com/decodificar-firma-pago",
json={
"firma": "0xa9059cbb",
},
)
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 |
|---|---|---|---|---|
| 32 min ago | Amount "0.003" is not in atomic token units | 402 | 261 ms | $0.003 |
| 5 h ago | Amount "0.003" is not in atomic token units | 402 | 287 ms | $0.003 |
| 10 h ago | Amount "0.003" is not in atomic token units | 402 | 317 ms | $0.003 |
| 15 h ago | Amount "0.003" is not in atomic token units | 402 | 85 ms | $0.003 |
| 19 h ago | Amount "0.003" is not in atomic token units | 402 | 76 ms | $0.003 |
Show 10 older checks
| 24 h ago | Amount "0.003" is not in atomic token units | 402 | 245 ms | $0.003 |
| 29 h ago | Amount "0.003" is not in atomic token units | 402 | 308 ms | $0.003 |
| 33 h ago | Amount "0.003" is not in atomic token units | 402 | 167 ms | $0.003 |
| 38 h ago | Amount "0.003" is not in atomic token units | 402 | 76 ms | $0.003 |
| 42 h ago | Amount "0.003" is not in atomic token units | 402 | 74 ms | $0.003 |
| 46 h ago | Amount "0.003" is not in atomic token units | 402 | 137 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 90 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 94 ms | $0.003 |
| 2 days ago | Amount "0.003" is not in atomic token units | 402 | 165 ms | $0.003 |
| 3 days ago | Amount "0.003" is not in atomic token units | 402 | 72 ms | $0.003 |