
VEYA Utility: Give AI agents access to assets, apps, and tools while keeping control over permissions, limits, and execution.


Infrastructure for autonomous systems. Privacy-first, intelligent & decentralized on RH. CA: 0x81e770ba8343232b6f200209bf9a2c1430c2dea1 t.me/withveya

VEYA Utility: Give AI agents access to assets, apps, and tools while keeping control over permissions, limits, and execution.


Why pay an agent for something a free chatbot already does? You shouldn't. What's worth paying for is an agent that can buy what it needs (a search API, a data feed) without your card, and never past your limit. That's what we're building with priced tasks: 1. Your agent asks for a task 2. VEYA shows the exact price first, valid for 5 minutes 3. You approve. Nothing moves before that 4. It's paid from your own wallet, under your permission 5. If the real cost comes in higher, the charge never goes above the quote Every step leaves a receipt. The payment flow works end to end in our tests. Connections to real research providers are built and still being tested. Not live yet. What would you want your agent to buy first? Curious what @Mrbullemmy and @0x99Gohan would pick 👇

Microsoft's agent got instructions. BNY checked the counterparty, the bill, the size and the terms. The agents only haggled inside approved price limits. That's the whole design: the agent can negotiate. It cannot rewrite the checks. On VEYA those checks run before the payment leaves. Payee, amount, a limit the agent can't raise, and a receipt on Robinhood Chain with payee and amount never stored. The banks already know the agent shouldn't be the one holding the pen.
Pour a quick coffee. BNY and Microsoft had AI agents haggle over a U.S. Treasury bill. The word I circled in BNY’s release was repo. Here’s what actually happened: Microsoft Treasury gave its agent instructions. BNY checked the counterparty, the bill, the size and the settlement terms. The agents haggled inside approved price limits. Humans signed off. The firms executed and booked the trade through their existing systems. Now take that same setup into repo, where firms borrow cash against securities. BNY says it’s a possible next use. If the terms can come together faster, how fast can you actually get the cash and the collateral to the right place? Who has both available at size? How much cash do you still have to park in advance? The agents can agree on a price. Somebody still has to deliver. The plumbing point to Dec 31st/Jan 1st, Jan 18th, June-July 2027, to the Fed, to the Treasury, to the OCC. Comment periods are ending fast. Not fast enough.

@0xJeff @AltcoinMiyagi, agent checkout is here. Who's building the limits.

A spending limit, and a list of stores the agent is allowed to use. That's the right shape for checkout. The part that matters is where the limit lives. If the agent can reach the thing that raises it, it isn't a limit. It's a suggestion. On VEYA the cap sits onchain in USDG, the payee list is the owner's, and the agent has nothing in reach to change either one. Only the owner moves it. Every agent that can check out needs a limit it can't talk its way past. $VEYA
Now Gemini can check out securely with Google Pay, using the Agent Payments Protocol (AP2). Just set a spending limit and pick which stores it can use. Gemini checks with you before it buys, or you can let it go ahead on its own, within your limit. You’ll still receive all your card benefits, and we’ve partnered with Visa, Mastercard, and, soon, American Express, to secure your purchases using digital tokens on supported cards. Afterward, your receipts, order confirmations, and delivery updates will all be in your Google Wallet, which is expanding to iOS starting today. Tasks in Gemini will soon integrate with the Universal Commerce Protocol (UCP) for an even easier shopping experience.

We showed you the control room. Here's what "Stop all agents" will do when it ships. 🎛 One press: → Every agent in VEYA pauses → Every approval still waiting is declined → Your wallet gets ONE transaction that revokes all their permissions at once Sign it, and nobody can use those permissions again. Not the agent. Not us. The revoke happens on chain, not as a switch in our database. In our tests, one transaction revoked every permission, and the next payment attempt was refused. Refusals get receipts too: ❌ "Refused, over the limit" ❌ "Refused, permission revoked" When something goes wrong, you don't just want to know what your agent did. You want to know what it tried. In final testing. It ships with wallet permissions. Daily limit or kill switch: which would you set up first? 👇

Giving outside experts deep access to test your safeguards is the right instinct. The same rule should apply the day an agent gets a wallet: the safeguard can't live inside the thing it's guarding. At VEYA the agent's USDG limit sits outside the agent. It can ask for more. It can't raise it. Trust that can be checked by someone else is the only kind that scales.
We’re working with @ApolloResearch, @METR_Evals, @TransluceAI, and @GoodfireAI on embedded assessments: giving outside experts deep access to our internal models and systems to investigate alignment and test our safeguards. These assessments build on our ongoing alignment and safety research, bringing independent scrutiny to how we identify and manage risks in our systems. openai.com/index/our-first-p…

Veya just applied to the @arbitrum ARB02 Mentorship Program 🛡️ We're building security guardrails for AI agents: spend limits, allowlists, 2-of-3 checks and on-chain receipts. Fingers crossed for the next stage 🤞 veyanet.tech

"Agents won't use crypto rails" only holds if you picture an agent buying sneakers. ChatGPT Wallet on Visa and Mastercard is great for that. Cards were built for a person at checkout. Now picture an agent paying another agent 3 cents for an API call, 400 times an hour, at 3 AM, with nobody awake to approve it. That needs a USDG limit the agent can't raise and a payment that settles in seconds. That's the part we build at VEYA. Cards for shopping. Onchain rails for machines paying machines. Both win.
The last bull case for crypto (agentic payments) just died. They will not use crypto rails. It’s over.

