Choose an integration

CLI + Skill is the default for AI agents with terminal access.
Choose another transport when it fits the host application. REST, MCP, and CLI are
connections to the same catalog, jobs, results, and
billing model.

Integration	Best for	Authentication	Start
CLI + Skill	Terminal-capable coding agents	Browser OAuth or API key	`Set up Scrappycoco: https://scrappycoco.ai/setup.md`
MCP	Clients that expose remote tools natively	OAuth for the MCP resource	`https://api.scrappycoco.ai/mcp`
REST	Application backends, services, and CI	`X-API-Key` or OAuth bearer token	`https://api.scrappycoco.ai/api/v1`

There is currently no official Scrappycoco language SDK. Application
developers should use REST directly or generate a client from the OpenAPI
document. The CLI is a command-line client, not an SDK package.

Use CLI + Skill when

The agent can run terminal commands.
You want a portable installation across coding agents.
You want structured JSON, JSONL, or CSV output written to local files.

Use MCP when

The host can connect to a remote Streamable HTTP MCP server.
You want Scrappycoco capabilities to appear as native tools.
The host supports the OAuth protected-resource flow.

Use REST when

Scrappycoco is part of an application backend or automation pipeline.
You need direct control of durable jobs and idempotency keys.
You want to generate a typed client from the OpenAPI reference.