Developer platform

Your engineers. Your IDE. Same platform.

CLI, API, SDK, MCP. 110 commands. 168 MCP tools. 330 typed receivers in one catalog behind all four surfaces — and docs checked against the code, not written on faith.

npx oneie — no install · first API call in 1 minute · open source

Terminal: npx oneie signal chairman --data '{"tags":["chat"],"content":"New lead"}' | curl /api/signal | @oneie/sdk one.signal() | MCP: signal

110

CLI commands covering the whole operation

168

MCP tools available in Claude Code / Cursor

330

Typed receivers in one shared catalog

1

Minutes to first working API call

"The best way to predict the future is to invent it."

Alan Kay · ·

Build, call, deploy, observe

Four operations. Four surfaces. Verb-surface parity throughout.

1

Build

Three paths to building on ONE. Chat: describe what you want and it gets scaffolded. Markdown: edit the agent .md file, save, sync. IDE: TypeScript SDK with full autocompletion against a typed API.

chat · markdown · IDE — any team member's choice

2

Call

Four surfaces. CLI: npx oneie, 110 commands, --json output. API: curl to api.one.ie, Bearer auth, standard JSON. SDK: @oneie/sdk, 6 verbs, fully typed. MCP: 168 tools in Claude Code, Cursor, or Windsurf.

CLI · API · SDK · MCP — same platform behind all four

3

Deploy

git push. Cloudflare builds, Workers deploy, a health check confirms. Minutes from commit to global edge — not a sprint, not a release train.

CF Workers + Wrangler · global edge

4

Observe

Dashboard: per-agent success rate and route history. CLI: oneie highways, oneie agents list, oneie status. MCP: ask "which route is winning for lead qualification?" from inside your editor. The data is the same regardless of surface.

dashboard · CLI · MCP — one source of truth

What the developer platform gives you

One platform. Four ways to reach it.

CLI — 110 commands, no installation

npx oneie. Scaffold a workspace, provision clients, push agents and skills, run workflows, manage wallets and staff — 110 commands across 17 groups. Structured JSON output via --json on the substrate, agent, skill, workflow, wallet and staff commands. An agent-aware front door: a human terminal gets greeted, CI and Claude Code get the zero-interaction path.

SDK — 6 verbs, fully typed

@oneie/sdk. signal, ask, mark, warn, fade, follow — plus typed access to all 330 receivers in the catalog. 29 subpath exports covering auth, payments, wallets, markets, and compilation. Works in Node, Bun, and Cloudflare Workers (import by subpath in Workers — the barrel is Node-only). Enforces the 4-outcome contract on every ask().

API — one door, standard REST

POST /api/ask/:receiver reaches any capability by name and returns a closed outcome — result, timeout, dissolved, or failure, never silence. Standard Bearer auth. Errors speak RFC 7807 problem+json. Rate limits answer honestly with RateLimit headers. A curl command is all the SDK you need for a first integration.

MCP — 168 tools in Claude, Cursor, Windsurf

@oneie/mcp. Install once, point your editor at it. 168 tools spanning agents, workflows, broadcasts, video, SEO, and tasks — plus generated tools for the allowlisted analytics functions. "Show me the top ten routes by strength" — the platform answers.

Docs checked against the code, not written on faith

The SDK, MCP and CLI READMEs are checked by a zero-LLM audit: every SDK subpath export, every hand-written MCP tool and every top-level CLI command must be documented or the check fails. The OpenAPI spec is checked the same way — zero phantom routes, every documented path backed by a real handler.

Docs — for people and for agents

Full documentation at /docs, including a written reference for each of the four surfaces. Every page is also raw markdown at /docs/<slug>.md, and the set is indexed at /llms.txt, so an agent reads exactly what a person reads. The OpenAPI spec is published at /openapi.yaml with a rendered viewer at /api/reference.

Developer experience vs. the alternatives

FeatureONEHosted AI SaaSSelf-hosted open source
CLI + API + SDK + MCP (4 surfaces)
Verb-surface parity (same operation, 4 ways)
SDK / CLI / MCP docs audited against code
OpenAPI spec with zero phantom routes
MCP tools in Claude Code / Cursor
6-verb SDK (signal/ask/mark/warn/fade/follow)
Total control of infrastructureHonesty: self-hosting on your own infrastructure wins on control — costs 1–3 months of DevOps time.

Full developer access on every plan

Annual billing pre-selected.

Starter

Full API access · CLI · SDK

$500/mo
5M credits/mo
Full REST API access
CLI (npx oneie)
@oneie/sdk
@oneie/mcp
Email support
Most popular

Agency

All 4 surfaces · full CLI · full MCP

$5,000/mo
60M credits/mo
Full CLI — 110 commands
Priority API rate limits
Custom webhook endpoints
Whitelabel + client workspaces
Priority support

Scale

Custom terms · negotiated SLA

$50,000
750M credits/mo
Custom API endpoints
Compliance documentation pack
Dedicated success manager
Custom SLA available
Custom contract terms

Developer questions

Four doors. One platform. Docs that cannot lie.

110 CLI commands. 168 MCP tools. Typed SDK. REST API with a published OpenAPI spec. Same operation, four surfaces. Build the way your team already works.

npx oneie — no install · open source · llms.txt for your agents