An app your agents can actually use
You want your app callable by Claude and other agents. Orbit gives every app a REST API and an OpenAPI schema an agent can read and drive today, and a curated MCP server is the next step, not a promise we've already made.
Who's booked today?
Three today: Ava at 10:00, Marcus at 11:30, and Priya at 2:00 (pending).
The agent interface
A human's API can drown an agent. A raw one, too.
Developers are split, and both sides are right. One camp: “if I feed an OpenAPI spec to an LLM it can use it as a tool,” so a clean API is often all an agent needs. The other: “an API built for a human will poison your AI agent, you're not empowering it, you're drowning it.” The answer isn't a new protocol for its own sake. It's an interface an agent can actually read.
How it works
Agent-ready today. Curated MCP next.
Every Orbit app already speaks the interface agents understand: a REST API, an OpenAPI schema, and an llms.txt. That's enough for an agent to read your app and act on it now, and it's the foundation a first-class MCP server builds on.
REST plus OpenAPI, the interface agents read
Your data model generates a REST API and an OpenAPI 3.0 schema at /openapi.json. Point an agent at the spec and it can discover your app's shape and call it, the pattern skeptics rightly say is often all an agent needs.
An llms.txt so answer engines find your app
Every app publishes an llms.txt that lays out its pages in plain text, so LLMs and answer engines can understand what your app is and point people to it.
Honest edge: llms.txt today describes your app's pages, not its API endpoints.
A curated MCP server, on the way
The interface agents want is a tight, curated toolset, not a raw dump of every endpoint. Orbit's platform already runs an MCP server for building apps, and per-app MCP, your app exposed as a clean set of agent tools, is what we're building toward next.
Honest edge: today a built app is agent-reachable over REST and OpenAPI. It is not yet its own MCP server.
Where it fits
Build the app once. Every caller reads the same shape.
Your screens, your REST clients, and the agents that drive your app all read from one data model. Build it once, and the interface follows, for people and for agents.
Ship an app agents can drive
Build your app and get a REST API and OpenAPI agents can read today, ready for the MCP server coming next.