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.

Search companies

Find employers by name or slug, map them in the index, and scope job search by company.

Overview

Company discovery starts with GET /companies?q= (name/slug search over employers with open jobs), then GET /jobs/map, and company= on GET /jobs.

When to use

If you are building:

A typeahead or global search for employers GET /companies?q=google&limit=5 returns ranked companies with logos for typeahead A hiring map or geo dashboard GET /jobs/map returns company HQ, coordinates, logo, and open job count per employer A single-employer slice of the market index Filter GET /jobs?company=slug for indexed roles at that employer (comma-separated OR; prefix - to exclude, e.g. -lucid-motors)

The consumer company page at worklittle.com/company/:slug can mix index jobs with that employer's published board. For the published board API, see Public job board.

Basic usage

curl -s "https://api.worklittle.com/companies?q=glossier&limit=5" \
  -H "Authorization: Bearer $WORKLITTLE_API_KEY"

curl -s "https://api.worklittle.com/jobs/map?limit=50" \
  -H "Authorization: Bearer $WORKLITTLE_API_KEY"

curl -s "https://api.worklittle.com/jobs?company=stripe&limit=20" \
  -H "Authorization: Bearer $WORKLITTLE_API_KEY"

> Tip: GET /companies and GET /jobs/map are metered per company row - Pricing.

Search companies reference

> Self-contained reference for company-scoped job discovery.

Overview

| Route | Auth | Purpose |
| --- | --- | --- |
| `GET /companies?q=` | `jobs:read` | Ranked company name/slug search (employers with ≥1 job). MCP: `search_companies` |
| `GET /jobs/map` | `jobs:read` | Companies with coordinates + job counts |
| `GET /jobs?company=` | `jobs:read` | Jobs by employer slug(s): bare = include OR; leading `-` = exclude |

GET /companies params

| Param | Role |
| --- | --- |
| `q` | Required, 2–80 chars. Trailing words like "jobs" / "careers" are stripped. |
| `limit` | Default 5, max 20 |

Ranking: exact slug > exact name > slug/name prefix > name contains (multi-word). Payload is identity + logo/enrichment fields (no job_count / HQ). Responses are edge-cached (~30 days).

MCP / SDK / CLI: pass the same company string on job search (e.g. stripe or -lucid-motors,-tesla). For employer typeahead use MCP search_companies (same as REST GET /companies?q=) - agents should resolve real slugs/ids from the index, not invent them.

Include and exclude employers on job search

company on GET /jobs (and on SDK jobs.search / CLI --company / MCP search_jobs) takes exact slugs:

| Value | Meaning |
| --- | --- |
| `stripe` | Only Stripe |
| `meta,google,apple` | Any of those employers (OR) |
| `-lucid-motors` | All employers except Lucid |
| `meta,google,-amazon` | Meta or Google, never Amazon |

Only a leading - excludes. Mid-slug hyphens are part of the brand (lucid-motors). Title exclusions (-Senior) stay in title / q, not in company. See Search jobs.

Map filters

| Parameter | Role |
| --- | --- |
| Bounding box (`north`, `south`, `east`, `west`) | Geo filter |
| `center_lat`, `center_lng`, `radius_km` | Radius search |
| `limit` | Cap rows returned |

Common mistakes

| Wrong | Correct |
| --- | --- |
| Searching companies with `GET /jobs?title=Google` | Use `GET /companies?q=Google` for employer hits, or `GET /jobs?company=google` for that employer's roles |
| Omitting `q` on `GET /companies` | `q` is required (min 2 characters) |