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.

Interactive job map

Commute search: plot employers with open roles on an interactive job map using geocoded coordinates, then drill into jobs and auto-apply where eligible.

Worklittle geocodes every job. GET /jobs/map returns employers with coordinates and open-job counts so you can build commute search, not string match on city names. Job listings stay on GET /jobs. Auto-apply stays on Apply with AI.

When to use

Use this pattern when the product is where someone would work, not only which title.

A map of nearby hiring (pan, zoom, radius). A relocation explorer that compares cities by who is hiring. * A commute filter in a search UI that already uses Job search assistant.

The consumer version of this is Maps. Swipe to apply is Jobs. Do not scrape those pages. Call the API.

Calls

1. Map companies. GET /jobs/map (see Search companies). Each row is an employer with coordinates, logo, and open job count. Billing is per company row, inside the monthly company/map quota. 2. List jobs. GET /jobs with location / geo filters, or company= for one employer. 3. Detail. GET /jobs/:id only for cards the user opens. 4. Auto-apply. If apply_with_ai_eligible is true, Apply with AI.

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

Scope is jobs:read for map and search. Apply needs jobs:apply.

Pitfalls

| Pitfall | What to do instead |
| --- | --- |
| Treating map rows as job postings | Map rows are companies. Fetch jobs with `GET /jobs` |
| Matching city strings only | Use geocoded map/search filters |
| Starting apply from a map pin without eligibility | Check `apply_with_ai_eligible` on the job |
| Building a map by paging all of `GET /jobs` | Use `GET /jobs/map` |

Related docs

Search companies, Search jobs, Job search assistant, Apply with AI, Jobs pricing.