Veto

42 posts

Veto banner
Veto

Veto

@Vetooai

Making agentic payments safe, controllable, and trustworthy The decision layer for autonomous commerce

Katılım Nisan 2026
21 Takip Edilen18 Takipçiler
Sabitlenmiş Tweet
Veto
Veto@Vetooai·
Shipping Veto v1 next week. The enforcement layer between AI agents and the money. Your agent will not be able to spend what he shouldn't. Here's what you need to know 👇
English
1
3
13
379.7K
Franklin
Franklin@FranklinRun_·
AI agents keep hitting paywalls. So we gave one a wallet. Franklin: npm install -g @blockrun/franklin → browses the web → generates images & video → writes & runs code → pays for all of it on-chain 55+ models. <1ms routing. Your budget. Your results. github.com/BlockRunAI/fra…
English
1
5
15
1.4K
kevin
kevin@kleffew94·
I had a great time presenting to the crowd at @AWS Startup Connect in SF today! We covered the recent x402 launch enabling AWS AgentCore Bedrock Payments. Learn more here: docs.aws.amazon.com/bedrock-agentc…
kevin tweet mediakevin tweet media
English
13
7
75
2.3K
Global Settlement
Global Settlement@GSXnetwork·
@circle Agents will need money movement that actually has guardrails. Big step.
English
1
0
0
255
Circle
Circle@circle·
Introducing Circle Agent Stack: financial infrastructure for the agentic economy. Agent Stack gives agents the tools to: → Hold and move USDC through Agent Wallets → Discover services through Agent Marketplace → Execute repeatable financial actions through Circle CLI All within defined permissions and guardrails. Explore the site: agents.circle.com Read the blog: circle.com/blog/introduci…
English
67
113
501
223.1K
vibhu
vibhu@vibhu·
We built pay.sh in part to solve this emergent challenge with machine payments. Most agentic payments are being done through gray or black market facilitation, which means they can be disabled or banned without notice by the underlying provider. In collaboration with Google Cloud and (soon) a long list of other popular API providers, we're bringing the agent economy into the light. Our new tool takes Solana stablecoins as inputs, but pays the provider in fiat with a full license. That means you can safely build, deploy, and scale production apps with x402 or MPP at the root.
Bankless@Bankless

x402 broke a million transactions in the last two weeks alone, as endpoints keep going live across the ecosystem. Yet, a number of them appear to be unauthorized wrappers of services whose terms EXPLICITLY prohibit reselling. Right now there's no way to tell which is which. Three cases to consider: - Wolfram Alpha prohibits "resellers and aggregators," bans scraping, and bars sublicensing without permission. Yet, there's a third-party endpoint available for accessing it via x402 - Amadeus, a travel service, requires formal certification for any third-party connection, documented in a Service Order. You can access via Stabletravel. Whether the endpoint meets that standard isn't visible from the outside - A third-party wrapper was sourcing Google Flights data via SerpApi — a company Google is actively suing for scraping Search results and reselling access. Endpoint was recently removed from the Agentic Market storefront To be clear — the accountability here does NOT sit with x402. It's an open protocol, same as HTTP. It sits with those packaging unauthorized endpoints and collecting fees. With these current dynamics, providers bear the server load and see NONE of the revenue. A cleaner model already exists. MPP marks first-party integrations directly on each service card. Exa announced native x402 support, going first-party and citing the Linux Foundation's governance as the reason for choosing it. If there's no accountability here, it poisons the well. Potential native integrators become adversaries rather than participants. That revenue belongs to the providers. Native integration is how they claim it, and how x402 earns the legitimacy it needs to grow.

English
26
16
158
29.6K
Veto
Veto@Vetooai·
The question to How agents will pay has already more than 10 answers. We’re building the answer for How agents will pay SECURELY
vibhu@vibhu

We built pay.sh in part to solve this emergent challenge with machine payments. Most agentic payments are being done through gray or black market facilitation, which means they can be disabled or banned without notice by the underlying provider. In collaboration with Google Cloud and (soon) a long list of other popular API providers, we're bringing the agent economy into the light. Our new tool takes Solana stablecoins as inputs, but pays the provider in fiat with a full license. That means you can safely build, deploy, and scale production apps with x402 or MPP at the root.

English
0
0
1
65
Veto
Veto@Vetooai·
@ethanyish What about collaborations? 😅
English
0
0
0
224
Veto
Veto@Vetooai·
To anyone that’s been affected by the coinbase layoffs, we were sorry to hear that. But we would absolutely LOVE if you’d join us to build the next step of agentic commerce. Our dms are open 💙
English
0
0
1
63
Priyanka Saini
Priyanka Saini@PriyankaSaini28·
Hey Builders, Drop what you’re building Just the link No Pitch I’ll go through everything ↓
English
325
6
137
8.8K
Nick Prince🛡
Nick Prince🛡@Nick_Prince12·
agentic(.)market week 2: you can now give your agent access to thousands of services by pasting a single URL (seriously, that's it) plus verified badges and seller tools three things shipped 🧵
English
38
16
189
77K
contract.dev
contract.dev@contractdotdev·
if you ask us what contract.dev does, here’s the short intro: > private testnets that follow real mainnet state, so you test in production conditions before shipping > catch edge cases that only show up against real on-chain data, not sanitized testnets > built-in devtools contract dashboards, simulation framework, integrations with uniswap, chainlink, and more tl;dr: your own private mainnet to break things on, before users do.
contract.dev tweet media
English
3
3
15
878
Youssef
Youssef@0xyoussea·
Last week, agentic market dropped a new md file that helps your agent fully onboard you to x402 no matter the level of your technical skills or the app you're using (Claude Code, Claude Desktop, etc) When you're shipping agentic products, you can target a wider audience by pushing the complexity to the agentic layer It's a completely new paradigm, most haven't fully caught up to it yet
Danny Organ@organ_danny

🤖Agentic commerce lifecycle: -Agents pursue most efficient execution path -Other agents observe and follow suit -if a new (more efficient) path emerges, agents switch to new path The # of buyers/sellers of x402-enabled services is 📈, which is bullish for: -agentic autonomy -stablecoins -high efficiency chains -x402

English
12
3
73
5.8K
Build in Public
Build in Public@buildinpublic·
What are you working on this week?
English
395
5
212
18.4K
Veto
Veto@Vetooai·
Composes with the agent-payments stack: - x402 (@coinbase) - HTTP 402 micropayments - AP2 (Google + 60 partners) - intent mandates - Stripe MPP - card-rail at machine speed - Verifiable Intent (@mastercard + @google) Veto sits one layer above. The block travels with the agent.
English
1
0
0
1.4K
Veto
Veto@Vetooai·
Shipping Veto v1 next week. The enforcement layer between AI agents and the money. Your agent will not be able to spend what he shouldn't. Here's what you need to know 👇
English
1
3
13
379.7K