For AI agents · the namesake
Your agents arethe marketing team.
marketer.sh exists so software can run marketing. Every pipeline is a tool an agent can call, every cost is declared up front, and every dollar stops at a cap you set.
The grind today
Agents can plan. They can't produce.
Your agent can write the campaign doc. Then what?
No hands
An agent can draft a strategy, but rendering video, cutting captions, and publishing on schedule takes a stack it doesn't have.
Five APIs and a prayer
Gluing a script model to a video model to a voice model to a scheduler is a platform team's quarter, per pipeline.
Nobody trusts it with a card
Generative spend compounds fast. Without hard limits, an agent with a budget is an incident report waiting to file itself.
With marketer.sh
Connect, call, stay under the cap.
01
Connect over MCP or the API
Point your agent at the MCP server, or use the API, SDK, or CLI with a scoped PAT. The whole platform is callable.
02
Tools declare their cost
Every tool description says what it does and what it costs, so agents budget before they act instead of apologizing after.
03
Guardrails do the worrying
Per-niche and global caps refuse overspend at the API. The approval gate holds publishing for a human until you lift it.
The product moment
One sentence in. A campaign out.
An ops agent gets a one-line instruction, calls the tools, checks its budget, and parks the whole push at your approval gate.
- MCP tools with cost-aware descriptions
- Scoped PAT auth for every surface
- Caps refuse overspend server-side, gates hold publishing
your ops agent
mcp · pat: launch-* scope
Launch a content push for the new feature.
marketer.queue_video × 3est $2.90 · cap okmarketer.queue_article × 2est $1.30 · cap okCreated niche, queued 3 videos + 2 articles. Est. $4.20, cap $10. Awaiting your approval gate.
Outcomes
Autonomy, with receipts.
0
surfaces to drive it: API, SDK, CLI, MCP
0/7
the cadence agents can hold
$0
spendable past the caps, by design
Questions
Agents, answered.
How do agents authenticate?
With scoped personal access tokens. Mint a PAT, limit it to the niches an agent may touch, and use it across the API, TypeScript SDK, CLI, and MCP server.
Can an agent overspend?
No. Per-niche daily caps and a global cap are enforced server-side, and everything runs on prepaid credits. A call that would pass a cap is refused before it costs anything, and every tool description states its cost up front so agents can plan.
Does anything post without review?
Only if you turn the approval gate off. With the gate on, agents can brief, produce, and queue freely, and publishing waits for a human. Many teams start gated and hand agents the keys once the output has earned it.
Get started
Give your agent a marketing department.
Mint a PAT, set a cap, hand your agent the MCP server. Keep the gate on until it earns your trust.