Build your remote job search
Find remote roles by job title, location, seniority, salary, and technology. Use the REST API from your application, connect an agent through MCP, or run a search from your terminal. All three use the same authenticated job-search service.
Get an API key
Sign in to manage your API key. Live searches require an active subscription. Keep keys on your server or in your agent client's secret storage. Send the key as an Authorization: Bearer header.
Make your first request
curl https://www.remoterocketship.com/api/openclaw/jobs/ \
-H "Authorization: Bearer $RR_API_KEY" \
-H 'Content-Type: application/json' \
-d '{"filters":{"jobTitleFilters":["Software Engineer"],"locationFilters":["United States"],"itemsPerPage":20}}'Read the complete API documentation or import the OpenAPI 3.1 contract. Responses include jobOpenings, totalCount, and pagination. This service uses REST; it does not provide GraphQL.
Try the sandbox
The sandbox returns a fixed fictional job, ignores filter values, and requires no key. It does not access real listings, change your account, or consume your job-search quota. Use it to check your request and response handling.
Sandbox endpoint: POST /api/openclaw/sandbox/ with {"filters":{}}.
Connect an MCP client
Streamable HTTP endpoint: https://www.remoterocketship.com/api/openclaw/mcp/. Initialization and tool listing are public. Set your API key as an Authorization: Bearer header for live searches. The server exposes search_remote_jobs, with typed filters and pagination. Tool calls use your existing subscription and quota.
Use the CLI
Download the official CLI package. Requires Node.js 20 or later. This downloadable package is available from this site; npm registry publication is pending.
npm install -g https://www.remoterocketship.com/downloads/remoterocketship-cli-0.1.0.tgz
remoterocketship search --sandbox
# Set RR_API_KEY in your environment for a live search.
remoterocketship search --filters '{"jobTitleFilters":["Software Engineer"]}'Handle limits and errors
Standard accounts have a daily quota of 500 requests or 3,000 returned jobs, whichever is reached first. Quotas are per subscriber, shared across keys and clients, and reset at midnight UTC. Requests return up to 50 jobs. Errors contain message, code, and hint. A 429 includes Retry-After in seconds; wait before retrying.
RateLimit-Policy and RateLimit follow draft-ietf-httpapi-ratelimit-headers-11, an IETF draft, not a published RFC. RateLimit describes remaining requests (r) and seconds to reset (t). X-JobLimit-Limit, X-JobLimit-Remaining, and X-JobLimit-Reset describe the separate job quota; these are application-specific headers. Remaining quota is advisory under concurrent requests. Unlimited accounts omit quota headers.
