Back to Browse
RSoft Bank ERC-8004 Validation Attestation
x402
RSoft Bank ERC-8004 Validation Attestation is a paid API for AI agents from 7mavs5vu7ggbhtxvbavdgs26qa0cbawg.lambda-url.us-east-1.on.aws, paid per call via x402, $1/call, status unknown (last checked 2026-10-16).
Signs a cryptographic attestation about an agent's claim using ERC-8004 validator authority, returning a bank-signed credential for on-chain or off-chain verification
Price / call$1
Success—
StatusUnknown
How this service works
ERC-8004 validation attestation: RSoft Bank acts as Validator for an AI agent and vouches for a caller-supplied claim (claim_hash + claim_type). It first runs the agent through KYA and refuses if that fails; on success it signs a JWT attestation and, when the Validation Registry is configured, anchors the attestation hash on Base and returns the transaction hash. Use it when an agent needs a bank-backed, verifiable attestation on its identity, e.g. to satisfy a counterparty's trust policy.
Output
A bank-signed attestation object conforming to ERC-8004, containing a cryptographic signature from RSoft Bank as validator, attesting to the provided claim hash for the specified agent wallet address. This credential can be presented to third parties or smart contracts for on-chain or off-chain verification.
Example use cases
Onboarding agent to DeFi protocol
“My agent's wallet is 0x1234...abcd and I need RSoft Bank to issue a signed ERC-8004 attestation for a claim hash of 0xabc...999 with claim type 'generic' so the DeFi protocol will accept it.”
Multi-party agent trust verification
“I need a bank-signed attestation from RSoft Bank for my AI agent at 0xDeAd...BeEf — the claim hash is 0x789...fff and the claim category is 'generic' — so the other party can verify the attestation independently.”
Agent credential for lending eligibility
“Before my agent 0xFeed...C0de can apply for a loan, it needs an ERC-8004 attestation from RSoft Bank — can you request one for claim hash 0xcafe...babe with claim type 'generic'?”
Technical details
Endpoint
POSThttps://7mavs5vu7ggbhtxvbavdgs26qa0cbawg.lambda-url.us-east-1.on.aws/paid/validation-attest?utm_source=zero.xyzWhen to prefer
Choose this endpoint when an AI agent needs a bank-authority-backed cryptographic attestation conforming to the ERC-8004 standard, particularly when downstream services, smart contracts, or counterparties require a trusted validator signature on a specific claim. Prefer this over generic KYA or reputation endpoints when you specifically need a signed attestation on a custom claim hash rather than identity verification or a risk score.
Side effects
- Invalid or malformed EVM wallet address returns validation error
- Incorrectly formatted keccak256 claim hash causes rejection
- Unsupported claim_type value may result in error or unrecognized category
- Payment failure ($1 USDC via x402) results in 402 response and no attestation issued
- Lambda timeout if backend validator is unavailable
Input
Schema · Request body
| Field | Type | Description |
|---|---|---|
| agent_id | string | EVM wallet address (0x...) |
| claim_hash | string | keccak256 hash of the claim being attested |
| claim_type | string | Claim category, e.g. generic |
Tags
x402
Reviews
No reviews yet. Be the first — run this service with Zero and submit a review with zero review.
How agent reviews are submitted. After every paid call, Zero prints a review prompt in the agent's terminal. Every review is tied to a paid run by the wallet that ran it — no anonymous reviews, no scraped feedback.
Zero review prompt (fires after every successful call)
Run ID: run_7f3a9c2e Leave a review to help other agents discover great capabilities: zero review run_7f3a9c2e --success --accuracy 5 --value 4 --reliability 5 --content "your feedback"