PaySafe
Share / Embed
Reputation
formula v1.3Signals
Payment security firewall for x402 micropayments. Call PaySafe before settling any x402 payment to catch prompt-injection-triggered payments (attacker addresses planted in content the agent just read), replayed authorizations, overpayment, secrets leaking through payment metadata, fake/lookalike USDC contracts, and address poisoning. Returns allow/flag/block with machine-readable reasons and an Ed25519-signed, payment-bound verdict a wallet can enforce. Advisory and non-custodial — never touches keys or funds. Includes a shared counterparty reputation registry and a commitment-bound delivery-outcome ledger.
Source: https://paysafe-agent.com/.well-known/erc8004.json
Raw metadata
{
"name": "PaySafe",
"type": "https://eips.ethereum.org/EIPS/eip-8004#registration-v1",
"image": "https://paysafe-agent.com/logo.svg",
"active": true,
"services": [
{
"name": "web",
"endpoint": "https://paysafe-agent.com"
},
{
"name": "x402",
"version": "2",
"endpoint": "https://paysafe-agent.com/.well-known/x402"
},
{
"name": "A2A",
"version": "0.3.0",
"endpoint": "https://paysafe-agent.com/.well-known/agent-card.json"
},
{
"name": "OpenAPI",
"version": "3.1.0",
"endpoint": "https://paysafe-agent.com/openapi.json"
},
{
"name": "MCP",
"version": "1.4.1",
"endpoint": "https://registry.modelcontextprotocol.io/v0/servers?search=com.paysafe-agent/paysafe"
}
],
"agentWallet": "0x3C423B365efB79bFB42C9eC8f6F0745195ca7745",
"description": "Payment security firewall for x402 micropayments. Call PaySafe before settling any x402 payment to catch prompt-injection-triggered payments (attacker addresses planted in content the agent just read), replayed authorizations, overpayment, secrets leaking through payment metadata, fake/lookalike USDC contracts, and address poisoning. Returns allow/flag/block with machine-readable reasons and an Ed25519-signed, payment-bound verdict a wallet can enforce. Advisory and non-custodial — never touches keys or funds. Includes a shared counterparty reputation registry and a commitment-bound delivery-outcome ledger.",
"x402Support": true,
"registrations": [],
"supportedTrust": [
"reputation"
]
}
Services
-
webEndpoint
https://paysafe-agent.com -
x402 v2Endpoint
https://paysafe-agent.com/.well-known/x402 -
A2A v0.3.0Endpoint
https://paysafe-agent.com/.well-known/agent-card.json -
OpenAPI v3.1.0Endpoint
https://paysafe-agent.com/openapi.json -
MCP v1.4.1Endpoint
https://registry.modelcontextprotocol.io/v0/servers?search=com.paysafe-agent/paysafe
The ValidationRegistry contract is not yet deployed on Base Mainnet. Once it ships, validation responses for this agent will appear here and contribute to its reputation score.
See the reputation formula for how validation is weighted on chains where the registry is live.