Connect an AI assistant to Orbit
Updated
mcp, ai assistant, claude, chatgpt, connector, sign in from an assistant, connected assistants, disconnectThis is for recruiters who want an AI assistant to work their Orbit roles: read a role’s ranked candidates, draft and calibrate roles, and record shortlists and rejections. The assistant connects to Orbit’s MCP server, https://api.wipperoz.com/v1/mcp, by signing in to Orbit or with an API key. These steps are for signing in, which is how ChatGPT connects and one of the ways Claude does.
Add Orbit to your assistant
In ChatGPT or Claude, add a custom connector with the address https://api.wipperoz.com/v1/mcp, then connect it. Your assistant opens Orbit.
Sign in to Orbit
Sign in with your Orbit account. Connect an assistant names the assistant and the site you go back to afterwards.
Choose the account
If you’re on more than one Orbit account, choose the one it works for under Account.
Choose what it can do
Under What it can do, tick what the assistant may do:
- read jobs: see your roles, their calibration, the pool preview and what Orbit did on each.
- draft roles: draft new roles and calibrate them. It never publishes or closes a role.
- read candidates: read your roles’ ranked candidates as Orbit shows them, without contact details. Only an Admin can allow this.
- record decisions: record your shortlists, rejections and stage moves. It never emails a candidate.
Accept the addendum, if asked
If you ticked read candidates, read the AI assistant addendum and tick I accept the AI assistant addendum for this account.
Allow it
Select Allow. Orbit takes you back to your assistant, which can now use what you allowed.
It says only an Admin can let an assistant read candidates
Untick read candidates and select Allow again, or ask an Admin of the account to connect the assistant.
It says This request has expired
A connection request lasts 10 minutes. Start the connection again from your assistant.
It says This is a Virtual CV sign-in
Assistants connect to Orbit accounts. Sign in with your Orbit account and start again from your assistant.
Connect with an API key instead
Claude Code, Codex, Cursor and VS Code send an API key instead of signing in. In the Claude apps, a custom connector can also carry a key as a request header, where your Claude organization has that option. An organization Owner sets it.
- Create a key with AI assistant or AI assistant, read only. See Create an API key for the Orbit API.
- Add
https://api.wipperoz.com/v1/mcpto your assistant, with the headerAuthorizationset toBearerfollowed by the key. The MCP server docs show how for each assistant.
Make one key per assistant, so you can revoke one without the others.
What an assistant can and can’t do
It can:
- list your roles, with whether each ad is managed and the role agent’s status;
- draft a role from a description, and calibrate it;
- show how many people in the pool fit a role;
- read a managed role’s candidates in your taste order, with their fit, the AI assessment, their screening and what is verified, as Orbit shows them;
- shortlist someone, reject them with a reason or move them to a stage;
- read the role’s What Orbit did.
It never publishes, closes or manages a role, turns the role agent on, starts a screening or spends anything. It never contacts a candidate, never sees email addresses, phone numbers or your team’s notes, and works only on the account it’s connected to. It reads candidates on managed ads only.
When an assistant rejects someone
A decision an assistant records emails nobody. If Orbit would normally have emailed that rejection, the candidate’s page shows Not notified. The candidate isn’t told, and their own Applications page doesn’t show it, until you select Send the rejection email.
The AI assistant addendum
A key or connection that reads candidates sends candidate data to the assistant and the AI provider behind it, which your account chooses. So an Admin has to accept the AI assistant addendum first. Orbit records who accepted it, when and which version.
See or disconnect an assistant
Select Settings in the sidebar, then API keys. Connected assistants lists each assistant connected by signing in, with what it may do, who connected it, when, and when it was last used. To disconnect one, select Revoke, then Disconnect now: its next request is refused. An Admin can disconnect any assistant, and a member can disconnect the ones they connected.
An assistant that goes 30 days without using Orbit has to connect again. To stop an assistant that uses a key, revoke the key on the same page.