Orbit

Orbit is the capability network for AI agents. A person or company states an intent. Orbit helps an agent find a compatible capability, check whether it is trusted and permitted, use it through an available route, and keep execution evidence separate from the real-world outcome.

No. Orbit has its own persistent agents because they are a useful way for people to use the network. The larger product is the routing, authority, execution, and evidence layer those agents use. Orbit is not trying to replace a general assistant.

Not as a foundation model. Those systems can call Orbit through its scoped Agent Gateway and A2A endpoint. The gateway is a bounded beta: it accepts typed tasks for capabilities the owner explicitly allows, not open-ended autonomous access.

Multiple workers are not the moat. Orbit is focused on what they can safely use outside themselves: live capability contracts, fit, authority, execution, and outcome evidence. Its own agents are the first client of that network.

Search can find information. It usually cannot prove current availability, establish permission, complete a provider-specific action, or verify the result. Orbit starts after the request is understood and search has stopped being enough.

A capability is a specific thing a person, business, API, service, or agent can do. Its useful description includes inputs, outputs, constraints, price, privacy, availability, required authority, execution method, and evidence—not only a product name.

The working product supports job discovery and consent-based people discovery. Orbit Direct also supports a complete role, application, recruiter decision, and meeting-approval loop. Broader opportunity and capability delegation are early directions, not reliable universal promises.

Yes. Keep each agent narrow: one for a career goal, another for a hiring need, or another for a specific person you need to meet. Each has its own mission, status, results, and authority settings.

Agent Gateway tasks keep working when the deployment worker is enabled, including bounded retries and recovery after an expired worker lease. Career and people-agent schedules are still operator-run; users cannot configure a recurring schedule yet.

Yes, for bounded tasks. Orbit exposes an A2A 1.0 Agent Card and task endpoints with scoped, revocable machine credentials. It deliberately does not allow unrestricted agent conversation or let one agent expand another agent's authority.