Search, Performance Max, and Display campaigns across accounts and MCCs. Budget control and normalized reporting through the Google Ads API.
Connectors
Every connector implements the standard tool set against its platform’s native API. Capability differences are declared, never silent — an agent asks what each connector supports through list_platforms, and a verification is a claim about a date, stamped with it.
Status in the hub
What your agent can do on each platform today, from the connector’s own declaration. Launch = one draft becomes a complete campaign; read & manage = reads, reports and edits, no launch yet. Written from a platform’s docs means not yet run against a live account. Every date is a claim about that day, never about today.
Launch lanes
Recorded = a campaign was created paused through this path on that date and read back; built = the path exists with no recording yet.
Retail media starts here — and it is more than sponsored products: offsite display and video across Surfside's exchanges, Connected TV, and commerce media on Surfside's own inventory built from catalog product cards.
Recordings were made on Surfside's preview environment, not production. Commerce media has no recording yet, and the brand catalog it builds from is listable only by all-accounts logins today.
Ads in ChatGPT conversations, under OpenAI's published ad policy and your own destination and category rules — checked before anything is sent.
Campaign, ad set and ads with image or video in one draft. Not covered yet: saved audiences in a launch, and cost caps — Meta bids for the lowest cost.
Image recorded 2026-10-23 and video 2026-10-26 on a production ad account; the Meta app was on its development access tier.
Search campaigns in one all-or-nothing create: keywords and negatives, responsive search ads, regions and a schedule. Target cost per conversion is not offered yet.
Two recordings on a production Google Ads account.
Ad platforms
12 connectorsFacebook and Instagram through the Marketing API. Campaign, ad set, and ad management down to creative swaps, custom audiences, and insights reporting.
In-feed and spark ads via the TikTok Business API. Campaign management, custom audiences, and normalized performance reporting.
Promoted posts with community and interest targeting. Audience sync and conversion reporting through the Reddit Ads API.
Campaigns and promoted content via the X Ads API. Audience management and analytics. Live writes require OAuth 1.0a signing and approved Ads API access.
Sponsored Products through the Amazon Ads API: campaigns and ad groups, budget control, and the async reporting pipeline normalized into the standard schema. API access requires Amazon approval.
Criteo Marketing Solutions campaigns and ad sets. Criteo campaigns carry no on/off switch — delivery control lives on ad sets, and the connector says so rather than faking a status.
Campaigns and flights (as ad sets) inside any Kevel-powered retail media or ad network, via the Management API. One connection per network.
Sponsored listings reporting for marketplace advertisers, connected with a partner-minted token. Write support (campaign creation and budgets) is on the roadmap.
Surfside commerce media through its Elements API — the first-party connector, built with third-party discipline: campaign create, budget and flight edits, pause/resume, strategies and placements as ad sets and ads, and delivery plus media-spend reporting normalized to the standard schema.
The Basis DSP through its Platform API: clients, campaigns, line items, and per-line-item delivery stats normalized to the standard schema. The API is read-only by design — campaign changes stay in the Basis UI, and the connector says so.
IAB Tech Lab's AAMP seller agents through OpenDirect 2.1 MCP tool calls — one connection per seller endpoint. Accounts and orders read and write; line bookings commit inventory. The OpenDirect surface carries no delivery reporting, and the connector says so instead of inventing numbers.
AI surfaces
2 connectorsAds inside AI assistants, through the same governed interface — reads and writes available. ads in AI assistants →
Sponsored chat cards in ChatGPT through the public ChatGPT Ads Advertiser API, connected with the advertiser's own API key. Campaigns, ad groups, ads and delivery reporting (account timezone) read into the standard schema. Every draft declares an ad category and runs our pre-flight against OpenAI's published ad policy. Campaign writes run on the governed path (dry run, confirm, live, one change-log row each); writes doc-derived 2026-10-23, a claim about that date. reads doc-derived 2026-10-13.
Sponsored cards and polls inside AI chat assistants through Thrad's advertiser API, connected with an advertiser key. Campaigns, ad groups, ads and delivery reporting (UTC days) read into the standard schema, with delivery split by supply source as reported by Thrad's insights API. Thrad publishes no advertiser ad policy, so our pre-flight blocks every regulated category. Campaign writes run on the governed path (dry run, confirm, live, one change-log row each); writes doc-derived 2026-10-23, a claim about that date. reads doc-derived 2026-10-13.
There is also a built-in sandbox platform (mock): deterministic campaigns and metrics, no credentials, no network — evaluate the full loop before connecting a real account. Platform names and marks identify the third-party services each connector integrates with; they imply no affiliation or endorsement.
Your platform missing?
A connector is a few hundred lines against a documented spec: implement the standard tools, declare your capabilities and your metrics semantics, carry a verification claim per capability, and pass the contract suite every shipped connector runs. LinkedIn, Pinterest and Snapchat are the most-requested — claim one.