Jobo for v0
A job board from a prompt, on live data.
v0 builds an app from a description, and Jobo supplies the jobs. The generated app calls Jobo's REST API from a Route Handler or Server Action, with your API key stored in v0's Environment Variables so it never reaches the browser. v0's agent can also connect to Jobo's MCP server, which lets it look at real listings while it builds; that connection is for the agent, not for the published app.
- API
- https://connect.jobo.world
- Auth
- X-Api-Key header
- Key stored in
- Environment Variables
- Called from
- a Route Handler or Server Action
- MCP for the agent
- Supported
What can you do with the v0 integration?
Build a job board or sourcing tool in v0 on live job data, with your API key kept server-side.
Real listings from the first prompt
The app v0 generates shows live jobs collected from employer career sites, not placeholder rows you replace later.
The key stays server-side
Your API key lives in v0's Environment Variables and is read by a Route Handler or Server Action. The browser calls your app, and your app calls Jobo.
Filters the API already has
Location, work model, employment type, experience level, skills, salary and posting date are request parameters, so the builder wires up filter controls instead of inventing its own matching.
A prompt that carries the contract
The search integration prompt in Jobo's docs spells out the request shape and the mistakes that still return 200, which a builder's agent otherwise gets wrong.
Live job search while you build
v0's agent can connect to Jobo's MCP server and look at real listings and valid filter values as it writes the app.
How do you connect v0 to Jobo?
One-time setup. After this, the data keeps itself current.
- 1
Create a Jobo API key
Sign up, open Developers → API Keys in the Jobo dashboard and create a key. New accounts start with a $5 balance and need no credit card. A sandbox key returns fictional jobs for free while you build.
- 2
Add the key to v0's Environment Variables
Open the project menu, then Settings → Environment Variables, and add JOBO_API_KEY. Select at least Development (the v0 preview) and Production (the published app). Do not prefix the name with NEXT_PUBLIC_, which would expose it to the browser.
- 3
Prompt the build
Tell v0 what to build and where the data comes from. The call must run in a Route Handler or Server Action, never in browser code. Jobo's docs have a longer prompt that covers filters, facets and error handling.
textAdd job search to this app using the Jobo API. - Call POST https://connect.jobo.world/api/jobs/search from server-side code only. - Send my key from the JOBO_API_KEY secret in the X-Api-Key header. Never expose it to the browser. - Request body: {"queries": ["<keywords>"], "locations": ["<place>"], "page": 1, "page_size": 20}. - The response has a "jobs" array and a "total". Show title, company.name, locations and date_posted, and link each job to its listing_url. - Add keyword and location inputs and pagination. On HTTP 402 show "out of credits" instead of retrying. - 4
Optional: connect Jobo's MCP server to v0
Open the + menu in the prompt form and select MCPs, then configure a custom MCP server: enter the server URL, choose OAuth as the authentication and complete the sign-in. The server URL is https://jobs-mcp.jobo.world/mcp, and you sign in with your Jobo account rather than a key.
- 5
Publish
Publish the project. Variables scoped to Production apply to the live app. After adding or changing a variable, send a new message so the chat and its preview pick it up.
What goes wrong with v0, and how do you fix it?
The things people actually hit when running Jobo in v0.
- The API key is visible in the browser
- The generated code is calling Jobo from the page. Ask v0 to move the call into a Route Handler or Server Action and read the key from Environment Variables, then create a new key in the Jobo dashboard and delete the exposed one.
- A filter returns no jobs
- Filter values are lowercase, hyphenated and matched exactly, and an unrecognised value is not an error. Check them against the documented values: full-time rather than full_time, onsite rather than on-site.
- Searches start failing with HTTP 402
- The balance cannot cover the request. Search is billed per job returned, so a results page of 20 jobs costs 20 jobs. Top up, or lower page_size.
- The published app cannot use the MCP connection
- That is how v0 documents it: a custom MCP server gives tools to v0's own agent while it builds, not to the app it generates. The app reads jobs through the REST API.
- The preview cannot read the variable
- The v0 preview only reads variables available to the Development environment, and it cannot read a variable stored with Vercel's sensitive type. Add JOBO_API_KEY as an ordinary variable with Development selected.
How do you get the most out of v0?
- Build against a sandbox key first. It returns fictional jobs for free, so a prompt that loops on a broken request costs nothing.
- Keep page_size at what the page shows. Search bills every job returned, not every job displayed.
- Cache results for repeated searches rather than calling the API on every page view.
Which other Jobo integrations work alongside v0?
Start pulling live jobs into v0
One API key covers every integration, and the same job index sits behind all of them.













