Indeed
Job search, job detail, and company lookup from Indeed, served as plain REST. Responses are reshaped from Indeed's GraphQL API into a clean structure, not raw passthrough.
Endpoints
| Endpoint | Path params | Query params | What it returns | Price | Data up to |
|---|---|---|---|---|---|
GET /indeed/search |
— | what, where_query, radius_miles, limit, cursor, sort, job_type, is_remote, co, locale |
Job search results. | $0.003 | 5 min |
GET /indeed/job |
— | key, co, locale |
Full detail for one job listing. | $0.003 | 1 hr |
GET /indeed/companies |
— | what, co, locale |
Company name search. | $0.003 | 1 hr |
Prices are per call, paid in USDC with x402. "Data up to" is the cache window: a repeated call inside it returns the same data.
Calling it
# x402: no account or API key. The server answers 402 with payment instructions; an x402 client pays and repeats the request.
curl -i "https://<base-url>/indeed/search?what=software+engineer&co=US"
Responses are JSON. Field names follow the upstream source, so a response can be larger than the table above suggests.
Notes
job_type(full-time, part-time, contract, internship, temporary, per-diem, volunteer) andsort(relevance, date) are closed enums.limitdefaults to 25, maximum 100.co(country) defaults toUS,localedefaults toen-US.
