Skip to content
Open protocol

Advertising as infrastructure you can audit

Public references explain the ad request, decision and measurement contract. Source-level capabilities and live deployment configuration are separate; validate the paths your integration uses.

The protocol

Six public surfaces, one contract

These implementations are documented in source. Account access, operational configuration and interoperability must be confirmed before production use.

Serve contract (v1)

The documented GET /api/v1/serve/ad decision distinguishes internal, OpenRTB, house and no-fill responses. Follow the response contract and per-runtime rendering requirements.

OpenRTB source

OpenRTB routes exist in source. Partner compatibility and buying access require integration review.

VAST video path

The backend includes a separate VAST route and the Web SDK source has a playback helper. Player compatibility, click ordering and live eligibility require testing.

Receipts and log

Signed-receipt implementation exists; availability depends on backend configuration and the event path. Merkle log implementation exists. Live completeness and independent inclusion verification remain unverified.

Reporting interfaces

Reporting screens and endpoints exist. Data freshness and financial settlement are separate.

Agent-facing references

Public documentation and a capability manifest describe the integration boundaries. Machine-readable material does not imply provider endorsement or search visibility.

Read the wire contract
Rules of the road

Integration responsibilities

Review the contract and runtime limits together.

Handle no-fill safely.

An unavailable or rejected creative must leave the placement empty and must not trigger paid tracking.

Measure actual visibility.

A server response is not a viewable impression. Host renderers must wait for the documented visibility conditions.

Respect consent and identity.

Forward only the real user context permitted by your privacy requirements. Never share an identity cookie across users.

Verify receipts when available.

Receipt configuration and event paths affect coverage. A missing receipt is not evidence that no financial charge occurred.

Implement the contract

Grab an API key, read the SDK hub, and serve a sandbox ad in minutes — or port the contract to a platform we haven't.

Open the SDK hub