---
name: worklittle
description: >
  Worklittle gives agents job search, apply, ATS, MCP tools, and SDKs
  from one API. Install agent skills, get a Bearer key, then pick MCP,
  REST, SDK, or CLI. Route to the right path after install.
---

# Worklittle

Worklittle is the Jobs API (`https://api.worklittle.com`) plus MCP
(`https://mcp.worklittle.com`). Use it to search millions of roles,
apply, generate resumes, post jobs, and run an ATS.

Human-readable Agent Quickstart:
https://docs.worklittle.com/use-cases/agent-quickstart

Classic curl Quickstart (humans writing HTTP by hand):
https://docs.worklittle.com/jobs/get-started/quickstart
https://docs.worklittle.com/business/get-started/quickstart

## Install

One command installs Worklittle agent skills (best practices, docs
lookup, capability map, MCP install, job search, apply, ATS):

```bash
npx skills add https://docs.worklittle.com
```

GitHub mirror:

```bash
npx skills add worklittle/agent-skills
```

Index: https://docs.worklittle.com/.well-known/skills/index.json

Manually installed skills do not auto-update. Run `npx skills update -y`
to pull the latest.

## Get credentials

Create a key at https://worklittle.com/business (API keys). Keys look
like `sk-wl-api01-...`. Store as `WORKLITTLE_API_KEY`.

```http
Authorization: Bearer sk-wl-api01-...
```

Common Jobs scopes: `jobs:read`, `jobs:apply`, `agent:tools`.
Employer / ATS scopes: `jobs:post`, `jobs:applications`, `webhooks:manage`.

Public job-board GETs do not need a key. They are rate limited per IP.

If paid routes return **402**, the human must fix billing. Do not retry
until that is resolved.

## Decide Jobs vs Business first

Infer from the user's request. Do not ask them to pick a docs pill.

- Market-wide search, apply, resumes, public boards → **Jobs**
- Post jobs, ATS, employees, org, hiring webhooks → **Business**
- Unclear or both → Jobs for market data, Business for their own hiring workspace

Human page with both trees:
https://docs.worklittle.com/use-cases/agent-quickstart

## Choose your path

- **Need live tools in Cursor / Claude / VS Code** → Path A (MCP)
- **Need to call the API from product code** → Path B (SDK / REST)
- **Need a one-off search in this session** → Path C (REST curl)
- **Need apply / resumes** → Path D (Jobs)
- **Need to post jobs or run ATS** → Path E (Business)
- **Need to look up docs instead of guessing** → Path F

---

## Path A: MCP

Endpoint: `https://mcp.worklittle.com` (POST `/`). Same Bearer key.

Setup: https://docs.worklittle.com/jobs/mcp
Skill: `mcp-install`

Start with `search_jobs` and `get_job_details`. Do not invent tool names.
Use the MCP page or OpenAPI if unsure.

## Path B: SDK / CLI / REST in app code

Libraries: https://docs.worklittle.com/jobs/libraries/overview

```bash
export WORKLITTLE_API_KEY="sk-wl-api01-..."
```

Base URL: `https://api.worklittle.com`

Skill: `worklittle-best-practices` for scopes, billing, REST vs MCP.

## Path C: REST search in this session

```bash
curl -s "https://api.worklittle.com/jobs?q=software+engineer&limit=5" \
  -H "Authorization: Bearer $WORKLITTLE_API_KEY"
```

Filters and pagination: https://docs.worklittle.com/jobs/api/search-jobs
Skill: `job-search`

## Path D: Apply and documents

https://docs.worklittle.com/jobs/api/apply-for-jobs
Skills: `apply-with-ai`, `resume-cover-letter`

Eligibility is `apply_with_ai_eligible` on `GET /jobs` / `GET /jobs/:id`.
Do not sniff Greenhouse / Ashby / Lever from the client.

## Path E: Business ATS

https://docs.worklittle.com/business/get-started/overview
Skills: `post-a-job`, `candidates`, `employees`

## Path F: Docs discovery

Prefer docs over guessing endpoints, scopes, or MCP tools.

1. Index — https://docs.worklittle.com/llms.txt
2. Manifest — https://docs.worklittle.com/docs-agent-manifest.json
3. Page as Markdown — `Accept: text/markdown` or append `.md`
4. OpenAPI — https://docs.worklittle.com/openapi/openapi.yaml
5. Skills index — https://docs.worklittle.com/.well-known/skills/index.json

Skill: `worklittle-docs`

Goal → endpoint / tool / scope: https://docs.worklittle.com/use-cases/capability-map