Developer portal

From a question to sourced job data in one command.

Mike is Hiring maps the public AI and frontier-technology talent market over REST and Model Context Protocol. Public jobs, companies, compensation, funding, market signals, and evidence require no account or API key. Candidate workspaces are a separate, explicit connection.

1 · Call the public API

Start with the zero-auth discovery index, then search current jobs. Responses use a documented JSON envelope and include freshness metadata.

curl "https://mikeishiring.com/api/public/v1/search/jobs?q=research+engineer&domain=ai&per_page=5"

Open the OpenAPI 3.1 document →

2 · Connect an agent

The hosted server uses stateless Streamable HTTP. The compact market surface is read-only and excludes candidate profiles, applications, inboxes, connectors, and operator controls.

https://mikeishiring.com/api/public/v1/mcp?surface=market

Inspect the MCP server card →

3 · Run the official CLI

The npm package provides a local stdio MCP server for clients that launch tools as child processes. Node.js 22 or newer is required.

npx -y mikeishiring-mcp

View mikeishiring-mcp on npm →

Which surface should an agent use?

Use REST for deterministic reads and scripts that already consume HTTP JSON. Use the default hosted MCP when an agent needs to compare hiring demand, companies, roles, compensation, funding, or Frontier AI evidence in conversation. Choose a specialist candidate, company, admin, or compatibility surface only when that work is intentional. Use the browser when a person needs to inspect records and evidence. Respect response metadata and rate limits, and do not send candidate data in public search query strings.

Protocol and endpoint map

REST discovery: GET /api/public/v1/
Job search: GET /api/public/v1/search/jobs
OpenAPI: GET /openapi.json
MCP: POST /api/public/v1/mcp
MCP health: GET /api/public/v1/mcp/health
Agent index: GET /llms.txt
Agent skills: GET /.well-known/agent-skills/index.json

Authentication and boundaries

Public discovery, market reads, and the MCP market surface do not need credentials. Candidate-workspace operations require an explicit candidate connection and bearer token. Never place a token in a URL or publish it in an agent transcript. The API returns 429 with retry guidance when throttled. Public talent intelligence is aggregate; person-level candidate data and authenticated workspace state are outside the public contract.

Response discipline

Check the HTTP status before reading a body. Follow source, observation-window, generation, freshness, coverage, and suppression fields rather than describing every value as current. Treat disclosed, extracted, and predicted compensation differently. A posting is evidence of observed demand, not proof that a hire happened. Unknown website routes return a real 404; agents requesting Markdown receive a short discovery index with the same status.