The source answered.
Records delivered, or a completed search that found no matches. The checked scope stays visible.
Web data for developers and AI agents
Web data APIs.
Built for code and AI.
Get structured data from supported websites through REST or MCP.
See what each source delivered, what was left out and why, and what it cost. Starting with job search.
In development. Examples are interactive; APIs are not live.
- request
- “python” · CA · remote only
- indeed
- Delivered 14 records
- glassdoor
- Excluded
remote filter unsupported - Unavailable
zero charge - outcome
- partial · explicitly allowed
- spending cap
- $0.10
Illustrative receipt, sources and price. No live request. Source availability and rates are not published yet.
01 / Understand the outcome
Three outcomes, kept apart.
An empty list can mean “nothing matches” or “we could not find out”. Your application needs to know which.
Some of it, named.
Only when you allow it. Excluded and failed sources stay in the response, so partial coverage never looks complete.
We could not find out.
Unavailable or unable to complete. A failed collection is never presented as a successful search with no matches.
02 / Start from a task
One task.
A useful answer.
Job Search is the first planned release. More tasks will follow, one working API at a time.
Browse the planned catalog →03 / Code or conversation
Your workflow.
The same task contract.
REST for your applications. MCP for AI clients. Both are designed around the same inputs, source outcomes and spending controls.
REST, MCP and client connections are planned, not currently available.
{
"query": "python",
"country": "CA",
"sources": [
"indeed"
],
"limit": 20,
"maxCostUsd": 0.1
}Example request shape. See the preview documentation for the current contract.
04 / Know the cost
A billing unit you can understand.
Job Search is planned to charge per delivered record. Media operations will publish their own units, including duration where appropriate. No separate startup or platform usage fee.
How pricing will work →Can I call an API today?
Not yet. This is our public preview. You can explore the design and sample responses; accounts, keys and billing will open with the first working release.
Which job boards will be supported?
Sources are still being validated. Names in the example are illustrative. Confirmed coverage will appear on the product page before access opens.
Will every API launch at once?
No. We are starting with Job Search and adding useful tasks in batches. Catalog entries clearly show their planned status.
Explore the preview
Read one receipt before writing any code.
Try the example states. See exactly what the response is designed to tell you.
Explore Job Search ↗