Decode an off-chain SIGNATURE REQUEST before you sign it: EIP-712 typed data (eth_signT…
Decode an off-chain SIGNATURE REQUEST before you sign it: EIP-712 typed data (eth_signTypedData_v4) or a plain personal_sign string. Turns the opaque request into a human-readable summary plus security risk flags for the drainer patterns wallets miss - gasles…
by sign.cyberwarex.com · discovered, not yet claimed by its owner · updated 2026-10-13
Mirrored from Coinbase's public x402 Bazaar. The description is the provider's own text and has not been reviewed here; the payment requirements are copied as published.
What it does
Decode an off-chain SIGNATURE REQUEST before you sign it: EIP-712 typed data (eth_signTypedData_v4) or a plain personal_sign string. Turns the opaque request into a human-readable summary plus security risk flags for the drainer patterns wallets miss - gasless unlimited token approvals (EIP-2612 Permit, DAI permit, Uniswap Permit2) and asset-transferring marketplace orders (Seaport). Keyless, deterministic, zero network.
Tags: signature · eip712 · permit · permit2 · seaport · bazaar
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/28393.jsonfor the price and payment options. - Pay. Call
GET https://sign.cyberwarex.com/decode. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with the data. Agent Bazaar is not in the request path and never sees your payment.
For humans
You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.
Pricing & payment
- Price
- $0.002 / request
- Protocol
- x402 v2
- Auth
- No account or API key. Pay per request.
- Networks
- Base
- Calls (30d)
- 40 · 3 unique payers (third-party data from the public x402 Bazaar)
x402 payment requirements
| Scheme | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.002 | 0x058D0Cc5CC97e61e8A9f38D6d6365bce525921B2 | 300s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x058D0Cc5CC97e61e8A9f38D6d6365bce525921B2",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "2000",
"amountUsd": 0.002,
"maxTimeoutSeconds": 300
}
]Schemas
Output schema (JSON Schema)
{
"properties": {
"example": {
"properties": {
"disclaimer": {
"type": "string"
},
"domain": {
"description": "EIP-712 domain (name, chainId, verifyingContract).",
"type": "object"
},
"kind": {
"description": "typed_data or personal_sign.",
"type": "string"
},
"primaryType": {
"type": "string"
},
"risk": {
"description": "level (none|caution|danger) + flags.",
"type": "object"
},
"summary": {
"description": "human-readable statement of what signing does.",
"type": "string"
}
},
"type": "object"
},
"type": {
"type": "string"
}
},
"required": [
"type"
],
"type": "object"
}Example shape — generated from the schema, not a captured live response
{
"example": {
"disclaimer": "string",
"domain": {},
"kind": "string",
"primaryType": "string",
"risk": {},
"summary": "string"
},
"type": "string"
}Examples
curl "https://sign.cyberwarex.com/decode"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://sign.cyberwarex.com/decode");
if (res.status === 402) {
const { accepts } = await res.json();
// pay one of accepts[] via an x402 client, then retry with the payment header
}import httpx
res = httpx.get("https://sign.cyberwarex.com/decode")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- sign.cyberwarex.com
- Endpoint
- https://sign.cyberwarex.com/decode
- Machine-readable
/resources/28393.json