Order a UGC campaign via API or AI agent

Published June 30, 2026 · by UGC Pocket · ~7 min read

Why order via an AI agent

Marketing teams increasingly use AI assistants to orchestrate their tasks. Rather than filling out a form by hand, an agent can turn an intent ("I want 3 TikTok videos from creators with a dog to launch our kibble") into a campaign that's ready to confirm.

There are three benefits:

• Save time. The agent prepares the brief, chooses the categories and budget, and submits the draft in a single request.
• Integrate with your tools. The API and the MCP plug into your workflows (CRM, content calendar, internal assistant) without repetitive manual work.
• Stay in control. The agent only proposes: nothing is paid until a human has confirmed and funded the campaign.

How it works: the "human-confirmed draft" model

In one sentence: an agent creates a draft, the brand confirms and funds it. That's the human_confirmed_draft principle, designed to combine automation and safety.

1. The agent authenticates with a ugcp_live_… API key tied to your brand account.
2. The agent creates a campaign by sending a brief and the parameters (categories, budget, number of creators).
3. UGC Pocket returns a draft. The campaign is not active: it's waiting for a human action.
4. The brand confirms and funds from the app. Only then does the campaign go live for creators.
5. The rest follows the usual flow: creator selection, receiving the videos, approval, payment on approval.

This model guarantees that no agent can commit any spend on its own. AI speeds up the preparation; the human validates the financial commitment.

The draft created by the agent, awaiting human confirmation.

The surfaces: REST, MCP, llms.txt

UGC Pocket exposes three entry points for agents:

• REST API: host https://ugcpocket.com/api. Standard JSON endpoints to create and track a campaign. The full schema is described in openapi.json.
• MCP server: host https://ugcpocket.com/mcp. The Model Context Protocol lets a compatible agent discover and call UGC Pocket tools natively, without hand-coding the REST integration.
• llms.txt: a text file that summarizes the service and points agents to the right documentation.

A minimal example of creating a campaign in REST:

curl -X POST https://ugcpocket.com/api/campaigns \
  -H "Authorization: Bearer ugcp_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: camp-kibble-2026-06-30" \
  -d '{
    "title": "Kibble launch",
    "brief": "Energetic TikTok video, authentic tone, show the kibble in use with a dog.",
    "target_categories": ["dog"],
    "platforms": ["tiktok"],
    "prestation": "ugc_only",
    "budget_per_creator_cents": 12000,
    "creators_wanted": 3
  }'

The response returns a draft (unconfirmed status) with its identifier, which the brand finds in the app for confirmation.

Allowed values

The API validates every field. Here are the accepted values:

The budget is expressed in cents in the API (12000 = €120). The 7 niche categories correspond to: dog, cat, car, cooking, couple, business, podcast. The 3 services: UGC only, Video + posting, Posting provided.

Security & limits

Security rests on three safeguards: human confirmation, rate limits, idempotency.

• Mandatory human confirmation. No payment is triggered by the agent; the campaign stays a draft until the brand confirms and funds it.
• Rate limit: 30 requests/minute. Beyond that, the API responds with a rate-limit error (HTTP 429). Space out your calls or set up a queue on the agent side.
• Idempotency. By passing a unique Idempotency-Key header, you avoid creating two identical drafts if a request is replayed (network timeout, agent retry).
• Scope-limited key. The ugcp_live_… key is tied to a brand account; revoke it from the app if in doubt.

In short: an agent can prepare and submit, but can neither spend nor publish without your explicit go-ahead.

FAQ