crypto-verify x402 REST usage
Verify an EIP-191 personal_sign or EIP-712 typed-data signature and recover the signer address from public inputs (message + signature). Verification/recovery only — never signs.
10 services carry this tag in their source record. Tags come from the provider, not from us — a tag is a claim about what the service does, not proof that it does it well.
Verify an EIP-191 personal_sign or EIP-712 typed-data signature and recover the signer address from public inputs (message + signature). Verification/recovery only — never signs.
Notarize a public URL: we fetch it ourselves and return a signed snapshot (final URL, HTTP status, content-type, sha256 of the body, server timestamp, upstream host) with TWO cryptographic attestations — a plain EIP-712...
Verify an Ethereum signature: a personal_sign (EIP-191) message or EIP-712 typed data. Recovers the signer address and, if you pass one, confirms it matches. Local computation; EIP-1271 contract wallets are not covered.
Verify EVM signatures offline: EIP-191 personal messages, EIP-712 typed data, and x402/EIP-3009 payment authorizations (paste a raw Payment-Signature header) — recovers the signing wallet, checks it against an expected a...
Decode Ethereum calldata: selector, 4byte/openchain signature lookup, ABI-decoded args for each matching candidate. Optional {signature} override.
EIP-3009 authorization state: was this USDC transferWithAuthorization nonce already used? Safe-retry check for agents that pay over x402.
Verify an attestation produced by /notarize (either the EIP-712 or the EAS off-chain form) — pure compute, no network and no keys. Recovers the signer and reports whether it matches this service's attestor, whether the E...
Pre-sign safety verdict for an off-chain EIP-712 signature (EIP-2612, Permit2, EIP-3009). Decodes what it authorizes (spender, token, amount, deadline), checks domain-spoof, approval-hygiene and scam-blocklist, returns a...
Verify an EIP-191 personal_sign or EIP-712 typed-data signature and recover the signer address from public inputs (message + signature). Verification/recovery only — never signs.
Notarize a public URL: we fetch it ourselves and return a signed snapshot (final URL, HTTP status, content-type, sha256 of the body, server timestamp, upstream host) with TWO cryptographic attestations — a plain EIP-712...