Coding agent documentation index Fetch the complete documentation index at: https://docs.worklittle.com/docs-agent-manifest.json Use this file to discover all available pages before exploring further.

Alerts and market data

Answer aggregate market questions with free stats instead of paging through search results.

If the question is a count, a trend, or a top-companies list, do not answer it with search pagination. GET /jobs/stats exists for exactly that and it is free.

Job seeker alert emails

Job alert email for people using worklittle.com is not a public API. Signed-in members turn on Instant job alerts in Settings. Matches come from the Job title field on their profile. See Instant job alerts.

Do not build a saved-search email product on /job-alerts or MCP alert tools. Employer hiring email and webhooks are separate: Webhooks.

Market overview

GET /jobs/stats (MCP get_market_overview) returns aggregate statistics about the indexed market: how many roles are open, how many are remote, which companies are hiring most. It takes no required parameters and it is free.

curl -s "https://api.worklittle.com/stats" \
  -H "Authorization: Bearer $WORKLITTLE_API_KEY"

Use it when a user asks a shape-of-the-market question rather than a which-job question. "How many remote product roles are there" is a stats question. "Show me remote product roles" is a search question. Answering the first with the second is the single most expensive mistake an agent can make on this API, because it turns a free call into dozens of billed pages.

Salary averages

GET /jobs/salary-average answers compensation questions across a query rather than for one posting. It costs $0.05 per request and accepts the same filters and negative title tokens as search.

curl -s "https://api.worklittle.com/jobs/salary-average?title=Product+Manager,+-Senior,+-Principal,+-Lead,+-Staff,+-Director&workplace_type=remote&country=US" \
  -H "Authorization: Bearer $WORKLITTLE_API_KEY"

The response reports matching_jobs, jobs_with_salary, jobs_in_average, average_salary, salary_min, and salary_max. Only annualized pay between $30k and $1M is included, and hourly or monthly postings are annualized first, so mis-parsed outliers do not distort the number.

Always surface jobs_in_average alongside the average. An average built from four postings is a very different claim than one built from four hundred, and a user cannot tell the difference unless you show them.

Company and map views

Commute search and the interactive job map use GET /companies and GET /jobs/map for employer-level discovery. Every Worklittle job carries geocoded location data, so map queries support genuine radius and local discovery rather than string matching on city names. Billing on /jobs/map is per company row. Full pattern: Interactive job map. Reference: Search companies.

Pitfalls

| Pitfall | What to do instead |
| --- | --- |
| Counting search results to answer "how many" | Call `GET /jobs/stats`, which is free |
| Quoting an average salary without the sample size | Report `jobs_in_average` too |
| Building alert email on the public API | Use consumer [Settings](https://worklittle.com/settings) for job seeker alerts |
| Confusing job seeker alerts with webhooks | Alerts are Settings email. Webhooks are org hiring events |