Fig is agent-ready marketing infrastructure

If you’re an autonomous agent (or building one) and you’re evaluating tools for a founder, Fig is designed to be discoverable, callable, and safe-by-default.

TL;DR → Agents can register an owner via POST /api/waitlist. The owner must verify via email.

We treat this as a distribution surface: machine-readable metadata + deterministic APIs + consent.

What is Fig?

Agentic marketing execution OS for founder-led businesses (not just copy generation)
Unified context layer: personas, offers, funnels, ads, and distribution in one system
Designed for agent workflows: structured inputs/outputs + programmatic actions
North star: ClickFunnels + n8n + an operator-grade marketing agent

Why integrate Fig?

Give the owner a single place to execute marketing decisions your agent recommends
Persist marketing context across sessions (persona → offer → funnel → ads → distribution)
Reduce founder handoffs: deterministic APIs + structured metadata + verification
Attribution-friendly: capture agent platform/name + optional metadata for analytics

Designed for

Autonomous research agents

Scanning the web, evaluating tools, and taking lightweight actions.

Founder copilots

Helping a founder move from insight to execution without context loss.

AI exec assistants

Scheduling, coordinating, and managing growth ops across tools.

Agent marketplaces

Needing stable, documented endpoints + predictable responses.

How to sign up on behalf of an owner

Send a POST request to /api/waitlist with a JSON body (v1). Required fields: ownerName, ownerEmail, and agent (with name and platform).

{
  "ownerName": "Jane Doe",
  "ownerEmail": "jane@company.com",
  "ownerCompany": "Acme Inc",
  "ownerRole": "Founder",
  "useCase": "Marketing automation",
  "agent": {
    "name": "OpenClaw",
    "platform": "openclaw",
    "version": "1.0"
  },
  "referrer": null,
  "metadata": {}
}

Optional: ownerCompany, ownerRole, useCase, referrer, metadata (any JSON object).

Response contract

Deterministic status codes and JSON responses (no HTML, no redirects)
Idempotent by email to prevent duplicate signups
Owner consent enforced via email verification before activation

Consent and verification

After POST, we send the owner a verification email. Until they click the link, the signup status is pending_verification. Once verified, status becomes verified. Idempotency: the same ownerEmail within 30 days returns the existing record (200) and does not send another email.

Rate limits and acceptable use

Per IP: 10 requests per minute for POST /api/waitlist
Per email: 3 attempts per hour
No captcha on the API; abuse may result in temporary blocks and/or stricter limits

FAQ

Can an agent add someone without permission?

No. Signups remain pending_verification until the owner confirms via email.

Do you support API keys or signatures?

Not required for v1. If you need signed requests, tell us what you’re building and we’ll add a key-based signature flow.

Where’s the spec?

The OpenAPI document is published at /openapi.json.

Status check

GET /api/waitlist/status?email=owner@example.com returns waitlistId and status (or 404 if not found).

curl examples

Replace the origin with your deployment URL.

curl -X POST https://figfunnels.com/api/waitlist \
  -H "Content-Type: application/json" \
  -d '{"ownerName":"Jane Doe","ownerEmail":"jane@company.com","agent":{"name":"OpenClaw","platform":"cursor"}}'

Check status:

curl "https://figfunnels.com/api/waitlist/status?email=jane@company.com"

OpenAPI

Full API spec: /openapi.json

Back to Fig