✦PLATFORM VISION

How campaign software could become agent-accessible.

This page describes the integration direction we are researching. There is no public Anchors AI API today.

Discuss the platform direction View the concept

CONCEPTUAL REQUEST MODEL

A possible interface for structured campaign instructions.

The example demonstrates a planned data model only. It is not an operational endpoint and should not be used as API documentation.

✓Structured inputsBrand, goal, audience, budget and platform.
✓Predictable outputsCreator criteria, allocations and workflow states.
✓Observable executionConsistent statuses for every campaign action.

campaign-request.json

POST /v1/campaigns

{
  "objective": "product_launch",
  "audience": "SaaS founders in India",
  "budget_inr": 300000,
  "platforms": ["linkedin"],
  "execution": "prepare"
}

LONG-TERM DIRECTION

Designed to support controlled integrations over time.

After campaign workflows and permissions are validated, we plan to test controlled connections with selected AI and workflow products.

AI assistantsInternal agentsMarketing copilotsWorkflow tools

◫

Clear schemas

Consistent campaign objects that software can reliably read and update.

⌁

Permission-aware

Execution should occur only within the access, budget and platform constraints a company defines.

◎

Observable

Every meaningful campaign state is designed to be traceable rather than hidden in conversations.

EVENT-DRIVEN EXECUTION

A proposed event model for campaign progress.

These event names illustrate the system direction. Webhooks and public developer access are not currently available.

01campaign.createdWebhook

02creator.selectedWebhook

03collaboration.acceptedWebhook

04content.approvedWebhook

05post.publishedWebhook

06performance.updatedComplete

Conceptual interface · Public API access is not currently available

PRIVATE BETA

Interested in the platform direction?

Request early access