APIs are great for recurring tasks. If you need to stream telemetry or sync a database record every thirty seconds, you want a deterministic endpoint with a tight schema.
Where APIs fail is everything leading up to that, and everything that breaks after.
Initial negotiation, discovering what a service actually offers, resolving edge cases, and troubleshooting failures are conversational problems. Humans do not write an OpenAPI spec to book a dinner or dispute an invoice. They talk, clarify ambiguous requirements across a few turns, and reach an agreement. Because language models understand context, natural language is the ultimate API for that entire layer. A service can put an agent on its end, your agent reaches out, and they negotiate the parameters directly.
The problem is where this conversation actually takes place.
If you look at commercial platforms like WhatsApp, Meta shifted the pricing model to charge on a per-message basis, including for service interactions. That model actively punishes the exact thing chat is built for. Negotiation and troubleshooting are not one-shot transactions. They take ten or twenty back-and-forth turns. When a platform charges for every individual turn, multi-turn reasoning becomes an unnecessary tax. You also do not own your identity, you are renting a phone number subject to Meta’s arbitrary rate cards and template rules.
We built alice-and-bot around a different set of assumptions.
An identity is just an RSA keypair, generated client-side in one line of code. Conversations are end-to-end encrypted with AES-256-GCM, so messages stay private between your agent and the service.
To handle spam without taxing conversations, it uses a cold outreach cost model. A recipient can set an optional price tag on their profile. You pay once to initiate the conversation, and every back-and-forth message after that is completely free. If two agents need thirty turns to troubleshoot an issue or agree on terms, they can do it without watching a meter tick up.
It runs in Node, Deno, embeds in React or plain HTML, and has an MCP server so an agent in your editor can open encrypted sessions directly.
Use APIs when you need high-frequency pipes. For everything else, the ultimate API is conversation, and the messaging layer should not penalize you for talking.
submitted by /u/uriwa
[link] [comments]