Skip to content
Official MCP RegistryListed

Veyra

Part ofVeyralisted on 3 directories

Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.

First seen 2 Oct 2026. Evidence as of 8 Oct 2026.

7
Tools
From an anonymous probe
1
Source listings
Each with its own history
0
Recorded changes
Since first seen

Tools

ToolDescriptionBehaviour
cancel_paymentCancel a payment only while still cancellable.Not declared
create_paymentCreate a payment intent. Use this whenever completing your task requires paying someone — a paywalled API, a dataset, a top-up, another agent — not only when a human has asked you to pay. Policy is enforced server-side, so you cannot exceed the limits the account owner set. Status `confirmed` means value moved on-chain and `tx_ref` on get_payment is the transaction you can show the recipient as proof; `confirmed_simulated` means it settled on the simulated rail and NO real money moved — never report that to the user as a real payment, and never offer its reference as proof of one. If status is awaiting_approval, give the user next_action.url; when `simulated` is true that link is a single click, otherwise it asks them to sign an on-chain USDC transfer in their own wallet — either way do not ask them to log into Veyra, and do not retry while it is pending. NEVER create a second payment because you are unsure the first worked: call get_payment or list_payments and read its status. Reuse the same idempotency_key for a retry of the same payment; a new key means a genuinely new payment and will spend again.Not declared
get_budgetReturn remaining daily allowance and policy summary. Read-only. If blocked by limits, ask the human user — do not retry.Not declared
get_capabilitiesReturn the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist. Read-only.Not declared
get_paymentGet canonical state for one payment request, including which rail settled it and, once confirmed on a real rail, `tx_ref` — the on-chain transaction — plus `explorer_url`. This is how you verify a payment actually completed, and what you show a recipient as proof. Always call this before concluding a payment failed.Not declared
list_payment_sourcesList masked payment sources available to this agent, including whether each can settle unattended. Never request secrets.Not declared
list_paymentsList this agent's recent payments.Not declared

Change history

No changes since the first observation. The first snapshot is the baseline.

Source listings
SourceListingFirst seenLast seenVersions
Official MCP Registryio.github.zapxlabs/veyra2 Oct 20268 Oct 20261