Review-ready, not provider-endorsed · last verified 2026-08-16.
This is an Interchange current-main compatibility snapshot, not provider certification or endorsement. “Implemented” means a provider write/read path exists.
It does not mean fresh signed live evidence exists or that the selected account
is currently eligible.
Coverage and execution-package model
Claim provenance gaps
Object-mapping and reporting rows have no exported, code-owned complete denominator on current main. They remain published because they are useful, but the contract marks the missing drift oracle instead of pretending a same-test literal prevents drift.Evidence state
Static certification and live certification are different claims. Deterministic tests can prove code-owned catalog classifications and fail-closed behavior without contacting the provider. Object-mapping and reporting rows are validated for shape, presence, and uniqueness only; the provenance table above records that they are not compared with a complete code-owned denominator. Fresh live evidence must be dated, signed, bound to the exact account, product, resources, fixture revision, requested package, readback, no-spend result, and cleanup result. Live evidence is treated as stale after 30 days, and a newer failure overrides an older pass.Markets
account_check_required. No global market allowlist is asserted.
This page publishes no global market allowlist.
Authority: The selected account and provider response are authoritative.
Object mapping
Operations
Wholesale products and exact execution bases
Creative formats
The format state is deliberately narrower than the provider format catalog. Onlyexecutable formats have the ordinary provider write and readback path;
canary_only formats are restricted to governed proof, and
catalog_declared formats are present in current code without a public
ordinary-execution certification claim.
declared_not_buyer_selectable formats are not sold through the adapter.
Placements
This provider exposes no placement selector that Interchange can map without inventing inventory.Targeting
Reporting
Conversion and audience support
- Optimization: Product configuration is current-code classified; resource and event eligibility remain account-bound.
- Event-source setup: A callable sync_event_sources surface exists; provider behavior is not certified here.
- Event ingestion: No callable log_event method is present on current main.
- Audiences: A callable audience synchronization surface exists; provider behavior is not certified here.
Known limits
- No provider-flow denominator or current signed full-lifecycle artifact is captured; cancellation remains a named upstream limitation.
- Executable in the direct catalog means current-code classification, not deterministic certification, fresh signed live evidence, or present account eligibility.
- Formats marked catalog_declared are not claims of ordinary provider write/read support.
Public review endpoints
- AAO registry record
- Staging MCP/AdCP state:
relationship_gated_storefront_id_required. - Route template after a storefront relationship supplies its registered platform ID:
https://api.staging.interchange.io/seller/{registered_storefront_platform_id}/mcp - No provider-ID-derived URL is published. The shared MCP route requires a registered storefront platform ID assigned to the relationship; the adapter provider ID spotify is not asserted to be that record ID.