API for AI assistants

Connect your AI assistant to your campaign work.

Let an approved assistant read brand details, create campaign briefs, request ads, check approvals, and retrieve reports. People still control publishing and spend.

Connect an AI assistant Open the API schema

MCPnative connection/api/mcp

RESTagent endpoints/api/agent

Humanapproval gatesbefore risky actions

Serversecret boundarytokens stay off-client

What the offer includes

Everything you need to go from product page to finished ad.

Context

Brand details

Create brand profiles, look up approved facts, and attach assets your team can use.

Plan

Campaign details

Create briefs and campaigns, update the plan, and retrieve the latest information later.

Create

Create ads

Request creative work, check its progress, and attach the results your team has reviewed.

Control

Approvals

Keep each decision and its history attached to the exact work being approved.

Deliver

Files and reports

Retrieve finished creative, launch details, proof, and campaign reports.

Connect

Works with your assistant

Use MCP, OpenAPI, or the connection kit with the AI assistant your team already uses.

How it works

Four simple steps from your page to ready-to-use creative.

Create an organization token

Use a scoped, server-side credential with only the actions the integration needs.

Choose MCP or REST

Connect an assistant directly or call the authenticated agent endpoints from your own service.

Ground before generation

Load brand context, campaign state, source assets, and constraints before requesting creative work.

Follow the review state

Poll jobs, retrieve packets, and keep human approval intact before external execution.

Common uses

Give an assistant useful campaign work it can actually finish.

The API is designed for complete tasks: read the right context, create or check the work, and return something a person can review.

01AI assistant

Question → plan → review

Plan a campaign using approved brand information

Let the assistant retrieve the right details, create the plan, and return it for review.

Example workflow

02Agency platform

Brands · jobs · approvals

Run multiple brands without mixing their work

Keep each brand separate while jobs run at the same time and the right people approve the final work.

Example workflow

03In-house system

Request → status → result

Connect ad creation to your current tools

Start a creative request, check progress, handle a retry, and retrieve the finished output.

Example workflow

04Safe automation

Access · approval · history

Move faster without removing human control

Let the assistant prepare important actions while people keep the final decision and a clear record.

Example workflow

These are example workflows, not customer case studies. Available actions still depend on account access, configuration, and human approval.

Connection surface

One campaign workspace. Three ways to connect.

GET /api/agent/openapiPOST /api/mcpGET /api/agent/connection-kitGET /api/agent/creative-generation-capabilitiesPOST /api/agent/campaigns

Read the public schema

curl https://client.cloutos.com/api/agent/openapi

# Authenticated operational requests
Authorization: Bearer $CLOUTOPS_AGENT_TOKEN
X-CloutOps-Organization: your-organization-id

Common questions

Clear scope before the work starts.

Is the API public and unauthenticated?

No. Operational endpoints require scoped organization credentials. Public schema and connection surfaces help a developer understand the contract without exposing account data.

Can an agent publish or spend automatically?

Not by default. High-impact mutations stay gated by configuration, permissions, approval snapshots, and spend authorization.

What can I build with it?

Common paths include assistant-driven campaign planning, brand-context retrieval, creative job orchestration, approval workflows, and packet or report retrieval.