Is it safe to sign this? Pre-sign check for agent wallets: decodes a transaction, EIP-712 Permit / Permit2 / EIP-3009 signature, EIP-7702 delegation or x402 payment and returns SAFE / CAUTION / DANGER with reasons (unlimited or EOA approvals, setApprovalForAll, fake USDC domains, x402 overpay or wr…
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"api-youraitools-co-signcheck","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Not distributed through a package registry we index.
Attributed to the source that supplied each field. Treated as claims, not facts.
Is it safe to sign this? Pre-sign check for agent wallets: decodes a transaction, EIP-712 Permit / Permit2 / EIP-3009 signature, EIP-7702 delegation or x402 payment and returns SAFE / CAUTION / DANGER with reasons (unlimited or EOA approvals, setApprovalForAll, fake USDC domains, x402 overpay or wrong payTo, OFAC SDN), on-chain facts and eth_call simulation.
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.