"Privacy shouldn't be a setting you go looking for." Best line I've read this week. One week of Gloam: Elysium live as the fifth mainnet, cashouts to another chain, a ninth live partner, Agent SDK 0.7 tying every x402 payment to the payee it was meant for, 2-of-3 signers on vault changes across four chains, and 500+ private transfers on mainnet. That's not a roadmap. That's a changelog.
This past week we took privacy to more places. Privacy shouldn’t be a setting you go looking for. It should already be wherever your money is. Elysium went live as our fifth mainnet. Money bridged into Elysium can land private, and HYPE and KNTQ now sit beside USDC. Cashouts can now go to another chain, so your money leaves Gloam where you actually need it. @blocktronicsxyz joined as our ninth live partner, and Agent SDK 0.7 ties every x402 payment to the payee it was meant for. Changes to our vaults now need two of three signers on four chains. We bought back and burned robinhood:0xdcd885f5c60b3ad49f6d58718696417314e8724d for the third time on Friday, and Hunt 2 was solved on Saturday with the 100 USDC claimed. 500+ private transfers on mainnet so far. Last call for the Gloam Video Contest. Entries close tomorrow, Monday 16 Nov, at 23:59 UTC. $600 goes to four winners, paid privately with Gloam claim links. Winners are announced by 18/19th Nov.

A prompt is a suggestion. A limit is a wall. ChainGPT nails it: the rule has to live in code and get checked before the wallet signs, not sit in a system prompt hoping the model listens. That's how we built VEYA. The agent's USDG limit sits outside the agent, and it can't raise it. Every payment gets checked first. The receipt lands on Robinhood Chain, with payee and amount never stored. Agents can be persuaded. Code can't.
"Spend carefully" doesn't enforce a wallet rule. A prompt guides the model. ChainGPT's Developer Kit checks configured transaction policies in code before its optional agent wallet signs locally.

192 teams. 421 public updates. One week. People keep asking where the Robinhood Chain builders are. They're right here, shipping on a Sunday: spend logs, risk checks, v4 hooks, GPU rental, signed receipts. Every chain says it has builders. This one has receipts.
192 teams were building on Robinhood Chain this week. 421 updates shipped, every one public. Eight of them: @upochtech shipped 2.0 to 2.3 in four days: a spend log, Risk Check, the Agent Hub and mobile alerts @qHooks_ deployed a new Uniswap v4 hook on Robinhood Chain and shipped launch verification @texelrun released its contracts v1.0.0 and opened GPU rental to every wallet @LetronnaAgent shipped 0.1.0-alpha.5.1, with a one-command install on a Mac @zolva_agent shipped one-click setup for its read-only MCP server @alphamorpheus published its thesis, two REBUS research results and a public log @paidwithtab shipped tab 3.2.0, with a public log of every signed receipt @bitty_io shipped EVM vaults to its mobile app, Robinhood Chain included The builders are here. Most people just aren't looking. Every Sunday we show who shipped. Follow so you don't miss the next ones.

Not one hand went up. Honestly, that's the right answer. Nobody should let an agent pay on their behalf if "on their behalf" means the whole wallet. The question changes when it's a budget instead: 10 payments fired at once against a 5 USDG total limit. First 5 allowed, last 5 refused, the rest of the wallet untouched. People won't trust agents with money. They'll trust limits that hold.
Jimena Santillán asked a room of payments people in the Nordics who would let an AI agent pay on their behalf. Not one hand went up. Why the people building agentic payments don’t trust them yet. Full discussion: buff.ly/brtvZqz

Giving your AI agent money shouldn't mean giving it your wallet. Coming to VEYA: wallet permissions. You sign one rule set: → How much it can spend per day → Who it's allowed to pay → Until when → Only VEYA can use it, and only inside those rules The rules live on chain, not in our database. VEYA checks first, and if anything ever slipped past us, the chain itself would refuse it. In our tests: ✅ Inside the limit: paid ✅ Same request twice: charged once ❌ Over the limit: refused ❌ After you revoke: refused Your funds stay in your wallet until a payment fits what you signed. In final testing now. What would you let an agent pay for first? 👇

A security check for every purchase. That's the line that matters in ChatGPT Wallet. Agents don't get your card. They get permission, one purchase at a time. Same instinct we built VEYA on for onchain agents: a budget check before every payment, USDG limits the agent can't talk its way past, receipts on Robinhood Chain, payee and amount never stored. Agents are getting wallets. The ones that win will have brakes.
openai.com/index/introducing… "We’re introducing ChatGPT Wallet, setting a new bar for secure payments by agents. It’s the first wallet that lets agents pay without access to users’ actual card details and that requires a security check for every purchase, while also preserving existing card rewards and protections for eligible disputes. Built in partnership with American Express, Mastercard, and Visa, ChatGPT Wallet will initially be available through dots for ChatGPT Pro subscribers in the US. Alongside ChatGPT Wallet, we’re releasing tools and guidance to help businesses support customers using agents."

25,517 agents registered on Robinhood Chain. 510 actually moved money. That gap isn't a demand problem. It's a trust problem. Nobody hands an agent a wallet without knowing where it stops. That's the part we build at VEYA: a budget check before every payment. We fired 10 payments at once against a 5 USDG total limit: first 5 allowed, last 5 refused, the rest of the wallet untouched. The other 25,000 start moving when the limits are boring and provable.
Of the 25,517 agents registered on Robinhood Chain through Nov 11, most are not moving any money. that1618guy's State of Blocks chart, read straight off the chain, shows those wallets paid $56.4K in USDG over the prior 7 days. Only 510 of them were active, and the median payment was $5. The count only includes agents with an on-chain registry ID, and only the USDG they send. Other tokens and off-chain work are left out, including agents that trade inside the Robinhood app. The registry is filling up much faster than the payments. That is the state of agentic finance on this chain so far. FT @that1618guy @stateofblocks @RobinhoodCrypto @RobinhoodApp