Job data for
your next tool call.

Search structured job summaries. Fetch the full details only when your agent needs them. Through REST or MCP.

A small search. A useful result.Fixture API · Synthetic data · No billing

Searching synthetic jobs…Fixture API

Loading job summaries from the fixture API.

POST/v1/jobs/search

{
  "query": "engineer",
  "location": {
    "id": "san-francisco-ca-us",
    "mode": "administrative"
  },
  "filters": {
    "workModes": []
  },
  "pageSize": 25
}

Search returns summaries. Full job details are a separate request.Open the playground

Structured job data for the agent you are building.

REST API MCP tools

A search result is
just the beginning.

Your agent needs enough information to choose a role before it needs the whole listing. Jobuse keeps those two steps explicit.

Follow a request

Search a focused set of summaries.

Use a query, location, coordinates, and work mode to narrow the roles your agent considers.

Let your agent choose what to read.

Compare structured fields such as title, base salary, skills, and posted date before requesting a full description.

Retrieve the details by ID.

Fetch an individual job through REST or the matching MCP tool. Both interfaces expose the same capability.

Fields your code
can work with.

Keep location, work mode, salary, and skills in their own fields. Pass structured results into your next step.

Explore the example schema

Summary fields
Field	What it carries
id	A job identifier for detail retrieval
location	Place and geographic coordinates
workMode	On-site, hybrid, or fully remote
baseSalary	Range, currency, and period
skills / postedAt	Skills and the original posted date

Make your first tool call.

Explore the complete flow with synthetic data. No account required for this demo.

Try the playground Explore MCP

Job data foryour next tool call.

A search result isjust the beginning.