Developers / Standards
Standards support
Check which versions and features Riptide supports before connecting a buyer, player, verification service, or agent. The notes below describe coverage and limitations.
| Standard | Target | Status | Notes |
|---|---|---|---|
| OpenRTB | 2.6 default, 2.5 accepted | Partial | Supports request parsing, demand connections, and bid responses. Some fields and interoperability cases have limited coverage; check the OpenRTB guide for integration details. |
| VAST | 4.3 target; 4.2 XSD-tested rendering; 2.0/3.0 negotiation | Partial | Supports inline and wrapper ads, macros, trackers, companions, and negotiated interactive resources. VAST 4.3 coverage is incomplete. |
| OpenRTB Native | 1.2 | Supported | Validates requested assets and returns ad responses with event trackers and privacy fields. |
| HLS and SCTE-35 boundaries | RFC 8216 media playlists | Supported | Per-session SSAI manifests, CUE/DATERANGE break boundaries and AES-128 handling. SCTE-35 payloads are opaque; multivariant playlists are not accepted by the media-playlist parser. |
| IAB GPP | SIDs 2, 5, 6, 7 (v1/v2), 8-27 (v1) | Supported | Consent sections determine permitted data use. Unsupported or malformed US sections restrict processing. Forward the consent signals collected by your integration. |
| DSA transparency | Platform-rendered ad disclosures | Supported | Uses privacy signals to determine required ad disclosures. Riptide includes the configured disclosure when it renders the ad, and can reject an ad if a required disclosure cannot be shown. |
| schain (SupplyChain) | OpenRTB 2.6 source.schain | Partial | Includes single-hop and multi-hop supply chains in outbound requests. Some completeness checks and older inbound field locations have limited support. |
| ads.txt / app-ads.txt | 1.1 | Supported | Serve, crawl, analyze, verify and enforce configured supply policies, including OWNERDOMAIN, MANAGERDOMAIN and app developer-site discovery. |
| sellers.json | 1.0 | Supported | Canonical endpoint, confidential sellers, identifiers, upstream passthrough resolution and scheduled partner checks. |
| ads.cert | 2.0 Authenticated Connections | Supported | Signs outbound connections and verifies inbound connections, with DNS key discovery and rotation. Requires configured signing keys and verification policies. |
| IAB Content Taxonomy | 3.1 | Supported | Supports category lookup, taxonomy selection, and restrictions for sensitive content. |
| MRC / IAB video measurement | June 2018 + SSAI guidance | Supported | Counts ads when rendering begins and distinguishes on-time from late tracking events. Riptide does not claim certification by a measurement authority. |
| OpenRTB impression expiration | 2.6 imp.exp / bid.exp | Supported | Delivery windows, sealed beacons and on-time/late classification. |
| OMID | 1.5 integration | Partial | Configured AdVerifications resources are emitted subject to API negotiation. Vendor naming and some resource attributes remain limited; Riptide does not supply a player measurement SDK. |
| MCP | 2025-06-18 | Supported | POST /mcp streamable HTTP, stdio, tools/resources/prompts and durable tasks. Registered agents sign requests; HTTP replies are JSON and GET /mcp does not open an event stream. |
| IAB AAMP | Identity, scope, task and audit alignment | Partial | Agent identity, permissions, tasks, and audit are implemented. AAMP-specific protocol conformance has not been verified. |
| AdCP | Sales / Signals / Creative / Trusted Match | Partial | Gateway tools transact against supported platform operations. Broader protocol roles and full external wire conformance remain outside the supported subset. |
| ARTF | current | Monitored | Under review; no supported integration. |
| Privacy Sandbox / PAAPI | n/a | Monitored | Outside the server-side SSP/DSP scope. |
Supported: the listed features are implemented and tested. Partial: available with the limitations described above. Planned: intended for a future release. Monitored: under review, with no committed implementation. See the examples and integration guides for setup instructions.
Check compatibility before launch
Support applies to the versions and features listed here. Test your buyer or player integration with the formats, consent signals, and tracking events you expect to use. Contact us if you need a field or protocol behavior that is not covered in the guides.
Check your integration requirements
Send us the protocol version, fields, and buyer or player behavior you need. We can clarify the supported cases before you start integrating.