Key facts
| Agent stack | Chat completions, function calling and embeddings are live |
| Use cases | Brief assembly, creative QA, research digests, performance summaries |
| Brand rules | Expose style, legal and claims checks as tools the agent must call |
| Tools | Any internal API can be exposed via function calling or MCP |
| Models | 30+ models; small aliases for checks, stronger ones for synthesis |
| Approval | Keep a human gate before anything publishes or spends budget |
| Pricing model | Flat monthly self-serve plans with unlimited fair-use usage |
| Roadmap | Image, audio and batch endpoints are coming soon |
TL;DR
- Automate the brief, the checks and the digest, not the publish button.
- Encode brand and legal rules as tools the agent cannot skip.
- Ground research and performance claims in retrieved sources.
- Keep humans accountable for spend and final creative approval.
- Measure cycle time and rework, not the number of drafts generated.
How it works, step by step
- Choose one workflow such as creative QA or the weekly research digest.
- Write the brand, legal and claims rules as discrete check functions the agent must call.
- Ground research in a retrieval index over approved sources and your own past campaigns.
- Generate drafts with citations and attach the check results to each one.
- Route to a human approver for sign-off before publishing or committing budget.
- Log tool calls and approvals, then measure review time and rework rate.
Try it yourself
Open the agent workflow designer →
Advertising workflows an agent can own
Agents do best where steps repeat and evidence is checkable:
- Brief assembly: combine the client request, audience notes, past performance and constraints into a structured brief.
- Creative QA: check copy against tone, legal and claims rules and flag every violation with the rule cited.
- Research digests: summarise market and competitor material from an approved source set.
- Performance summaries: turn campaign numbers into a plain-language recap with caveats.
Anything public or budgeted still needs a named human owner.
Architecture and brand-safe tooling
Model the workflow as a short, bounded loop:
- Planner: turns a request into steps and required checks.
- Retriever: pulls approved sources, style guides and past campaign results.
- Tools: brand check, legal check, claims check and asset lookup, called explicitly.
- Composer: drafts with citations to the retrieved material.
- Approver: a human reviews the draft and the attached check results.
Make the checks mandatory tool calls rather than instructions; instructions can be ignored, a required tool call can be enforced in code.
Guardrails, spend and disclosure
Never let an agent commit media spend or publish without approval. Cap any budget action behind a human confirmation step and a hard limit. Keep an audit log that records the prompt, sources, check results, model version and approver for every asset, so you can reconstruct why something was released. Separate environments and keys for each client or brand where confidentiality demands it. Where a client or market requires local processing, run the same compatible workload inside a VPC, on-prem or air-gapped deployment.
Evaluating an advertising agent
Prototype on plugsky-micro or plugsky-lite against a small set of past briefs and creatives, then use the 14-day full-access trial to test a frontier model on synthesis-heavy work. Track brief cycle time, number of human edits, rule violations caught and false positives, and the share of claims with a valid source. Self-serve plans are flat monthly with fair-use usage, so high-volume testing does not create per-token spikes. Keep prompts and rule sets versioned, since brand guidance changes often.
Honest comparison
| Capability | Plugsky | Typical agent framework | Building in-house |
|---|---|---|---|
| Tool calling | Live function calling over internal APIs and MCP tools | Framework-specific adapters | You build and maintain |
| Retrieval | plugsky-embed plus RAG over brand and research sources | Add-on or external store | You integrate everything |
| Approval gate | You enforce publish and spend gates in code | Varies | You design controls |
| Deployment | Cloud, VPC, on-prem and air-gapped | Usually cloud-only | You operate GPUs and serving |
| Pricing | Flat monthly self-serve, fair-use usage | Varies by framework and model | GPU plus operations cost |
Frequently asked questions
Can the agent publish ads directly?
No. Keep a human approval gate for anything public or budgeted; the agent should prepare the asset, evidence and check results for sign-off.
Which endpoints does an advertising agent need?
Chat completions, function calling, JSON mode and embeddings are live. Image, audio and batch endpoints are coming soon.
How do we enforce brand rules?
Encode them as tools that must be called before a draft is accepted, and fail the run when a check is missing or returns a violation.
Is there a free plan?
Yes. The free plan includes plugsky-micro and plugsky-lite with no credit card, which is enough to prototype brief assembly and creative QA.
How does pricing work?
Self-serve plans are flat monthly with unlimited fair-use usage. See the live pricing page for current plans and enterprise options.
Can we isolate client data?
Yes. Use scoped keys and separate projects or deployments per client, including VPC or on-prem where confidentiality demands it.
How should we measure it?
Track cycle time, number of human edits, violations caught, false positives and audit completeness rather than drafts generated.