Skip to main content

Endpoints

Use the live model catalog before hardcoding model IDs. The catalog returns model IDs, context windows, pricing, serving metadata, modalities, supported parameters, and whether a model can be served confidentially.

Query Parameters

string
Set to true to return only models that can be served under zero data retention, meaning the upstream serving route does not retain prompt or completion content.A model is included when at least one route that can serve it operates under zero data retention. Listing a model here means a request for it with provider: {"zdr": true} can be routed. See Zero Data Retention.true is the only accepted value. Any other value, including false, returns 400. Omit the parameter to list the full catalog.
string
Set to true to return only models that are offered confidentially, meaning the model object carries is_tee: true.This filter reports a model’s own capability. It does not promise that a given request will reach an attested provider, which depends on the deployment serving it. To require attestation for a request, send provider: {"aci_verified": true}. See Attested Routing.true is the only accepted value. Any other value, including false, returns 400. Omit the parameter to list the full catalog.
Both filters compose. Combining them returns models that satisfy each constraint. Response entries have the same shape as the unfiltered catalog. There is no zdr field on a model object: the filter is the way to read this property. An invalid value returns 400:

Examples

Response

Model Object Fields

Find Verifiable TEE Models

Filter for models that can be served confidentially:
is_tee: true means the model can be served confidentially. To require attestation for a specific request rather than reading the catalog flag, use Attested Routing. The receipt remains the per-response proof: read the x-receipt-id header, then verify it with Attestation Report and Get Receipt.

Find Zero-Data-Retention Models

is_tee and zdr describe different properties. is_tee says a model can run inside a verified TEE, which constrains who can read memory during execution. Zero data retention says the upstream serving route does not keep prompt or completion content after serving the request. Filter for it with the query parameter rather than inferring it from is_tee:
To route a request under the same constraint, send provider: {"zdr": true} in the request body. See Zero Data Retention.