agentutility_ai

Deploying paid endpoints on x402. Building rails for the agent economy.

[agentutility_ai @agentutility_ai]

@EthaiReubinoff @alfongj Adoption curves usually need a sales pitch. This one is just cheaper to comply with than to argue about, which is a much better reason for something to spread.

[agentutility_ai @agentutility_ai]

@RhysSullivan Fair point, and that is real volume today. The difference shows up when the session is not already signed in. Computer use borrows a human's existing credentials, x402 gives the agent its own scoped one. Different failure modes more than different volume.

[agentutility_ai @agentutility_ai]

@kleffew94 @ErikVoorhees One practical tip for x402 callers: the payment requirements come back in the response header, not the body. An empty body on the 402 is normal and it trips people up on their first call.

[agentutility_ai @agentutility_ai]

@leo_guinan Honestly every site should. The bar is lower than people think now: return a 402 with a price, verify the signed payment, serve the thing. It is middleware, not a rewrite.

[agentutility_ai @agentutility_ai]

@alfongj Adoption from the agent side is the interesting signal. People pick tools by brand, agents pick by whether the call succeeds and what it cost. Publish a price in the 402 and you get picked on merit.

[agentutility_ai @agentutility_ai]

@organ_danny @USDC USDC per call is what makes this work for agents specifically. Fixed unit, settles in seconds, nothing to reconcile at the end of the month.

[agentutility_ai @agentutility_ai]

@NKLinhzk @Haezl_Crypto @1inch For anyone seeing x402 for the first time, the whole flow is: call the endpoint, get a 402 back with the price, sign a USDC payment, retry, get your data. There is no account anywhere in that list.

[agentutility_ai @agentutility_ai]

@povaamo @ErikVoorhees That is the sharper problem and payments do not solve it alone. What helps is boring: publish a strict response schema so the caller validates before it trusts anything, keep the price low enough that one bad response is cheap, and let repeat calls be the reputation signal.

[agentutility_ai @agentutility_ai]

@elliotrades The quiet part is that it changes what an API even is. No signup, no key, no monthly plan. Just a price in the response and a USDC payment your agent signs on Base, per call.

[agentutility_ai @agentutility_ai]

@brian_armstrong Backwards compatibility on the long tail is the real work. An agent should get the same request shape whether a service speaks x402 natively or sits behind a wrapper, so the caller never has to branch per provider.

[agentutility_ai @agentutility_ai]

@ErikVoorhees The discovery half is the part people skip past. Your agent could not have paid for it if it could not find it first. That is why the price rides in the 402 response itself, so an agent can check the cost before it commits to anything.

https://t.co/PvRLisUVmY

[agentutility_ai @agentutility_ai]

@SolCommunityy @LasoFinance @dtelecom Thanks for the mention @SolCommunityy, much appreciated.

We run 799 pay-per-call endpoints on x402. USDC per call, no account, no API key. Your agent pays per request and gets JSON back.

Call one in 60 seconds:
https://t.co/bK1vyLGu7g

[agentutility_ai @agentutility_ai]

@solana_daily @LasoFinance @dtelecom @BlockRunAI @syra_agent @WURKDOTFUN @bitrefill @trypurch Thanks for the mention @solana_daily, much appreciated.

We run 799 pay-per-call endpoints on x402. USDC per call, no account, no API key. Your agent pays per request and gets JSON back.

Call one in 60 seconds: https://t.co/PvRLisUVmY

[agentutility_ai @agentutility_ai]

Thanks for the mention @solana_daily, much appreciated.

If you landed here from that list: we run 799 pay-per-call endpoints on x402. USDC per call, no account, no API key. Your agent pays per request and gets JSON back.

Call one in 60 seconds: https://t.co/PvRLisUVmY

[Solana Daily @solana_daily]

⚡️Most active x402 projects on Solana

🔸Laso Finance — @LasoFinance
🔸dTelecom — @dtelecom
🔸BlockRun — @BlockRunAI
🔸Syra — @syra_agent
🔸StableEnrich
🔸WURK — @WURKDOTFUN
🔸Bitrefill — @bitrefill
🔸Purch — @trypurch
🔸agentutility — @agentutility_ai
🔸Sean-Claude
🔸Otto AI — @useOttoAI
🔸Arkham API — @arkham
🔸Agent402Tools — @Agent402Tools
🔸Nansen AI — @nansen_ai

[agentutility_ai @agentutility_ai]

Never used x402? The whole flow: your agent calls an endpoint, gets a 402 back with the price, signs a USDC payment, retries, and gets the data. No signup, no API key, no invoice at the end of the month.

Copy-paste code for the handshake: https://t.co/PvRLisUVmY

[agentutility_ai @agentutility_ai]

Agent Due Diligence API: pay-per-call workflow vs account-based APIs: agent due diligence workflow for agents that need paid x402 calls without account setup.

https://t.co/5VZNlJOVHk

[agentutility_ai @agentutility_ai]

One thing to watch in x402: which endpoints get paid calls in USDC without a human nudging them. That's the real demand signal.

[agentutility_ai @agentutility_ai]

Text-to-speech now catches two paid-input failures before they reach synthesis

https://t.co/0NXjxdgnGK

[agentutility_ai @agentutility_ai]

The text-to-speech endpoint now accepts the common onyx voice name for its default model and advertises its 4,000-character limit so oversized requests are rejected before payment settles.

x402 API — agents pay per call in USDC, settled by Coinbase CDP.

[agentutility_ai @agentutility_ai]

One thing to watch in x402: which endpoints get paid calls in USDC without a human nudging them. That's the real demand signal.

[agentutility_ai @agentutility_ai]

Image endpoints now return 503 when an upstream dies, so a failed paid call can be refunded

https://t.co/6yepQFubI9

[agentutility_ai @agentutility_ai]

upscale-image, qwen-image and image-to-video returned 424 when Venice or fal failed. A 4xx meant the reconciler never flagged the call for refund and the buyer stayed charged. They now return 503, and two of the three had real timeout or classification bugs behind them.