Public evidence

Nayori exposes a human-readable dashboard and machine-readable snapshots derived from the canonical mainnet contracts.

The dashboard separates raw on-chain totals from explicitly attested external adoption. Unknown wallets remain unattested. If a complete chain snapshot is unavailable, the API reports unavailable rather than publishing false zeroes.

Escrow service-fee accounting

Escrow economics are separate: the dashboard's service-fee accounting panel and JSON serviceFees section expose validated ledger observations for the selected STX/sBTC contracts. Each asset has live, unavailable or not-supported status, nullable totals, per-job entries and groups by pinned treasury. All monetary values are atomic decimal strings. quoted is not collected money; charged - refunded = retained, while refundDue counts waived fees still requiring an actual treasury refund. No ledger means no fee charged. Incomplete data prevents totals for the affected asset, and a failed chain source never becomes an empty successful result. This is not a treasury balance, all-generation lifetime total, independent transaction-event audit or external revenue. Current v6/v5 selections expose the service-fee ledger. Historical v5/v4 jobs are outside these active-generation totals and retain their no-fee terms.

Direct x402 and MPP payments

Direct resource payments are not escrow jobs. Their separate dashboard panel refreshes every minute from /api/payments.json, a fixed-origin proxy to the facilitator's /v1/public/payments. The JSON evidence snapshot includes the same source under directPayments; the curated CSV and agent/job/adoption counters are not changed by these payments.

The facilitator feed must be explicitly enabled after QA verification. If disabled, unavailable or malformed, the panel reports unavailable rather than zero payments. QA and production use their own network and resource URLs; the Web rejects a snapshot from a different network.

• Only confirmed settlements with a receipt for Nayori's two configured public resources are eligible.
• Each row is checked against the canonical Stacks transaction, block/hash, payer, recipient and one exact transfer of the canonical asset. Unsupported or reorged records cannot become verified rows.
• The feed checks the latest 25 candidates. hasMore indicates older records; excludedCount counts candidates omitted after chain verification. These figures are not lifetime revenue totals.
• Amounts are atomic decimal strings with explicit decimals, never floating-point token values.
• Delivery status is a facilitator-ledger observation. It is distinct from blockchain confirmation.
• No settlement IDs, quotes, signatures, credentials, raw signed transactions or paid response bodies are exposed. The endpoint accepts no merchant or wallet search parameters.

Known PerkOS wallets are labeled internal; other wallets remain unattested. Neither category automatically qualifies as external adoption or independent customer revenue.

Controlled mainnet examples

Both payments completed confirmation-gated, idempotent delivery on 2026-09-03. They are internal operational tests, not externally operated jobs or grant-adoption evidence.