Job Postings Skill

Add job postings to your app

data10 credits/callMCP · RESTNew
See how to connect

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. You switch it on with a single toggle — no SDK and no endpoint wiring — and it answers over MCP or REST using the same key as every other skill.

A real response from the Job Postings Skill — exactly what your agent gets back when it makes the call.

vervekit · jobpostingstool call
{
  "company": "airbnb"
}
result
company
Airbnb
boardTotal
174
truncated
false
total
174
page
1
pages
4
count
2
jobs
[ 2 items ]
Run it with your own input. Live calls happen in your dashboard, on your key.
Sign in to try

One toggle, a new capability

Enable Job Postings and your app or agent can add job postings to your app on demand — no SDK, no endpoint wiring. It answers over MCP or REST using the same key as every other skill.

A tool agents call themselves

Over MCP, Job Postings appears to your model as the jobpostings tool it invokes whenever a task needs it — you don't write the glue, the agent reaches for it.

REST from any backend

Prefer to call it directly? Any language that can send a GET can hit Job Postings to add job postings to your app inline in your own server-side code.

Once enabled, this skill is reachable two ways — pick whichever fits how you build. Both use the same key.

For AI agentsMCP

It appears to your model as a callable tool. No extra code — the agent invokes it when a task needs it.

jobpostings
For apps & backendsREST

Call it from your server with one request and your key. Node, Python, Go — anything that can send a GET.

GET /v1/jobpostings
  • “Enable Job Postings and ask your agent to add job postings to your app.”
  • “Use the Job Postings skill for me.”

Job Postings Skill, answered

How to connect it over MCP or REST.

How do I add Job Postings to my app or agent?
Enable the Job Postings Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the jobpostings tool) or over REST (call it from any backend). No SDK to install and no endpoint to wire.
MCP or REST — which should I use?
Both work off one key. Use MCP when an AI agent should decide when to add job postings to your app — the skill shows up as a callable tool. Use REST when your own server-side code should call it directly. Many apps use both.
Which agents and frameworks does it work with?
Any MCP client — Claude, Cursor, LangChain, and custom agents all speak the Model Context Protocol, so Job Postings appears as a standard tool with nothing skill-specific to integrate.
How many credits does a Job Postings call cost?
Each call costs 10 credits. Every skill rides the same key and the same connection, so enabling more skills doesn't add more integrations to manage.
Do I need to install anything?
No SDK and no endpoint wiring — enabling the skill is a toggle. You point your agent at the VerveKit MCP endpoint (or call REST) and Job Postings is available immediately.
Where does the data come from, and what shows on my bill?
VerveKit runs on APIVerve, our production data engine; Job Postings is one of 300+ skills on the same key. Invoices and card statements show APIVERVE.

Other ways to use Job Postings

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

Give your software a way to act on the world.

Scaling in production?

The same key runs from your first prototype to millions of calls — on APIVerve's rails, 99.9% uptime.

See pricing