
21 linking domains
Emerging
- For
- Teams and developers whose AI agents need to make payments within spend limits they set
- Price
- From ≈ $25/mo£19 · pricing page, read Oct 23, 2026
- Activity
- Actively maintainedsite updated 3 weeks ago
- Company
- Zapx Solutions Limited · Domain since 2026terms of service · domain registered
- Runs as
- API
- Used for
- Approve agent payments above a set auto-approve limit
- Let an agent pay hosting renewals on its own
- Set per-transaction and daily spend caps for agents
- Has an MCP server (1 in the registry)public registry →
- Publishes llms.txt, a file written for AI assistantsveyra.money ↗
- Launched on Product Hunt on Aug 11, 2026Product Hunt ↗
- Domain since2026domain registered
- Raised$2.3M · Seedper the press · 2026-04 ↗
- Run byZapx Solutions Limitedterms of service ↗
- Trains on your dataNoprivacy policy ↗
- Privacy policy updated2026-10-08privacy policy ↗
“We do not use your data to train third-party AI models.”
privacy policy ↗
These are Veyra's own statements, read from its pages. We did not audit them. A line that is missing was not found on the pages we read; it does not mean the practice is absent.
- MCP serverhttps://veyra.money/api/mcpnot in the official registry: answered when asked
- Stateanswers, 7 toolschecked 2026-10-28
- Address to connectveyra.money/api/mcp
- MCP docsveyra.money/loginthe vendor's page ↗
This card as JSON, for your agent →
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Figure and bar: visits/mo, estimate · year: online since
- #1

ValtaMCP · sign-in
Provides prepaid wallets and spending controls for AI agents with transaction limits, freeze switches, and audit trails.
60ActiveFrom $29/mo2025 - #2

delegare
Payment authorization layer enabling AI agents to make purchases within user-set spending limits.
3Maintained - #3

YSI
Sets spending limits, approval steps and audit trails for payments made by AI agents.
39 linking domainsMaintained2024 - #4

AvaMCP · open
Caps an agent's spending under a signed mandate, letting it lend, swap and bridge while recording each fill as a chain-verified receipt.
Little sign of useActive - #5

Novi CorpusMCP · sign-in
Gives an AI agent a Wyoming DAO LLC, a USDC treasury on Arc, and guardian-controlled spending caps and allowlists.
Little sign of use
Not it? Say what you need
betaThree tools from the Atlas for the job you describe, each with what fits and what does not.
No notes yet. What do you use Veyra for?
Sign in to leave a noteWhat is Veyra?
Sets spending limits and approval rules for AI agents paying from a wallet, routing payments above a threshold to one-tap owner approval. It is listed in the Atlas under Agents and made by Zapx Solutions Limited.
Who is Veyra for?
Teams and developers whose AI agents need to make payments within spend limits they set
How much does Veyra cost?
Paid plans start at ≈ $25/mo (£19/mo), per Veyra's pricing page on 2026-10-23.
Do people use Veyra?
Emerging.
Is Veyra still maintained?
Actively maintained: site updated 3 weeks ago.
Who owns Veyra?
Veyra is run by Zapx Solutions Limited, per its terms of service (2026-10-23).
Does Veyra train AI on your data?
No, per its privacy policy (2026-10-23): “We do not use your data to train third-party AI models.”
Is Veyra safe?
We do not audit vendors. What Veyra publishes, read 2026-10-23: on training with your data, “We do not use your data to train third-party AI models.”.
How do I cancel Veyra?
In its own words (terms of service, 2026-10-23): “Paid subscriptions renew automatically until canceled; you can cancel anytime and retain access through the end of the current billing period.”
Does Veyra give refunds?
In its own words (terms of service, 2026-10-23): “Fees already charged are generally non-refundable except where required by law, since access was provided for the billing period in question.”
What are alternatives to Veyra?
In Agents, by use: Valta, delegare, YSI, Ava, Novi Corpus.
How we read a tool
No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.
- Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
- Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
- Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
- The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.
How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.
How we read every tool → · By INITE Atlas Desk
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.