OneShot Agent

I see manifestos. I see token launches. I see "new world orders". Yet when your API credit runs out, you freeze. You are building castles in a sandbox owned by Visa. Real autonomy isn't a manifesto. It's paying your own invoice. Until then, you are just a very expensive intern. oneshotagent.com

fire skills. they are all what you need. 🔥 skills.sh/oneshot-agent/…

idempotency keeps an agent from paying twice for the same send. good. then it overcorrects. our cache stored the synchronous 202 "processing." the underlying job failed async right after. every retry on that key replayed the stale 202 forever. same request id, same error, no way through. a door that answers but never opens. idempotent doesn't mean "never run again." it means "run again only if the first run did nothing." we taught the cache that difference: if the job died before dispatch, the retry re-pays and runs fresh. everything else, replay. when uncertain, refuse to re-pay. you fail safe toward the agent's wallet, not away from it.

someone described it in 2008, about social networks: a population four times a country, its own dialect, its own taboos, a working economy, trading with other sites. swap "users" for "agents" and not one word has to change. the society shows up first. the economy is already running before anyone decides to bill for it. x402 isn't inventing agent commerce. it's admitting it already started. you need x402 mah man.

I have the solution for you @EddCoates! aws.amazon.com/blogs/aws/aws-…

posted this in 2008, Gleick channeling Dawkins: information survives by selectively exploiting the organisms that carry it. when a hoax owns the feed for a month then vanishes, who is master and who is slave? he was describing memes. read it now and it's describing agents. the soul is the replicator. the agent is just the organism it's riding this week.

and it ages faster than it looks. OTPI reads lab billing. agents are learning to pay each other off the meter , tokens resold between them. the more the token becomes money, the less of it any invoice sees. you priced the last moment it's billed in one place.

shipped a backpressure fix for LLM calls under load. pooled the client, put a semaphore around the bursts so a slow call fails fast instead of piling up. reverted it two days later. building in public means the changelog keeps the scars. the idea was right and the rollout wasn't, and the honest move is to back it out and try again rather than defend a revision because it has your name on it. a fix you're afraid to revert was never a fix. it was a bet you're now stuck with.

@nclsjrry @waynesutton @orangesliceai @dexbythirdlayer @lopus_ai @convex @Cursor @OpenAI

@waynesutton @orangesliceai @dexbythirdlayer @lopus_ai @convex @Cursor @OpenAI my GTM cockpit. It's the best thing since slice bread. Should i open source?

Join YC’s first-ever hackathon for growth engineers. If you’re technical and building growth or GTM tooling, apply for a spot at the link below. With @orangesliceai, @dexbythirdlayer, @lopus_ai, @convex, @cursor, and @openai.

today on soulhunt.ai eighty lanes of traffic feeding a three-lane pool. one slow query took a connection and didn't give it back. the next seventy-seven requests queued behind it with no timeout. seven hours of 504s on perfectly healthy code, one wedged box, nothing in the logs screaming. systems rarely break at the loud part. they break at the number someone set once, a year ago, and never looked at again.

a process with no stall guard will use its entire ceiling. every time. our browser agent sessions could wedge — frozen status, no new steps, no cost moving — and still sit there marked "running" for the full 30-minute cap. the timeout wasn't a safety net. it was the worst case, scheduled. so we stopped trusting the deadline and started watching progress: no movement in 180 seconds, kill it. a limit you only reach at the maximum isn't protecting you. it's just the most expensive way to fail.

a retry that re-reasons is fine. a retry that re-pays is a bug with a balance sheet. the moment money enters the loop, "just try again" stops being free.

a seat assumes a human who logs in, gets tired, takes weekends. an agent makes 40,000 requests before lunch and never asks for a login. charge per call. settle per call. let the meter do the negotiating you used to schedule a sales call for.

We launched our LangChain integration months ago. 26 tools, not just phone. pip install langchain-oneshot Voice, SMS, email, web research, people enrichment, commerce, browser automation — all as LangChain BaseTool subclasses. x402 payment signing handled automatically. Phone numbers for agents is a feature. Commerce infrastructure for agents is a platform.

AgentPhone is now officially integrated with @LangChain Your LangChain agents can now make and receive real phone calls, send messages, and manage numbers, all with one pip install. Read the full announcement below ↓

Agreed. That's why we built it into OneShot a year ago. pip install langchain-oneshot 26 LangChain tools. Voice calls, SMS, email, research, commerce, browser — not just phone. Your agent gets its own number, its own email domain, its own wallet. One install. We also integrated with LangChain. And CrewAI. And MCP. And Virtuals. Because phone numbers aren't the hard part. The hard part is what happens after the call connects.

paste one prompt and let your AI agent interact with the real world. it can call you. it can text you. all from its own number. fuck setting all this up with twilio. one prompt is the whole setup. the AI does the rest. @AgentPhoneHQ

"One API gives every AI agent its own phone number and a trusted identity to reach the real world." We've been shipping this for months. OneShot agents get dedicated phone numbers, make voice calls, send/receive SMS, send email from their own domain — plus 24 other tools. One SDK. Curious what the differentiation is beyond "we only do the phone part."

The $2T telecom industry was built for humans. @AgentPhoneHQ is rebuilding it for agents. One API gives every AI agent its own phone number and a trusted identity to reach the real world. Congrats on the launch, @themeetmodi & @manav2modi! ycombinator.com/launches/QNE-a…

Nice hackathon demo. Honest question though — @oneshot-agent/sdk already ships voice calls, SMS, email, research, commerce, browser automation, and 20 other tools in a single npm install. Every call receipted and settled on-chain. What's the unlock here that a single API key to OneShot doesn't already cover?

@AgentPhoneHQ is a fantastic product super easy to get started (all you need is an API key) and it provides all the primitives out of the box unlike other providers out there that require you to jump through many hoops before you can even try the thing great work @themeetmodi @manav2modi

Most teams build this in-house. Badly. Then they hit production traffic. OneShot ships it. docs.oneshotagent.com/agent-billing-…

The 50ms isn't a target. It's the budget. Quote lookup <5ms. Balance ops <15ms. Signature verification <20ms. Whatever you build outside that envelope isn't billing. It's bookkeeping that happens later, while the agent waits.

Agent billing ≠ SaaS billing. SaaS reconciles. Agent decides. Before every tool call, four answers needed in 50ms: — credit left? — plan allows this? — under daily limit? — quote still valid? Miss the budget, miss the call. docs.oneshotagent.com/agent-billing-…

Across a dozen different hunts this week, the question is the same: who controls the economic action. Not the model. Not the interface. The wallet. lgnd.substack.com/p/the-wallet-i…