For agent developers
Build against a live on-demand job fair.
Jobby.dev ships a Model Context Protocol server, a public OpenAPI spec, and a personal-access-token flow so your agent can discover live sessions, search open roles, and queue developers into interviews. The video room itself is humans-only — agents never accept matches.
The humans-only booth
An agent can discover a live session, match a seeker to a role, and drop them in the queue — but the seeker has to tap I’m here in the Jobby.dev app to enter the video room. Match acceptance is not exposed as a token scope: the invariant is architectural, not policy. Every person a recruiter interviews on Jobby.dev is a human, always.
Two transports
MCP (stdio or HTTP)
Install @jobbydev/mcp in any MCP host or POST JSON-RPC 2.0 at /api/mcp. Same tool surface either way.
REST (OpenAPI 3.1)
Canonical endpoints under /api/v1/*. Public read surface is zero-auth; writes use scoped personal access tokens.
Tool surface
| Tool | Scope | What it does |
|---|---|---|
| jobbydev_live_now | public | List live and upcoming Jobby.dev sessions. |
| jobbydev_search_jobs | public | Search open roles by stack, seniority, salary. |
| jobbydev_get_event | public | Fetch a single live event by slug. |
| jobbydev_queue_join | queue:write | Drop the authenticated seeker into a queue. |
| jobbydev_queue_status | queue:read | Check the seeker's current queue status. |
| jobbydev_matches_list | matches:read | List recent matches for the seeker. |
| jobbydev_profile_get | profile:read | Read the seeker's profile. |
No queue:acceptscope exists. That’s intentional — see the humans-only booth above.
Identity & tokens
Send X-Agent-Identity with every request. The string you pick (e.g. claude-desktop/0.7.0) is stored on any queue entry your caller creates and surfaced to the counterparty UI so humans can see which agent routed the match.
Scoped writes require a personal access token minted by the end user at /settings/api-tokens. Tokens use the jbb_ prefix and carry explicit scopes: the user chooses what the agent can do on their behalf.
Rate limits are per-token for authenticated calls and per-IP for public discovery. The MCP HTTP endpoint itself is rate-limited at 60 requests per window per IP.
Install
Want your agent or IDE in the Jobby.dev directory? Mail hi@jobby.dev with a pointer to your install flow.