# Developer overview

DoorOps publishes four developer surfaces. They share the same tenant boundary and role model.

| Surface | Auth | Use it for |
| --- | --- | --- |
| [REST API](/docs/developers/api) | Organisation API key (`dop_…`) | Scripts, iPaaS, custom apps |
| [Tenant MCP](/docs/developers/mcp) | OAuth 2.1, scope `mcp:use` | Claude, ChatGPT, Grok against live org data |
| [CLI](/docs/developers/cli) | Same API key | Terminal and CI |
| [Skills](/docs/developers/skills) | None (public Markdown) | Teach an agent the safe workflow before it calls tools |

Interactive OpenAPI lives at [doorops.com/docs/api](https://doorops.com/docs/api) (signed in). The snapshot in this site is the public reference.

Third-party apps register at [doorops.com/developer/apps](https://doorops.com/developer/apps) and use REST scopes. They cannot request `mcp:use`.

If you are wiring a system DoorOps does not have a native connector for, start at [build your own integration](/docs/integrations/custom).