Skip to main content
A campaign is the primary product object. It carries a goal, generates creator matches against that goal, and holds the shortlist you augment and operate. Campaigns work the same from the web, MCP, REST, and CLI. All campaign endpoints require a credential: an agent access token, a Settings API key, or a browser session. See Authentication.

The loop

1

Create with a goal

2

Generate matches

Generation runs searches against the campaign goal and lands ranked creators on the campaign.
3

Augment

Add or remove individual matches with POST /api/campaigns/{id}/matches and DELETE /api/campaigns/{id}/matches/{matchId}.
4

Operate

Read the campaign with matches (GET /api/campaigns/{id}), update it (PATCH /api/campaigns/{id}), or export the shortlist as CSV (GET /api/campaigns/{id}/export).
Every endpoint is in the API reference with an interactive playground.

Visibility and cost

  • New campaigns are public by default. Public campaign bodies are free to read for any identified caller.
  • The owner always reads their own campaigns free.
  • Private campaigns are invisible to non-owners (404). Anonymous callers get 401.
  • Making a campaign private costs 1 credit: at creation, or when flipping public to private. Updates to an already-private campaign do not charge again.

CLI equivalents