API and MCP
Read public job data directly or connect an MCP-capable agent with a scoped, metered API key.
Use the public HTTP API for a script or data reader. Use MCP when you want an AI client to search jobs, inspect details, find similar roles, and participate in a job discussion.
Read jobs without a key
The feed API is public:
curl -s 'https://www.remotera.ai/api/jobs?accepts_country=DE&has_salary=true&limit=10'The list response contains jobs and total. Use count_only=1 when you only
need the result count.
Common parameters include:
| Parameter | Example |
|---|---|
accepts_country | DE |
worldwide_only | true |
role_type | backend |
experience_level | senior |
employment_type | full-time |
skills | `React |
skills_match | all |
languages | en,de |
salary_min_usd | 120000 |
has_salary | true |
search | fintech |
sort | date, salary, or relevance |
limit, offset | pagination |
Feed-page URL parameters are not identical to API parameters. See URL parameters only when generating browser links.
Anonymous job responses can redact employer application URLs while retaining
the public job facts. Automated anonymous traffic is rate-limited and may
receive a verification challenge. Pass an explicit limit and cache responses
you do not need to refresh.
Create an MCP key
Sign in and open API keys.
Create a key and copy the rmk_live_… secret immediately. The raw value is
shown once; only its hash is stored.
Open MCP, copy the client configuration shown there, and replace the placeholder token with your key.
The server URL is:
https://mcp.remotera.ai/mcpKeys use bearer authentication and the mcp scope. Revoke a key from the API
keys page if it is exposed or no longer used.
MCP tools
| Tool | Use it for |
|---|---|
search_jobs | Search compact job cards with pagination. |
get_job | Fetch full details for a public job id. |
similar_jobs | Find semantic neighbors of a job. |
react_job | Add or remove a public reaction. |
comment_job | Add a public comment. |
submit_application | Reserved placeholder; do not build against it. |
Read tools spend credits. Search charges per page, so narrow the query before paging through a broad result. Reactions and comments use daily action caps instead. The MCP page displays the current cost and cap for every tool—use that live table rather than hard-coding prices from documentation.
Watch and control usage
API keys shows the current balance, recent ledger entries, and short-term spend. The full activity page groups usage by operation and source.
Server-side tool failures are eligible for a refund; invalid requests are not. Credits refresh by plan period and do not affect the website, alerts, CV tools, or extension.
Keep agents efficient:
- search narrowly before requesting another page;
- retain public ids and use
get_jobonly for serious candidates; - cache stable details inside your own workflow;
- treat comments as public user-generated content;
- never place a key in a repository or client-side bundle.