IXP · Inference eXchange Protocol

One open standard to reach the exchange.

IXP defines how an order is expressed, priced, matched and cleared. Implement it once and your prompts can clear anywhere on Keld. Our plugins and SDKs speak it natively.

Early accessThe spec is stabilising during the beta. Read the draft and send feedback.

The order object

An IXP order carries everything the exchange needs to match and clear it: the prompt, a ceiling price, a deadline, and constraints on model class, latency and use case.

{
  "prompt": "Process this 10,000-line CSV…",
  "ceiling_price": "$0.50/mTok",
  "deadline": "12h",
  "use_case": "batch",
  "model_class": "70b-instruct",
  "constraints": { "region": "eu", "max_latency_ms": null }
}

Lifecycle

An order moves through submitted → matched → executing → cleared → settled. Each transition is recorded in a transparent, auditable log. Execution is durable: retries and model selection happen automatically, and the result returns on completion — no polling.

Who implements it

Keld's plugins and SDKs implement IXP out of the box. Partners and customers are welcome to implement IXP directly if they want to integrate their own tooling with the exchange.