# zopdev developer documentation

> The zopdev REST API and MCP server: authentication, resources, costs, schedules, recommendations, deployments, rate limits and the error model.

Source: https://zop.dev/developer-docs

---

Reference documentation for everything programmable in zopdev. If you want the
shortest path to a working call, read [/auth.md](https://zop.dev/auth.md) first — it covers
credentials for both the REST API and the MCP server.

- Overview: authentication, getting started, the request headers every call needs.
- Core concepts: resources, resource groups, schedules, overrides.
- Operations: actions, recommendations, notifications, reports, provisioning.
- Deployments: projects, services, builds, deployment spaces, webhooks.
- Administration: organizations, users and teams, roles and policies, audit logs.
- Reference: the API reference, the error model, and rate limiting.

Machine-readable companions: the full REST surface is at
[/openapi.json](https://zop.dev/openapi.json), the MCP server card at
[/.well-known/mcp/server-card.json](https://zop.dev/.well-known/mcp/server-card.json), this
section's own index at [/developer-docs/llms.txt](https://zop.dev/developer-docs/llms.txt), and
the whole corpus as one file at
[/developer-docs/llms-full.txt](https://zop.dev/developer-docs/llms-full.txt).

A shorter, curated starting point for the whole developer surface — REST, MCP
and credentials together — is at [/developers/llms.txt](https://zop.dev/developers/llms.txt).