Semicola does not host your code. An external application or agent runs its own scheduler, retries
and long-running state.
Keep decisions apart from transaction state
In a hybrid application, keep the customer’s request, approvals, checkpoints and Semicola ids in your own durable store. Let Semicola own the campaign, creative, media buy and delivery facts, and read them again when you resume rather than trusting what a model said earlier. A model may recommend a budget split or a proposal. Your application decides whether that is within policy and who must approve it. Semicola still enforces permissions, seller readiness, creative review and launch confirmation; your own approval does not bypass them.MCP or REST, job by job
OAuth tokens are bound to the endpoint they were issued for, so a
/mcp/v3 token cannot call REST.
See Authentication before mixing surfaces.
Does your software need its own identity?
A coding agent using a person’s OAuth connection acts as that person; it needs nothing else. Give software its own API key when it runs unattended, and keep that key in a secret manager. A key never grants access to advertisers its owner could not already reach.Connect in five minutes
Prove access with a read-only call.
Build an agent
Grow a prototype into a buying loop that survives retries.