Jobs data API
5 endpoints for Jobs: linkedin, linkedin search, search, post, xing. One API key, one JSON schema, as MCP tools or REST.
Endpoints
Call any of them over MCP with call_endpoint and its path, or over REST.
| Endpoint | Returns | Credits | Cache |
|---|---|---|---|
| linkedinGET /v1/jobs/linkedin | One LinkedIn posting through the guest jobs frontend: description, criteria and location. | 1 | 10 min |
| linkedin/searchGET /v1/jobs/linkedin/search | Search LinkedIn job postings by keyword and location. | 1 | 2 min |
| searchGET /v1/jobs/search | Remote job openings matching a keyword, with company, location, salary range and tags. | 1 | 2 min |
| postGET /v1/jobs/post | One remote job posting by URL: title, company, location, salary, dates and full description. | 1 | 10 min |
| xingGET /v1/jobs/xing | One Xing job posting with company, location, employment type and salary when the ad states it. | 1 | 10 min |
Connect your agent over MCP
Remote MCP server: https://data.openkrill.app/mcp with your key in the x-api-key header.
claude mcp add --transport http krilldata \
https://data.openkrill.app/mcp \
--header "x-api-key: YOUR_API_KEY"{
"mcpServers": {
"krilldata": {
"url": "https://data.openkrill.app/mcp",
"headers": {
"x-api-key": "YOUR_API_KEY"
}
}
}
}{
"mcpServers": {
"krilldata": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://data.openkrill.app/mcp",
"--header",
"x-api-key:${API_KEY}"
],
"env": {
"API_KEY": "YOUR_API_KEY"
}
}
}
}