DSP
Yahoo DSP
Yahoo
- Interfaces2
- TypesREST, MCP
- Exact tasks3 of 3
- Last re-checked14 Nov 2026
- Maturity index60 · rank =25
States are what public documentation describes for each interface, not account entitlement or tested behaviour. Dataset v2026-11-15.30. How the Atlas decides.
-
REST
Yahoo DSP Traffic/Reporting API
Released · no GA label
- Readdocumented
- Writedocumented
- Optimizedocumented
- Activatedocumented
- Access
- Any customer account
- Sign-in
- OAuth
- Qualifies for
- Create or change a paid campaign or media buyreviewed use-case tag (objects not typed yet)
- Change bids, budgets or pacingreviewed use-case tag (objects not typed yet)
- Put an audience livereviewed use-case tag (objects not typed yet)
- Claims reviewed
- Not re-checked yet; research dated 12 Nov 2026 · 3 sources on the record
- Sources watched
- Weekly watch read 3 of 3 cited pages, last 13 Nov 2026
- Endpoint probed
- Not probed
- Task scope from
- Reviewed use-case tag only (objects not typed)
- In the Atlas since
- Release v2026-11-12.3 (when we recorded it, not a launch date)
Setup not mapped yet: start from the vendor's docs linked on the full record.
-
MCP
Yahoo DSP MCP Server
Released · no GA label · since 23 Oct 2026 (earliest dated source found)
- Readdocumented
- Writedocumented
- Optimizeunknown
- Activatelimited
- Access
- Any customer account
- Sign-in
- OAuth, API key or token
- Qualifies for
- Create or change a paid campaign or media buywrites campaign
- Claims reviewed
- Re-checked 14 Nov 2026, corrected · 1 source on the record
- Sources watched
- Weekly watch read 1 of 1 cited pages, last 13 Nov 2026
- Endpoint probed
- Not probed
- Task scope from
- Typed objects or effects from the record
- Compared side by side
- DSP and CTV buying agents
- Evidence depth
- Each of read, write, optimize, activate, access, auth, launch is tied to one decisive vendor source, checked 14 Nov 2026. Sources and paraphrases on the full record.
- In the Atlas since
- Release v2026-11-12.3 (when we recorded it, not a launch date)
Setup not mapped yet: start from the vendor's docs linked on the full record.
Dated changes
- CorrectedYahoo DSP MCP Server: was Optimize limited; Activate documented; date not given; Docs linked to the MCP endpoint; Task answers: create or change a campaign, change bids, budgets or…; now Optimize unknown: No applied bid/budget/pacing change documented; only a creation-time $500 budget in an example prompt; tools unpublished; Activate…
- Vendor announcement Netflix CAPI enhancement, targeting, Yahoo attribution and upcoming TTD audiences/measurement
Every change with its stable ID: changes.json · RSS.
Cite as: No Fluff Advisory, Agentic Ecosystem Atlas, Yahoo DSP, dataset v2026-11-15.30, https://nofluffadvisory.com/agentic-atlas/companies/yahoo/