Protocol, auction, and reporting interfaces.

Sivora Exchange is built as market infrastructure. The stack is organized around an open bid protocol, a matching engine, and desk-scoped reporting — designed to operate inside finite response windows.

Stack

Infrastructure record

OpenRTB

Bid request and response objects are the contract between the exchange and connected desks. Integration details are issued to accepted participants.

Auction

Matching, eligibility, and timeout handling sit in the auction layer. The method in force is applied consistently to the objects received for that impression.

Reporting

Interfaces expose outcomes and activity for the participant’s own desk. They are not a public tape of the entire marketplace.

Latency

Response windows are finite. The stack is designed to operate within those windows. This site does not claim to be the fastest venue in the market.

Objects

What the stack handles

Protocol

Bid stream

Impression-level requests to eligible demand; responses parsed against the stated schema. Malformed or late objects are excluded from the auction.

Rules

Eligibility

Seller controls, buyer constraints, and venue rules are applied before a bid is considered. Eligibility is not a ranking claim.

Windows

Timeouts

Each request carries a response window. The engine does not wait beyond that window to prefer a late bid.

Interface

Reporting interface

Desk-level activity and clearing records. Schema and access are confirmed during technical onboarding.

Partner with Sivora

Discuss a technical seat

Technology partners may request protocol access. State the interface you intend to integrate.

Join the Exchange