Jobo for CLI
Job data from your terminal.
jobo is a command-line client for the Jobo API. Every search filter is a flag, the bulk feed streams as JSONL with a resumable cursor, and job, company and filter lookups are one command each. Output is a table in a terminal and JSON when piped, so it composes with the tools you already script with. It ships an Agent Skill that teaches a coding agent the commands and the cost rules, and it prints the setup for connecting Jobo's MCP server to any supported AI client.
jobo search "data engineer" --location "Berlin, Germany" --work-model remote,hybridWhat can you do with the CLI integration?
Search jobs, stream the feed and look up companies from a terminal, with an Agent Skill that teaches coding agents to use it.
Every filter is a flag
The search flags are generated from the same filter contract the other connectors use, so a filter the API gains cannot be missing here.
Costs on stderr, data on stdout
Each billed request prints what it cost on stderr. Data goes to stdout as a table, JSON, JSONL or CSV, so piping stays clean.
A feed that needs a cap
jobo feed will not start without --max or --all, writes the cursor after every batch, and resumes from it after a crash.
An Agent Skill for coding agents
jobo skill install copies a skill that teaches an agent the commands, how to find valid filter values, and the cost rules it must respect.
MCP setup for any client
jobo mcp <client> prints the command to run or the config to paste for each supported coding agent, IDE and assistant. It changes no files.
How do you connect CLI to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Install
The CLI needs Node 20 or later and installs from npm once it is published there.
bashnpm install -g jobo-cli - 2
Save your API key
jobo auth prompts for the key without echoing it and stores it in a file only you can read. The JOBO_API_KEY environment variable takes precedence when set.
bashjobo auth - 3
Search
Search bills every job it returns, so the default page is 10 jobs. Use jobo filters to list the valid values for a flag.
bashjobo search "python engineer" --work-model remote --experience-level senior,lead --posted-after 7d - 4
Stream the feed
For volume, use the feed. It bills a job once per 30 days and needs an explicit cap.
bashjobo feed --max 500 --sources greenhouse,lever --work-models remote > jobs.jsonl - 5
Teach your coding agent
Install the bundled Agent Skill, or print it into an AGENTS.md for agents that read one instructions file.
bashjobo skill install
What goes wrong with CLI, and how do you fix it?
The things people actually hit when running Jobo in CLI.
- jobo feed refuses to run
- The feed streams every matching job and bills each one that is new to you, so it needs --max N or an explicit --all.
- A command says it is not available with a sandbox key
- A sandbox key serves search, job and company only. The feed, expired ids, geocoding and filter lookups need a live key.
- jobo usage does not show a balance
- The API reports the wallet and included jobs only on billed search and feed responses. Those commands print the figures on stderr; the billing page in the dashboard has the full picture.
- The command exits with code 4
- The balance cannot cover the request. The check prices the whole requested page, so retrying fails identically. Top up, or lower --page-size.
How do you get the most out of CLI?
- Keep --page-size and --max small while exploring. Job, company and filter lookups are free.
- Pass --cursor-file to jobo feed so a long scan resumes instead of starting again.
- In scripts, read the key from JOBO_API_KEY and branch on the exit code rather than parsing error text.
Which other Jobo integrations work alongside CLI?
Start pulling live jobs into CLI
One API key covers every integration, and the same job index sits behind all of them.













