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.

REST, SDK, CLI, or MCP

One key and one billing account work across REST, SDK, CLI, and MCP. Choose by where your code runs and who calls it.

The short answer

| Situation | Use |
| --- | --- |
| Server-side code with a fixed contract | **REST** |
| TypeScript or Python app that wants types and helpers | **SDK** |
| Shell scripts, cron, one-off exploration | **CLI** |
| Claude, Cursor, ChatGPT, or another MCP client | **MCP** |
| Your own agent framework with its own tool loop | **REST or SDK**, wrapped in your own tool definitions |

MCP is https://mcp.worklittle.com. REST is https://api.worklittle.com. Setup: Worklittle MCP.

What each gives you

| | REST / SDK / CLI | MCP |
| --- | --- | --- |
| Surface | Every route, filter, field, and error code, including REST-only routes such as unauthenticated board apply | Tools an MCP client discovers without integration code |
| Guards | Yours | The tool surface as designed. A chatty client may call metered tools eagerly |
| Errors | HTTP status plus `error.code` | JSON-RPC. Upstream 429 and 5xx often arrive as `-32603` |

import { createWorklittle } from "worklittle";

const wl = createWorklittle({ apiKey: process.env.WORKLITTLE_API_KEY });
const list = await wl.surveys.list();

Libraries: Libraries, OpenAPI.

Mixing transports

Usage from every transport lands together on Usage. To attribute spend per surface, create a separate key per surface.