Job Postings

Agent capabilitydata10 credits/callMCPNew
MCP tooljobpostings

Job Postings is a jobs API that returns the open positions on a company's public career board. Every job comes back in the same shape: title, department, team, locations, remote and workplace type, employment type, posting date and apply link. Filter by keyword, location, department, employment type, posting date or remote. Paid plans add the full job description and salary ranges where the company publishes them.

Ground answers in real data

Enable Job Postings 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 Postings 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 postings at answer time and can carry the source with the result, so the reasoning stays current and auditable.

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_••••" }
    }
  }
}
# “jobpostings” is now a tool your agent can call

Each call returns structured fields your agent can read.

  • company
  • boardTotal
  • truncated
  • total
  • page
  • pages
  • count
  • jobs

Job Postings, answered

How to ground an agent in it over MCP.

How do I give my agent Job Postings?
Enable it on VerveContext and point your agent framework at the VerveContext MCP endpoint. Job Postings then appears to the model as a tool named jobpostings, 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 Postings is exposed as a standard tool, so nothing source-specific is required.
Can the agent cite Job Postings?
Job Postings 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 Postings call cost?
Each call costs 10 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 Postings 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 Postings is one of 300+ sources on the same key. Invoices and card statements show APIVERVE.

Other ways to use Job Postings

Same data, same VerveContext account, same credit balance — one key works on all of them.

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

Scaling up?

Volume pricing, custom SLAs, and dedicated support for high-traffic teams.

Contact sales