Orbit docs

Orbit takes a natural-language brief — "Senior fintech engineers in Berlin with payments experience" — runs a multi-source search, and returns a deduped list of people with LinkedIn URLs, titles, contact details, and a yes/no for each criterion in your brief.

Pick your surface

REST API

Mint a key → POST /v1/search → poll → export CSV. Any language, any stack.

MCP server

Connect Claude or any MCP client to Orbit's hosted server → orbit_search, orbit_status, orbit_results. OAuth, no key.

Claude Code plugin

/plugin install orbit → slash commands + market-map skill + Obsidian graph view.

ChatGPT app

Install the Orbit app in ChatGPT → search from any conversation. OAuth, no key.

How a project works

Every surface follows the same flow:

Submit a brief. The API returns a projectId immediately.
Wait. The project runs asynchronously — Orbit searches across multiple sources and evaluates each person against your criteria.
Retrieve. Page through the results as JSON, or export them as CSV.

A submitted search can't be edited — to search differently, submit a new brief. If Orbit can't act on a brief as written, the project reports status: "awaiting_input" with a clarificationQuestion saying why; submit a sharper brief. Every search draws on your workspace's credits and budget limits exactly as a search started from Slack does.

The API lives at https://api.orbitpeople.ai/v1. Its OpenAPI 3.1 spec is served live and unauthenticated at https://api.orbitpeople.ai/v1/openapi.json — import it into any generator, API client, or playground, or browse the interactive reference.