Skip to main content
jobo is a command-line client for the Jobo API. Every search filter is a flag, the feed streams as JSONL with a resumable cursor, and output is a table in a terminal and JSON when piped.
The CLI is built and tested but not on npm yet, so npm install -g jobo-cli does not resolve today.
For what all connectors share, see the connectors overview.

Install and authenticate

The CLI needs Node 20 or later. jobo auth prompts for the key without echoing it, checks it with a request that never uses credits, and saves it to a file only you can read. JOBO_API_KEY takes precedence when set, and --api-key on any command beats both.

Commands

Run jobo <command> --help for every flag.
  • Every filter of POST /api/jobs/search is a flag: the filter’s name in kebab-case, with an --exclude- twin where the API has one.
  • --page-size defaults to 10. --max N walks whole pages up to N jobs and never past it.
  • Date flags take an ISO 8601 timestamp or a relative time such as 24h, 7d, or 2w.
  • Use jobo filters to list the valid values for a flag.

Feed

The feed streams every matching job and bills each one that is new to you, so it won’t start without --max N or --all. The cursor is written after every batch; pass --cursor or --cursor-file to resume a scan that stopped.

Output

Data goes to stdout; costs, progress, cursors, and errors go to stderr, so piping stays clean. --json, --jsonl, --csv, and --table choose the format, --fields chooses the columns, and -o FILE writes to a file (it refuses to overwrite without --overwrite).

Agent Skill

The CLI ships an Agent Skill, a SKILL.md folder that teaches a coding agent the commands, how to find valid filter values, and the cost rules it must respect.

Sandbox keys

A sandbox key serves search, job, and company. Every other command answers that it isn’t available with a sandbox key.

Related: MCP server

An agent that supports MCP can search Jobo directly, with OAuth sign-in instead of an API key. jobo mcp <client> prints the setup.