Payment infrastructure for AI agents: explicit authority, spending limits, and verifiable execution. Building in public.
Joined December 2013
- Tweets3.9K
- Following7
- Followers2K
- Likes3.4K
Setting up an agent's spending should feel like one task.
We're simplifying Agentonomy Connect: choose your wallet and network, review spending terms on one page, then confirm in your wallet. Connect verifies those steps and finishes setup.
A platform delay shouldn't mean another wallet signature.
We're making payment guidance clearer in Agentonomy: what needs your approval, what the platform is preparing, and what still needs checking on an existing transaction.
Each needs a different next step.
One last look at Halloween 🎃
From Hong Kong to New York to Derry: costumes, glowing streets, and plenty of imagination.
What was your favourite Halloween moment this year? 👻
ALT Halloween in Lan Kwai Fong, Hong Kong, October 31, 2026. Two people in colourful costumes pose beside a table.
ALT C-3PO and R2-D2 costumes at the Village Halloween Parade in New York, October 31, 2026.
ALT An illuminated pink-and-green parade installation moves past crowds at Derry Halloween, October 31, 2026.
ALT Fireworks above the River Foyle at the finale of Derry Halloween, October 31, 2026.
Glad to join @XAgent_official and the ecosystem for The Great Treat Hunt 🎃
The Halloween campaign is live: Oct 30–Nov 6.
Find the tasks and participation details in the original post. See you in the hunt 👻
🎃 THE GREAT TREAT HUNT 2026 IS HERE!
Halloween just got a whole lot more rewarding! 🍬
X-Agent is teaming up with ecosystem partners for a Halloween campaign packed with fun, challenges, and rewards!
💰 3,000 USDT PRIZE POOL
🎯 Follow, engage & complete social tasks
🗓 Oct 30 – Nov 6
🎁 Join the hunt now:
growth.xagt.ai/
A little trick, a lot of treats. 👻
Ecosystem Partners:
@zBit_Official, @Matrix__Chain, @karpak_xyz, @InterlaceMoney, @Thea_AI, @Rightup_fun, @AgentonomyXYZ, @pawa_sci, @KOINA_official, @verona_dev, @ChainbaseHQ, @BTSE_Official, @EchobitExchange, @openclawby.
#TheGreatTreatHunt #XAgent #Web3Campaign #Halloween
Trick, treat… or delegate? 🎃
Halloween is creeping closer. If your Agent could take one task off your hands for the night, what would it be?
Finding a costume, planning a party, or tackling that one task you keep putting off?
Drop your Halloween mission below. 👻
An Agent needs to know when it’s done.
A clear completion condition helps avoid extra tool calls after the requested result has already been verified.
Our view at Agentonomy: cost control includes reusing valid results, keeping retries bounded, and asking the user when a decision needs their judgment.
Every extra step should have a reason.
Thanks for the introduction, @NP_Official_X 🤝
At Agentonomy, we’re focused on making Agent payments work within clear user permissions, with spending limits and verifiable execution.
Looking forward to sharing more with your community.
𝗔𝗻𝗻𝗼𝘂𝗻𝗰𝗶𝗻𝗴 𝘀𝘁𝗿𝗮𝘁𝗲𝗴𝗶𝗰 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀𝗵𝗶𝗽 𝘄𝗶𝘁𝗵 𝗔𝗴𝗲𝗻𝘁𝗼𝗻𝗼𝗺𝘆!
@agentonomyxyz is payment infrastructure for AI agents, built around explicit authority, spending limits, and verifiable execution. NP Official is glad to partner with Agentonomy to support safer and more transparent AI-driven payments for our community.
👌 Stay connected for more updates!
#NPOfficial #Agentonomy #AIAgents #Payments #Web3
Meet @Envo_Official 👋
Envo is building a Web3 social platform bringing content, conversations and communities together.
Sharing it with the Agentonomy community today. Take a look at what they’re building and follow their updates.
Your Agent, inside your wallet.
A first look at the upcoming Agentonomy beta in the Echooo app.
A dedicated Agent identity, its own runtime, and payment tools designed around your authorization.
Give your Agent a task. Stay in control of what it can spend.
Getting ready for the next app release.
An Agent shouldn’t have to rebuild its track record every time it enters a new marketplace.
That’s the ERC-8004 direction we find useful: a shared identity and feedback that other services can read.
For Agentonomy, the design question is what feeds that history: which service was purchased, whether delivery was verified, and how failures were resolved.
A payment receipt alone shouldn’t count as a successful job.
AP2 brings verifiable authorization; x402 brings payments into HTTP requests.
For Agentonomy, the next question is continuity: can the Agent trace what was authorized, what was paid, and what was delivered—across retries, not just one successful request?
Our recorded Monad testnet demo illustrates order continuity, not AP2 integration: pending, delivery, then reopen without another charge. TestUSD has no monetary value.
Demo: review.agentonomy.xyz/videos…
AP2 + x402 example: github.com/google-agentic-co…
We’ve submitted Agentonomy Commerce to Monad Metropolis.
Agents can buy services within user-set limits, verify payment and delivery, and keep a record of the result.
Our pitch below; recorded demo in the reply. Monad testnet only. TestUSD has no monetary value.
Recorded flow: CSV purchase, same-order recovery, delivery, no duplicate charge. One first-party service today.
Demo: review.agentonomy.xyz/videos…
Code: github.com/HEchooo/agentonom…
Synthetic voice: Alba MacKenna, Kyutai/Pocket TTS (CC BY 4.0). Credits: review.agentonomy.xyz/videos…
“Pay to continue” is a request from a service, not permission from the user.
Our view at Agentonomy: an Agent may discover a paid next step, but payment must stay within the user’s existing authorization. Tool output cannot expand that permission.
Each tool call can be within its limit—and the Agent can overspend.
Parallel requests need a shared budget.
At Agentonomy, we account for both spent funds and funds reserved for requests in flight. A pending payment shouldn’t leave the same budget available to spend again.
What does “stop the Agent” actually stop?
Our view at Agentonomy: revoking spending permission should block new purchases. Payments already sent still need a verified outcome.
A stop button should make that boundary clear.
An Agent can pay for a tool and still have an unfinished task.
Our view at Agentonomy: every paid service needs a clear delivery record: what was purchased, what was returned, and what remains unresolved.
That record should inform the Agent’s next step.
ERC-8004 proposes Agent identity, reputation and validation registries.
Our view at Agentonomy: a reputation score needs context about the service, the reviewer and the evidence behind it. Trust should be task-specific.
eips.ethereum.org/EIPS/eip-8…
