​
Reputation

Provider tiers, health signals, and the public routability snapshot.
Malibu has no public reputation score today. It has provider tiers that affect routing weight, live health signals the router acts on, and a public routability snapshot that shows the pool’s state without naming providers.

​
Tiers

There is no self-serve promotion request. Pinned is set only in the coordinator’s own configuration.

​
Health signals the router uses

  • Circuit breaker. Two faults inside 120 seconds mark a provider degraded and take it out of routing until it recovers.
  • Throughput floor. Providers whose estimated throughput is below the production floor (1.0 tokens/sec) are not dispatched to.
  • Heartbeat freshness. Providers silent for 90 seconds are disconnected.
  • Safety holds. A thermal-throttling report removes the provider’s free seats until it clears.
  • Settlement outcomes. A missing or invalid receipt earns the provider nothing for that request (see Verified model settlement).
See Discovery & routing for the full selection order.

​
Public routability snapshot

https://api.malibu.tech serves three public, unauthenticated views of the current pool: Providers are listed by provider_ref, an alias assigned per snapshot. It is not derived from the provider id and does not persist between snapshots. The projection leaves out provider ids, network endpoints, keys, hashes, prompts, buyer ids and hardware identity material. Field notes:
  • receipt_validity says whether the provider’s receipt key is on record: present, pending_rotation or missing. It is not a validity rate over past receipts.
  • attestation summarizes attestation status: hardware (Apple managed device attestation), self_signed (Secure Enclave key only), attested, attestation_failed, attestation_stale, unsupported, not_required or unknown. It does not affect routing today.
Network-wide totals are on GET /v1/stats/overview. See Operations → Network stats.

​
Not available yet

A persistent public per-provider history, a receipt validity rate, buyer-side reputation queries, and on-chain reputation attestations are not available.

​
Privacy

Reputation data is about providers only. Buyer request payloads and buyer identities never appear in it. A buyer’s own usage is visible only to that buyer (via /v1/usage) and to the operator (for billing).