Transparency
Catalog methodology
Amply uses a hybrid pipeline: repeatable Amply-measured samples (synthetic self-probes and production route telemetry) plus provider-validated attested catalog fields and reviewed cost-model submissions.
Amply-measured
Scheduled jobs call this deployment's own POST /api/v1/route with standard workloads. Each run records the recommended provider and handler compute_ms in amply_provider_metrics_history as synthetic_probe. Successful customer routes also append rows as route_telemetry.
Seven-day rollups surface as measured_* columns on amply_route_providers, with measured_aggregated_at for freshness.
Provider-validated
Attested metrics (provenance + verification time) remain the primary trust path when fresh. Providers whose catalog row is linked for self-service review may submit a cost_model JSON from the dashboard; it is stored as cost_model_pending_review until staff merge it—pending submissions are not used in automated scoring.
Blended policy
About 70% of the operational signal comes from Amply synthetic probes plus production telemetry on the same code path for every provider. About 30% comes from provider-submitted data that has been validated and merged into the catalog. Live freshness hints appear under GET /api/v1/status → diagnostics.catalog_metrics.