TrustedRouter / API guide

Model Precision Metadata API Guide

Read per-provider quantization, mixed weight formats, model revisions, and evidence links. Distinguish reviewed configuration from runtime verification.

Model precision overview

Read the selected provider's metadata

Precision belongs to an endpoint, not a model name. GET /v1/models/{author}/{slug}/endpoints returns quantization and trustedrouter.precision for each endpoint. The catalog also exposes these at trustedrouter.endpoints[].quantization and trustedrouter.endpoints[].precision.

import httpx

model = "openai/gpt-oss-120b"
response = httpx.get(
    f"https://trustedrouter.com/v1/models/{model}/endpoints", timeout=20
)
response.raise_for_status()
for endpoint in response.json()["data"]:
    precision = endpoint.get("trustedrouter", {}).get("precision")
    print(endpoint["provider"], endpoint.get("quantization"))
    if precision:
        print(precision["reviewed_on"], precision["model_revision"])
        print(precision["sources"])

These are public metadata endpoints and require no API key. Use model pages to inspect the same evidence visually.

Field meanings

  • quantization: the primary reviewed weight format. Unknown values are null.
  • weight_formats, label, notes: mixed formats and higher-precision exclusions.
  • kv_cache_dtype: the cache representation, separate from model weights. An FP8 KV cache does not establish FP8 weights.
  • model_repository, model_revision: the source model and reviewed revision.
  • reviewed_on, sources: the review date and links to serving code and model configuration.
  • evidence_type: published_serving_config.
  • runtime_verified: false. This is not per-request proof of the weights loaded by the upstream provider.

Unknown stays unknown

Reviewed records must match the provider, canonical model, and upstream ID. An unmatched endpoint returns null rather than an inferred precision. Pricing updates do not automatically refresh these reviews.

A provider changing its deployment requires a fresh review. Follow the evidence links and date before treating the record as current.

Metadata and routing are separate

provider.quantizations filtering is not implemented. Requests using it receive 501 not_supported_in_alpha. The metadata helps you compare and select providers; it does not silently enable a precision guarantee.

Gateway attestation, provider retention policy, reviewed serving configuration, and per-request weight identity are different evidence. Keep that distinction in eval reports.

Workspace access

Sign in

Choose a sign in method to access your TrustedRouter workspace.

By signing in you agree to the terms of service and privacy policy.