Ads in AI assistants, through the same interface
ChatGPT Ads and Thrad place sponsored units inside AI chat assistants. AdvertisingOS reaches both through their public advertiser APIs as two more connectors — same tools, same schema, same audit trail as every other platform.
every claim below carries its status and the date it was checked — a verification status is a claim about a date, never about now.
An AI-surface campaign is a campaign: the same create, edit and pause tools, the same rehearsal before any live call, the same ledger after it. What the channel adds is stated rather than smoothed over — a declared ad category checked before submission, the platform’s review hold in the preview, and the supplier, retailer and funding party each draft is for.
integrates the public ChatGPT Ads Advertiser API (OpenAPI v2.3.0)
Sponsored chat cards shown in ChatGPT, managed and reported per ad account. The connector calls the public Advertiser API with the advertiser's own key, like any other API client.
live writes verified: yes · the site status follows the connector's own flag
integrates the Thrad advertiser API (v1)
Sponsored cards and polls placed inside AI chat assistants. Delivery arrives split by supply source — Thrad's own and ChatGPT — as reported by Thrad's insights API.
live writes verified: yes · the site status follows the connector's own flag
Every AI-surface draft declares an ad category, and the pre-flight checks it against the platform’s published policy as versioned data. It is our heuristic: passing it is never a prediction of approval, and platform review stays the authority. The pre-flight blocks alcohol (> 0.5% ABV), THC / cannabis, intoxicating hemp THC, tobacco / nicotine, vapes / nicotine pouches, CBD ingestibles, lottery / gaming, kratom / botanicals and other regulated on ChatGPT Ads · OpenAI, and passes CBD topicals only as a warning (warning · refused without restricted-state exclusions); it blocks every regulated category on Thrad.
a silent or unpublished policy blocks the category until a written answer is recorded. sources: openai ad policies · thrad advertiser docs
AdvertisingOS is open infrastructure led and donated by Surfside, which runs commerce media for retailers and the brands that sell through them. In that model a supplier funds an ad that sends shoppers to a retailer’s pages — so every AI-surface draft names the supplier, the retailer and who pays, and the control plane keeps that declaration with the change log. What sits beyond that belongs to AdvertisingOS Cloud, the hosted offering from Surfside, and carries its roadmap status. Reports show observed delivery only: no transaction or return-on-spend claims until the transaction-linked layer exists.
status per docs/cloud-roadmap.md — a capability moves out of planned only when the code exists
Both connectors sit in the catalog beside every other platform and answer list_platforms with their declared capabilities, so an agent reads what each can and cannot do — including whether its writes are open — instead of discovering it on a refused call. Platform names identify the third-party services each connector integrates with; they imply no affiliation or endorsement.