Job Search

What it grounds

Job Search is a jobs API that searches the open positions at thousands of companies at once. Search by job title keywords, location, country, remote work, employment type, posting date or company, and get the newest matching jobs first, each with its title, company, location, country, workplace type, posting date and apply link. Paid plans add salary ranges, a minimum salary filter, larger pages and each job's full description.

Ways to ground with it

Ground answers in real data

Enable Job Search and it becomes a tool your agent calls over MCP to check itself against live data before it answers — grounding the response instead of guessing.

On the same endpoint and key

Job Search rides the one VerveContext MCP endpoint alongside 300+ other sources, so adding it to an agent is a toggle, not an integration.

Traceable and current

The agent pulls job search at answer time and can carry the source with the result, so the reasoning stays current and auditable.

Connect over MCP

Point your agent framework at the VerveContext endpoint. Every enabled source — this one included — becomes a tool the model can call. No per-source plumbing.

context.json

{
  "mcpServers": {
    "vervecontext": {
      "url": "https://api.vervecontext.com/v1/mcp",
      "headers": { "x-api-key": "vc_live_••••" }
    }
  }
}

# “jobsearch” is now a tool your agent can call

What it returns

Each call returns structured fields your agent can read.

page
count
hasMore
jobs

Job Search, answered

How to ground an agent in it over MCP.

How do I give my agent Job Search?

Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. Job Search then appears to the model as a tool named jobsearch, which it calls when a task needs it — no per-source plumbing.

Which agents and frameworks can use it?

Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol. Job Search is exposed as a standard tool, so nothing source-specific is required.

Can the agent cite Job Search?

Job Search is a capability rather than a factual source, so it isn't something to "cite" — but it runs on the same real-data layer, over the same MCP endpoint and key as every grounding source.

How many credits does a Job Search call cost?

Each call costs 20 credits. Scoped keys let you grant an agent only the sources it should reach, and usage logs show exactly what was pulled to ground each answer.

How current is the data?

Job Search is served live from APIVerve's production data engine and pulled at the moment the agent calls it, so answers reflect the world now rather than the model's training cutoff.

Where does the data come from, and what shows on my bill?

VerveContext runs on APIVerve, our production data engine; Job Search is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

Ground alongside

Browse all sources

Ground answers in real data

On the same endpoint and key

Traceable and current

Job Search, answered

Other ways to use Job Search

Ground your agents in Job Search. Connect over MCP, enable the source, and every answer carries its receipts.

Scaling up?