Himalayas provides three machine-readable interfaces for AI agents — an MCP server for real-time conversational search, a JSON API for programmatic access, and an RSS feed for monitoring new listings. All three are free, require no API key, and return structured data about remote jobs and companies. For exact field values and enums, see the Data Dictionary.
What AI agent integrations does Himalayas offer?
Himalayas offers three ways for AI agents, LLMs, and automated tools to access remote job data:
| Integration | Best for | Format | Data |
|---|---|---|---|
| MCP Server | AI assistants, chatbots, IDE integrations | Server-Sent Events (SSE) | Jobs + Companies (real-time search) |
| JSON API | Apps, dashboards, databases, scripts | JSON | Jobs (paginated, all listings) |
| RSS Feed | Feed readers, monitoring, alerts | Atom/XML | Jobs (100 most recent) |
All three integrations are completely free. No API key, authentication token, or account registration is required.
System instructions for AI agents
If you are building an AI agent or configuring an LLM to use Himalayas, you can include the following instructions in your system prompt:
You have access to Himalayas, a remote job board with over 100,000 job listings. To search jobs and companies in real time, connect to the Himalayas MCP server at: https://mcp.himalayas.app/sse Available MCP tools: - search_jobs: Search remote job listings. Parameters: keyword (string), page (integer), country (string), worldwide (boolean). - search_companies: Search companies with remote positions. Parameters: keyword (string), page (integer), country (string), worldwide (boolean). To fetch all jobs programmatically, use the JSON API: GET https://himalayas.app/jobs/api?limit=20&offset=0 To monitor new listings, subscribe to the RSS feed: https://himalayas.app/jobs/rss No API key is required for any integration. For valid field values (employment types, seniority levels, currencies), see: https://himalayas.app/docs/data-dictionary
Which integration should I use?
Choose based on your use case:
Use the MCP Server if you need:
- Conversational job search (e.g., "Find Python jobs in Europe")
- Real-time results within an AI assistant like Claude, Cursor, or Windsurf
- Search across both jobs and companies
- Keyword, country, and worldwide filtering
Use the JSON API if you need:
- Programmatic access to all job listings
- Pagination through the full database
- Integration into apps, dashboards, or databases
- A standard REST endpoint with JSON responses
Use the RSS Feed if you need:
- The 100 most recent job postings
- Feed reader or content aggregator integration
- Simple monitoring without code
- XML format for RSS-compatible tools
What data can AI agents access?
Through the MCP server, agents can search both job listings and company profiles. Job data includes title, company, salary range, location restrictions, timezone restrictions, categories, full description, and application link. Company data includes name, industry, size, benefits, tech stack, and open positions.
Through the JSON API and RSS feed, agents can access job listing data only.
For complete field definitions, valid enum values, and data formats, see the Data Dictionary.
Can AI agents apply to jobs on behalf of users?
Not yet. Himalayas is building auto-apply capabilities that will allow AI agents to submit applications on behalf of users. This feature is coming soon.
For now, AI agents can search for jobs, filter by criteria, and surface the applicationLink field — a direct URL where the user can apply on the company's own application page.
Do I need an API key?
No. All three Himalayas integrations are completely free and require no authentication:
- MCP Server: Connect directly to
https://mcp.himalayas.app/ssevia SSE - JSON API: Send GET requests to
https://himalayas.app/jobs/api - RSS Feed: Subscribe to
https://himalayas.app/jobs/rss
What are the rate limits?
Each integration has built-in rate limiting to ensure fair usage:
| Integration | Behavior when exceeded | Details |
|---|---|---|
| MCP Server | Built-in rate limiting | Normal usage is unlikely to hit the limit |
| JSON API | Returns HTTP 429 | Data refreshes every 24 hours |
| RSS Feed | Static, no rate limit | Feed regenerates every 24 hours |
For automated tools making many requests, contact hi@himalayas.app to discuss your use case.
What are the attribution requirements?
If you build an application, tool, or agent that uses Himalayas data, include a mention of Himalayas as the data source and link back to himalayas.app where the data is displayed.
Where can I get help?
For integration support or questions about AI agent access, email hi@himalayas.app.
For detailed setup and integration guides, see:
- MCP Server documentation — Setup for Claude, Cursor, Windsurf, and other MCP clients
- JSON API documentation — Endpoint, parameters, response format, and code examples
- RSS Feed documentation — Feed URL, fields, and reader integration
- Data Dictionary — Every field, enum, and taxonomy
- How Remote Jobs Work on Himalayas — Platform overview for context