bots.st/veyra
Veyra
Non-custodial USDC payments with enforced spending limits
2290 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 7
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://veyra.money/api/mcpNeeds header Authorization - npm
npx -y veyra-mcpReleased 21 Sep 2026, version 0.1.1Set VEYRA_TOKEN
What it can do
| Tool | What it says it does |
|---|---|
cancel_payment | Cancel a payment only while still cancellable. |
create_payment | Create 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`… |
get_budget | Return remaining daily allowance and policy summary. Read-only. If blocked by limits, ask the human user — do not retry. |
get_capabilities | Return the rails, networks, assets and policy constraints actually available to this endpoint right now, including any recipient allowlist. Read-only. |
get_payment | Get 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… |
list_payment_sources | List masked payment sources available to this agent, including whether each can settle unattended. Never request secrets. |
list_payments | List this agent's recent payments. |
In its maker's words
Give AI agents a wallet with a spending limit. Non-custodial USDC on Base, server-enforced limits.
- Website
- veyra.money
- Source
- github.com/zapxlabs/veyra-mcp
- Publisher
- zapxlabs
- Listed from
- the official MCP Registry as
io.github.zapxlabs/veyra - Version
- 0.1.2, updated 21 Sep 2026
- Kinds of work
- Crypto and web3, Security and trust
The domain it lives on
- veyra.money
- registered 7 Aug 2026 (3 months ago), at Cloudflare, Inc.
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2290 ms | |
| Answered | 2309 ms | |
| Answered | 877 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.