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.

Overview

Pick the Worklittle integration pattern that matches what you are shipping: job discovery, apply automation, an embedded careers board, ATS sync, sourcing, or an agent that combines several of them.

Every pattern on this page runs on the same base URL and the same sk-wl-api01 key. The differences are which scopes you enable, which endpoints you call, and how much of the flow a model drives.

Worklittle is job discovery, auto-apply, swipe-to-apply style card UIs, and commute search on an interactive job map, over one API. Jobs is the market-wide index plus candidate-facing apply and document tools. Business is your own hiring workspace: postings, ATS pipeline, employees, HR docs, and webhooks. Most integrations sit squarely in one of them, and the interesting ones bridge both.

Who these pages are for

| Audience | What you are usually building | Start with |
| --- | --- | --- |
| **Product engineers** | A job board, careers site, search UI, or candidate dashboard on top of Worklittle data | [Job search assistant](/use-cases/job-search-assistant), [Embedded job board](/use-cases/embedded-job-board) |
| **AI agent builders** | A copilot that searches, tailors documents, and applies on a user's behalf | [Agent Quickstart](/use-cases/agent-quickstart), [Agent patterns](/use-cases/agent-patterns) |
| **ATS integrators** | Two-way sync between Worklittle and an HRIS, CRM, or internal tool | [ATS automation](/use-cases/ats-automation), [Webhooks reliability](/use-cases/webhooks-reliability) |
| **Recruiting and GTM teams** | Pipeline automation, market sizing | [ATS automation](/use-cases/ats-automation), [Alerts and market data](/use-cases/alerts-and-market) |

If you are not sure which product tree you belong to, ask one question: does the data you need belong to every employer or only your employer? Market-wide is Jobs. Employer-scoped is Business.

Pick a pattern

| You want to | Pattern | Core calls |
| --- | --- | --- |
| Answer "what jobs match me?" | [Job search assistant](/use-cases/job-search-assistant) | `GET /jobs`, `GET /jobs/:id`, `search_jobs` |
| Commute search / interactive job map | [Interactive job map](/use-cases/interactive-job-map) | `GET /jobs/map`, `GET /companies` |
| Auto-apply (fill and send employer forms) | [Apply with AI](/use-cases/apply-with-ai) | `POST /jobs/apply`, `apply_for_job` |
| Generate a tailored resume or cover letter | [Resumes and cover letters](/use-cases/resume-cover-letter) | `POST /jobs/resumes`, `POST /jobs/cover-letters` |
| Put a careers page on your own domain | [Embedded job board](/use-cases/embedded-job-board) | `GET /business/jobs/company/:company/board` (no key) |
| Move candidates, add notes, schedule interviews | [ATS automation](/use-cases/ats-automation) | `/candidates`, `update_candidates`, webhooks |
| Run surveys, HR docs, and attendance from code | [Org operations](/use-cases/org-ops) | `/business/surveys`, `/business/documents`, `/attendance` |
| Chart the market | [Alerts and market data](/use-cases/alerts-and-market) | `GET /jobs/stats` |

How the sections here are organized

The remaining pages are grouped by the kind of problem they solve, not by endpoint.

1. Use cases (this section) describe end-to-end product shapes with the calls in order. 2. Agent Quickstart is the install-and-route page for coding agents (Jobs and Business on one page). Agent patterns cover architecture once a model is in the loop: REST versus MCP, tool sequencing, extraction, pagination, and conversation state. 3. Prompting gives system-prompt language you can paste and adapt, plus grounding rules that keep a model from inventing salaries. 4. Reliability is what you read before launch: backoff, closed jobs, webhook idempotency, and an eval checklist. 5. Reference holds the glossary and the capability map, which is the fastest way to go from a product goal to the exact endpoint.

One key, two products

You do not need separate credentials per pattern. A single sk-wl-api01-... key created on API keys works for REST at https://api.worklittle.com and MCP at https://mcp.worklittle.com. What changes between patterns is the scope set:

| Pattern | Scopes |
| --- | --- |
| Search and detail | `jobs:read` |
| Apply and Apply with AI | `jobs:apply` |
| Resumes and cover letters | `agent:tools` |
| Posting and ATS | `jobs:post`, `jobs:applications` |
| Event sync | `webhooks:manage` |

Grant the narrowest set that makes your integration work. A missing scope returns 403, not a silent empty result, so failures are loud during development. Balance and per-route spend show up on Usage in the Worklittle Business.

Related docs

| Doc | Why |
| --- | --- |
| [Search jobs](/jobs/api/search-jobs) | Filters, cursor pagination, detail fetch |
| [Apply for jobs](/jobs/api/apply-for-jobs) | Apply with AI and track applied jobs |
| [Worklittle MCP](/jobs/mcp) | Tool names, install, and auth |
| [Jobs pricing](/jobs/get-started/pricing) | What each call costs |

Business side: Business overview, Manage candidates, Webhooks.