Unofficial · Not an IAB Tech Lab artifact
Ad tech specifications as JSON Schema
In the era of agentic development, every standard needs an executable specification, not only prose that agents and implementers have to interpret. This work tries to fill that gap. It adds nothing to the official specifications: it is a pipeline that reads each specification's text and produces a faithful JSON Schema implementation of it. Those schemas are, or should be, the foundation of each standard's SDKs.
Where a text leaves a point open, a recorded decision fills it, the same way in every variant, and goes back to the specification's owners as feedback. Where we would change what a text settles, the change is a separate variant that you switch on. The default, as written, proposes no change. The site is unofficial and isn't an IAB Tech Lab artifact.
It covers OpenProposal, a specification that agents use directly, and the shared standards it rests on: AdCOM's code lists and the Deals API.
The specifications
OpenProposal 3.0
draft 1 · 2 inputs: main, open PRs
The proposal format that buyer and seller agents exchange, from IAB Tech Lab's OpenProposal 3.0 draft 1. Generating it took 39 decisions where the text leaves a point open, and we propose 5 changes, which a switch turns on.
115 types 39 open points filled 5 changes proposed
AdCOM 1.0
main of 2026-07-23 · 2 inputs: main, tag 202607
The code lists that OpenRTB and other specifications cite, such as device types and API frameworks: 42 lists and 287 codes, one vocabulary per list. Its 46 objects come later.
44 types 18 open points filled 0 changes proposed
Deals API 1.0
main of 2026-05-26 · 2 inputs: main, tag 1.0-202602
The Deal Sync API's two payloads, the deal its origin system pushes and the buyer's status response: 6 objects, 9 code lists of its own, and AdCOM's
CategoryTaxonomyandDeviceTypeby reference.28 types 32 open points filled 1 change proposed