Glossary

Every Jobby.dev-specific term, defined. If you came here looking for a term that isn't listed, drop us a note.

Advance / Pass / Follow-up async: The three decision states a recruiter sets after an interview. Advance flows the candidate into the recruiter's ATS; pass closes the match cleanly; follow-up-async holds the candidate in a team-visible state.
Bonus minutes: Live-event minutes granted outside the billing cycle (early-customer programs, service-issue make-good). Consumed before plan minutes, expire 90 days from grant date.
Discovery feed: The home-page list of currently-live events visible to seekers. Also accessible programmatically via jobbydev_live_now / GET /api/v1/live-events.
Humans-only rule: The platform invariant that agents can drive every administrative surface but the live interview itself is reserved for human seekers and human recruiters. See the humans-only rule.
Live event: A window of time during which a recruiter (or recruiter team) is available to interview. Live events have one or more roles attached. Time only counts toward billing while the event is in the live state. See creating events.
Match: A pair (seeker, role) the matchmaker has scored above the fit threshold. Both sides must accept within ~30 seconds for the interview to start.
Match score: The numeric output of the matchmaker for a (seeker, role) pair. Inputs: skills overlap, years-of-experience band, comp-range overlap, location/remote fit, work-auth compatibility, freshness boost.
MCP (Model Context Protocol): An open standard for connecting LLM agents to external tools. Jobby.dev publishes a tool catalog (the jobbydev_* namespace) any MCP-capable agent can drive. See MCP overview.
Off-session consent: A flag on the Stripe customer (off_session_consent: "yes") granted automatically the first time a recruiter completes a Stripe Checkout. Required before the agent can fire silent off-session upgrade charges. See the humans-only rule.
Personal Access Token (PAT): A user-minted bearer token with the jbb_ prefix used to authenticate REST and MCP requests. Tokens are scoped to specific capabilities (e.g. queue:write); the user picks scopes at mint time. See API authentication.
Queue: The ordered list of seekers waiting for a match in a specific live event. Each seeker can be in exactly one queue at a time.
Report card: Post-interview structured ratings (fit, communication, technical signal, each 1-5) plus optional recruiter-notes and candidate-facing summary. Drives the advance / pass / follow-up-async decision.
Role: Structured matching input — title, required skills, comp range, location, work-auth. Roles attach to live events and feed the matchmaker. See posting roles.
Room URL: A short-lived (30-second) Daily.co room URL handed to a matched pair once both have accepted. The browser opens the room directly; the URL is single-use and bound to the user's session.
Scope: A permission string a Personal Access Token carries. Examples: profile:read, queue:write, billing:write. The token can do exactly the actions its scopes permit and nothing else.
Seat: One recruiter on a team plan. Seat counts vary by plan tier; adding seats beyond plan allowance prompts an upgrade.
Webhook subscription: A registered HTTPS endpoint Jobby.dev pushes event payloads to. Configured at /account/webhooks or via jobbydev_webhook_create. See webhooks overview.