OpenX
OpenX is an independent supply-side platform (SSP) and programmatic ad exchange headquartered in Pasadena, California, founded in 2008. OpenX connects publishers and app developers to advertiser demand through a real-time marketplace that runs OpenRTB-based auctions across display, video, CTV, native, and mobile inventory. Its product suite is organized around the OpenX Exchange (the core marketplace), OpenXSelect (curation, deal creation, and supply-path targeting), OpenXBuild (a software toolkit for assembling custom supply-side workflows and real-time bidstream integrations), and OpenXControl (publisher yield management and demand routing). OpenX exposes several developer-facing APIs documented at docs.openx.com — an OpenRTB API for DSP bidding integrations, a Platform API for account, inventory, demand, targeting, and deal management, a Reporting API for analytics and performance metrics, an OpenXSelect GraphQL API for managing audiences/deals/inventory lists, and an OpenXBuild Real-Time Bidstream API — but the references are gated behind OAuth and OpenX does not publish a public OpenAPI specification or Postman collection. The company is a major contributor to the Prebid.org header-bidding ecosystem (Prebid.js and Prebid Server) and maintains a large GitHub organization with OAuth-based API client libraries in Python, PHP, Java, Perl, and Ruby for the legacy OX3 API. OpenX's business model is transaction-fee based — it takes a share of each ad impression cleared through its exchange — and access to the developer APIs requires an active OpenX account and BD/account-management onboarding rather than self-service signup.
Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.
API Evangelist profiles OpenX the way a machine reads it — 2 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — OpenX scores 13.8/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile OpenX
Each block below is one kind of artifact we hold for OpenX. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
GraphQL 1
Where a provider ships GraphQL, the schema is the contract. We profile it alongside the REST surface so the whole interface is legible in one place.
GraphQL schemas published by this provider.
OpenX GraphQL API
GRAPHQLSecurity Posture 1
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for OpenX — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Documentation 1
Reference material describing how the API behaves
Build 11
SDKs, sample code, and the tooling you integrate with
Scroll within the panel for all 11 ·
Access & Security 1
Authentication, authorization, and security posture
Learn 1
Tutorials, courses, talks, and written guidance
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 7
The organization behind the API
Scroll within the panel for all 7 ·
Other 9
Properties that don't map to a standard resource type
Scroll within the panel for all 9 ·
← All providers · Data indexed from github.com/api-evangelist/openx · machine-readable index on apis.io