Advertising as infrastructure
The taimads wire protocol is public by design: standard formats in (OpenRTB, VAST), verifiable math out (signed receipts, a public Merkle log, a provable take rate). A protocol can be adopted, forked and audited — it can't be quietly changed against you.
Six public surfaces, one contract
Everything below is live in production today — no partner agreement needed to read, verify or integrate.
Serve contract (v1)
GET /api/v1/serve/ad → 4-way decision union (internal / openrtb / house / no-fill) → render → viewability + click beacons. One contract, implemented natively by all 11 SDK surfaces.
OpenRTB 2.5 — both directions
Sell to us or buy from us: POST /api/v1/rtb/openrtb2/auction takes standard bid requests referencing your slot in imp[].tagid; PMP deals honoured via imp.pmp.deals.
VAST 4.0 video
GET /api/v1/serve/vast?api_key=…&slot_id=… returns spec-standard VAST 4.0 for any IAB player — web, in-app or CTV — with full auction, floors and billing behind it.
Transparency log
Every fill: Ed25519-signed receipt at /api/v1/transparency/receipt/{imp_id}, anchored in an RFC-6962 Merkle log. Public key + canonical formats at /.well-known/taimads-transparency.json.
ILRD feed
Impression-level revenue rows (GET /api/v1/mediation/ilrd) straight from the signed receipts — pipe them into AppsFlyer, Adjust, Singular or your own warehouse.
Agent offers
GET /api/v1/agent/offers — sponsored inventory as schema.org ItemList/Offer JSON with explicit sponsorship disclosure. Built for AI shopping agents, not scrapers.
What the protocol guarantees
These invariants are enforced in code, not policy documents.
Every billed impression is receipted.
If we billed it, there is a signed receipt for it — and if there's no receipt, it wasn't billed. The set of receipts is the append-only Merkle log.
The split is in the receipt.
Publisher share, reader dividend and network fee are fields in the signed payload. The take rate is computed from receipts, not asserted.
Consent gates personalisation, never serving.
TCF v2.2 purposes, GPP US sections, CCPA strings and explicit opt-outs flip requests to contextual-only. Contextual demand competes regardless.
Sponsored means labelled.
Every sponsored placement — display, video, product or agent offer — carries an explicit sponsorship marker in the payload.
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