Comparison · checked claim by claim, 14 Nov 2026

Yahoo DSP, FreeWheel Buyer Cloud, Apostra and Vibe agent interfaces compared

Which DSP or CTV buying interface lets an agent change bids or budgets, and how does spend start? Buy-side MCP servers for programmatic and CTV. They differ in whether bid and budget changes are documented operations or only example prompts, and in how a campaign goes live: a server-checked confirmation, an admin-only publish, or nothing published.

Open this comparison in the Atlas How these answers are made

The short answer

Create or change a paid campaign or media buy

Yes: Yahoo DSP MCP Server (writes campaign); FreeWheel Buyer Cloud MCP Server (writes campaign; via bc_v2_post_campaigns, bc_v2_patch_campaigns_id, bc_v2_post_line_items, bc_v2_patch_line_items_id); Apostra v3 account-aware MCP (writes campaign, media buy, flight; via save_campaign, save_media_buy); Vibe MCP server (writes campaign).

Change bids, budgets or pacing

Yes: FreeWheel Buyer Cloud MCP Server (writes bid; via bc_v2_post_bid_modifiers, bc_v2_patch_bid_modifiers_id); Apostra v3 account-aware MCP (writes budget, bid; via save_media_buy (budget, bid)); Vibe MCP server (writes budget).

No or not shown: Yahoo DSP MCP Server: writes campaign, audience, creative, line item, not bids, budgets or pacing.

Put an audience live

None of these.

No or not shown: Yahoo DSP MCP Server: activates campaign delivery, not audience delivery; FreeWheel Buyer Cloud MCP Server: activate is not established by the public documentation; Apostra v3 account-aware MCP: activates paid media spend, not audience delivery; Vibe MCP server: activates paid media spend, not audience delivery.

Yahoo DSP, FreeWheel Buyer Cloud, Apostra and Vibe agent interfaces compared: capabilities, access and tasks per interface
InterfaceYahoo DSPYahoo DSP MCP ServerFreeWheelBuyer Cloud MCP ServerApostraApostra v3 account-aware MCPVibeVibe MCP server
Type and stageMCP · Released · no GA labelMCP · BetaMCP · PreviewMCP · Released · no GA label
Readdocumenteddocumenteddocumenteddocumented
Writedocumenteddocumenteddocumenteddocumented
Optimizeunknownlimitedlimitedlimited
Activatelimitedunknownlimiteddocumented
Create or change a paid campaign or media buyQualifieswrites campaignQualifieswrites campaignQualifieswrites campaign, media buy, flightQualifieswrites campaign
Change bids, budgets or pacingNowrites campaign, audience, creative, line item, not bids, budgets or pacingQualifieswrites bidQualifieswrites budget, bidQualifieswrites budget
Put an audience liveNoactivates campaign delivery, not audience deliveryNoactivate is not established by the public documentationNoactivates paid media spend, not audience deliveryNoactivates paid media spend, not audience delivery
AccessAny customer accountInvite, waitlist, beta or staged rolloutAny customer accountAny customer account
Sign-inOAuth, API key or tokenOAuthOAuth, API key or tokenOAuth
Since23 Oct 2026 (earliest dated source found)not datednot dated16 Jul 2026 (announcement)
Evidence7 of 7 claims tied to a decisive source, read 14 Nov 2026. Sources on the full record · vendor docs7 of 7 claims tied to a decisive source, read 14 Nov 2026. Sources on the full record · vendor docs7 of 7 claims tied to a decisive source, read 14 Nov 2026. Sources on the full record · vendor docs7 of 7 claims tied to a decisive source, read 14 Nov 2026. Sources on the full record · vendor docs

Answers come from the same engine as the Atlas map, the task pages, the open index and the MCP server; a "No" can mean excluded, unknown or another object, and the reason says which. Public documentation only: no account, endpoint or spend was tested. Cite as: No Fluff Advisory, Agentic Ecosystem Atlas, dataset v2026-11-15.30, https://nofluffadvisory.com/agentic-atlas/compare/dsp-buying-agents/