Job Search Skill

What this skill does

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. 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.

See it work

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

vervekit · jobsearchtool call

{
  "keyword": "engineer"
}

result

page: 1
count: 2
hasMore: true
jobs: [ 2 items ]

Run it with your own input. Live calls happen in your dashboard, on your key.

Ways to use it

One toggle, a new capability

Enable Job Search and your app or agent can add job search 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 Search appears to your model as the jobsearch 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 Search to add job search to your app inline in your own server-side code.

Use it in your app

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.

jobsearch

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/jobsearch

Ask your agent

“Enable Job Search and ask your agent to add job search to your app.”
“Use the Job Search skill for me.”

Job Search Skill, answered

How to connect it over MCP or REST.

How do I add Job Search to my app or agent?

Enable the Job Search Skill on VerveKit, then reach it two ways with the same key: over MCP (it appears to your agent as the jobsearch 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 search 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 Search appears as a standard tool with nothing skill-specific to integrate.

How many credits does a Job Search call cost?

Each call costs 20 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 Search is available immediately.

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

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

One toggle, a new capability

A tool agents call themselves

REST from any backend

Job Search Skill, answered

Other ways to use Job Search

Give your software a way to act on the world.

Scaling in production?