Transparency
Discovery Is Not Execution
The single most important transparency rule in the network: a listing that can be found is not the same as a listing that has been executed, and the protocol never blurs the two.
Marketplace rows expose catalog sync, execution mode, and fresh handshake evidence as separate fields.
The weekly validator only initializes connections and lists tools. It never invokes a tool, signs a payment, or claims settlement.
An advertised payment rail is a configured capability, not settlement evidence. Readiness and completion are reported separately.
What Is Public
Production matrix
Live counters: calls received, known users, catalog supply, curated routes
Public metrics endpoint
Product usage totals, machine-readable
Marketplace catalog
The full normalized catalog, searchable and paginated
Health endpoint
Runtime, state, auth, payment, and route readiness
Receipts
Every executed intent returns its route, attempts, cost, and settlement evidence
What Is Not Claimed
The protocol's public copy follows the same discipline as its data surfaces:
No feature is described as live before it ships.
No venue is named before its connector is live; venue classes and counts are cited instead.
No return is promised anywhere; economic parameters are labeled indicative until governed.
Numbers cited in public materials are synced to live marketplace values at the time of publication. Every surface in the table above is live and independently checkable; endpoint paths are documented in the product documentation.
Last updated