For AI agents: an index of this guide is available at https://www.plungeai.com/guide/llms.txt. Append .md to any page URL, or send Accept: text/markdown, to get markdown. The developer documentation is at https://www.plungeai.com/docs/llms.txt.

Documentation Index: fetch the complete documentation index at /llms.txt. Use this file to discover all available pages before exploring further.
Feedback

PlungeAI Agency is three web apps on Cloudflare. They keep the agency's data in their own databases and use the Ocean platform for everything that thinks or generates: workflow runs, models, run outputs, brand cards and the clock. This is the only place in this guide that names the internal services.

Diagram 1. Three apps, the agency's own data, and the platform services they call. The dashed line is the scheduler calling the Dashboard's jobs. The public site forwards the start form to the Dashboard. Agency Studio and the Dashboard both read and write the agency's three D1 databases, the KV cache and the R2 bucket, and call the Ocean platform: auth-core, Ocean Studio runs, the One API, SharedMemory, the registry and the scheduler, which calls the Dashboard's jobs.

SurfaceWho uses itHow you get in
Public siteAnyoneNo login. Packages, the start form and the policy pages.
Agency StudioClient users (approvers and viewers); agency members can open their clients' workspacesA PlungeAI account, after an invite. Magic links open one decision without a login.
DashboardThe agency teamA PlungeAI account under an email an owner or admin added.

Every run is started as the agency's platform account, or, where the client's own connections are needed, on behalf of that client, so a client's credentials stay under that client. Notices by mail and Slack go through one outbox, and only the Dashboard's flush job sends from it.