MCP and REST tools for agent builders

Remoote for Agents

Give your job-search agent a structured source of remote roles, salary signals, location rules, canonical Remoote links, scoped apply intents, and job alerts — without scraping pages or exposing raw employer apply URLs.

Public tools are available without auth for discovery. Logged-in users can create a scoped token when their agent needs account-tied workflows such as apply intents or alerts.

Public searchScoped tokensNo raw apply URLsMCP + REST

Set up MCP Create a token See pricing

Tool flow

Search

Find matching remote roles with structured filters.

Reason

Check salary visibility, skills, and location constraints.

Act safely

Use scoped tokens for alerts or confirmation-required apply redirects.

What your agent can safely do today

The public surface is capped and safe for discovery. Token-authenticated calls add user-specific workflows while keeping Remoote entitlement checks and user confirmation in the loop.

Search without scraping

Find matching remote roles by keyword, skill, country or region, location tag, seniority, employment type, and salary availability.

Answer salary questions carefully

Compare salary ranges for a filtered search when enough normalized compensation data exists, with sparse searches called out instead of overconfident answers.

Create user-confirmed apply intents

With a scoped token, agents can request a Remoote apply redirect that still requires user confirmation and preserves entitlement checks.

Create job alerts

With the alerts scope, agents can create daily or weekly Remoote alerts tied to the user account instead of running repeated broad searches.

Setup

Choose the interface your agent needs

Start with MCP for tool-shaped agent calls. Use REST when you need to inspect schemas, reproduce requests, or build a small integration service.

Recommended for agents

Set up the MCP endpoint

Use MCP when your agent supports remote JSON-RPC tools. Public calls need no token. Add an Authorization bearer token only when calling account-tied tools such as apply intents or alerts.

POST https://api.remoote.app/remoote/agents/mcp
Public auth: none
Token auth: Authorization: Bearer rma_...
Tools: search_jobs, get_job, get_salary_stats, get_top_jobs, create_apply_intent, create_alert

Useful for debugging

Use REST when you need to inspect a call

REST mirrors the agent service layer and is useful for debugging, smoke tests, and simple backend workflows. For chat agents and multi-step assistants, prefer MCP.

GET  https://api.remoote.app/remoote/agents/tools
POST https://api.remoote.app/remoote/agents/search_jobs
GET  https://api.remoote.app/remoote/agents/jobs/{job_id}
POST https://api.remoote.app/remoote/agents/salary_stats
POST https://api.remoote.app/remoote/agents/top_jobs
POST https://api.remoote.app/remoote/agents/apply_intent
POST https://api.remoote.app/remoote/agents/alerts

Authenticated beta

Create a scoped token for user workflows

Tokens are created by logged-in users and shown once. Store the token in your agent secret store, then send it as a standard bearer token. Revoke it from Remoote if a device or workflow no longer needs access.

Create or revoke a token

jobs:search

Search public/authenticated job results

jobs:read

Read one public job record

apply:intent

Create user-confirmed apply redirects

alerts:write

Create job alerts for the user

Authorization: Bearer rma_...

Tool surface

Tools your agent can call

Each tool returns structured data with practical limits and a safe next step back to Remoote.

`search_jobs`

Public or token

Search active remote roles with supported filters: query, skills, excluded skills, country or region, location tag, seniority, employment type, and whether salary must be present.

`get_job`

Public or token

Return one public job record with title, company, salary fields, location rules, skills, excerpts, and the Remoote URL the user should open before applying.

`get_salary_stats`

Public or token

Calculate salary stats for a filtered job set when enough disclosed, normalized compensation data is available. Sparse searches return no stats instead of a weak answer.

`get_top_jobs`

Public or token

Return a capped short list of remote jobs for discovery prompts, daily review flows, or “show me what’s new” experiences.

`create_apply_intent`

Token required: apply:intent

Create a user-confirmed Remoote apply redirect for an authenticated user. It returns a Remoote URL, not a raw employer apply URL.

`create_alert`

Token required: alerts:write

Create a daily or weekly Remoote job alert for the authenticated user from structured criteria such as query, skills, country, seniority, and salary visibility.

Copy-paste examples

Smoke-test the endpoint

Use these examples with curl or adapt them for any self-hosted agent, OpenClaw-style workflow, or MCP client that can call a remote JSON-RPC endpoint.

Anonymous MCP

Search current remote jobs

No token is required for public discovery calls. Results are capped and return Remoote URLs instead of employer apply URLs.

curl -sS \
  -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"search_jobs","arguments":{"query":"python","limit":3,"salary_required":true}}}' \
  https://api.remoote.app/remoote/agents/mcp

Token-authenticated MCP

Create an alert

Create a scoped token on /agents/connect, store it as REMOOTE_AGENT_TOKEN, and only grant scopes your workflow needs.

export REMOOTE_AGENT_TOKEN='rma_...'

curl -sS \
  -H 'content-type: application/json' \
  -H "Authorization: Bearer $REMOOTE_AGENT_TOKEN" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"create_alert","arguments":{"name":"Python remote jobs","criteria":{"query":"python","salary_required":true},"frequency":"daily","limit":10}}}' \
  https://api.remoote.app/remoote/agents/mcp

Prompt patterns

Prompts that use the tools well

Good prompts give the agent a role, location, salary, or constraint to check. For account-tied actions, tell the agent to ask before creating apply redirects or persistent alerts.

“Find remote backend jobs open to candidates in Poland that mention PostgreSQL.”

“Show me senior remote marketing jobs that disclose compensation, then link me to each Remoote page.”

“Compare salary stats for remote data analyst roles in Europe and tell me if the sample is too small.”

“Create a daily alert for remote customer support jobs open to Portugal with salary listed.”

“I want to apply to this Remoote job. Create an apply intent, then ask me to confirm before opening it.”

Limits your agent should explain

Public tools are read-only and capped. They return public Remoote fields and canonical Remoote URLs, not raw employer apply links. Job availability can change, salary disclosure varies by employer, and remote does not always mean work-from-anywhere. The agent should ask the user to open the Remoote job page before applying.

Authenticated tools stay scoped

Apply intents and alerts require a user-created token with the matching scope. Apply intents return a Remoote redirect and `requires_user_confirmation=true`; they do not hand agents raw employer application links. Resume-aware ranking and richer partner access are planned for later.

Build with Remoote job data

Use Remoote when your assistant needs remote-job options with enough structure to reason about role fit, salary visibility, and location constraints. Create a scoped token when the agent needs to create alerts or ask for a user-confirmed apply redirect.

Connect your agent

Need higher limits or a partner integration? Contact Remoote.