For two years the question has been the same: the model can talk, so why can't it do anything in my accounts without a workflow builder in the middle?
0n3 is the answer we built. It is the universal hub: one sign-in that connects hundreds of applications and opens every one of their endpoints to the AI you already trust. Not workflows. Not Zapier. You describe the plan; the AI executes it in your accounts; every call lands on a receipt.
What changed
- One identity. Your 0n account works on every 0n app and inside every AI you install 0n3 into: Claude, ChatGPT, Cursor, Claude Code, Codex, Gemini CLI, VS Code, Windsurf.
- Every endpoint. 122 services and 1,804 endpoints, plus 868 generated CRM tools, callable with your own connections. Secrets never reach the model.
- Receipts. A multi-step job comes back as a receipt: each step ok, skipped with why, or failed in the provider's own words. "I think it worked" is gone.
- A front-facing URL and user login. A visual board builds the page your customers sign in to, live at 0n3.app/w/yourname or on your own domain.
- Payments. Prices, subscriptions, invoices and checkouts created by your AI in your own Stripe.
- The Desk. An assistant that runs on your computer with your own coding agent, asks you on your phone before anything leaves the machine, and replies with what it did. Seven guided steps.
- Patent pending. The MCP integration behind it.
Thirty seconds to the first tool
- Create an account at 0n3.app and connect one app.
- Open 0n3.app/install, pick your AI, copy the one line it gives you.
- Ask your AI: whoami. Then ask it to do something real.
{ "mcpServers": { "0n3": { "url": "https://0n3.app/mcp", "headers": { "Authorization": "Bearer 0n_…" } } } }
If you already run 0nMCP
Your 0n_ token works unchanged. The old endpoints carry it to 0n3 for you. Local installs move to npx 0nmcp@5 stdio; the 4.x package stays on npm as 0nmcp@4. The registry entry io.github.0nork/0nMCP now points at the hosted server.