# Supply and evidence — AdBuyMCP

Evaluate supported media and distinguish an implemented client from a verified commercial buying route.

## Seven buyer-facing channels

| Channel | Buying model |
| --- | --- |
| Paid search | Native search campaigns and reviewed keyword/negative targeting. |
| Paid social | Native social campaigns with supplier-specific targeting and creative requirements. |
| Connected TV | CTV video via eligible native suppliers or managed inventory. |
| Podcast and audio | Audio assets, contextual/native targeting and managed publisher placements. |
| Addressable TV | Household-oriented broadcaster and booking workflows; separate from CTV. |
| Cinema | Venue and catchment planning with managed booking and clearance. |
| DOOH | Screen, venue and place-based planning with supplier-specific inventory and booking. |

## Read operation-level evidence

The repository has 26 connectors, including buying, data and measurement integrations. That number is not a count of live-certified buying suppliers.

Read list_connections and the supplier dossier for the authenticated account. Capabilities are operation-specific: a working inventory read does not establish creative acceptance, activation, reporting or stop support.

Native API suppliers and managed bookings follow different workflows. A supplier confirmation window is not an instant programmatic purchase.

## Known execution limits

- Live supplier seats and controlled campaign acceptance remain required. No offline fixture is evidence that the account can buy media.
- StackAdapt terminal budget/flight states do not reveal an independent configured spend switch; those states retain final reconciliation holds pending a verified contract.
- Hivestack needs verifiable gross-cost readback and exact report columns/currency before automatic enable and settlement.
- Amazon DSP write operations without a verified current contract remain disabled; its reporting contract is experimental.
- Vibe supports US inventory and whole-USD budgets. The public prepaid platform is GBP-only, so that client cannot yet be funded through the buying flow.
- Some providers remain explicit stubs or human booking workflows. Availability also depends on the advertiser account, geography and exact operation.

## Niche targeting is a request, not a promise

The compiler preserves audience intent and labels unsupported constraints. Modeled catalogue matches are proposals, not verified provider segment IDs or audience counts.

Native targeting must preserve the approved geography and constraints. Unsupported exclusions, unresolved semantics or mismatched countries fail rather than silently widening the audience.