ApexScout owner view
ApexScout Live Command Center
Real payment movement, proof quality, continuation behavior, runtime traffic, rail status, and accounting integrity. Quiet periods stay quiet; passive reads and validation traffic are never promoted into buyer demand.
Commerce
Payment movement without inflated traction
Daily request activity gives operating context. Product and evidence charts carry the commercial read; raw request volume does not.
Seven-day request pulse
Green points mark paid activity; red outlines mark recorded errors.
Paid evidence quality
Mutually exclusive classes across every paid completion.
Revenue by product
Cumulative paid delivery mix, sorted by settlement value.
Buyer-client continuation
Where proof behavior stops or advances
The first two stages are passive. Everything after explicit start requires a real client action and stays zero until that happens.
Continuation funnel
One free receipt-bound diagnosis after a legitimate paid proof.
Runtime start channels
HTTP, MCP, A2A, and CLI count only explicit starts.
Runtime and distribution
What connected systems are actually doing
Blue lanes are observational activity. Green lanes require commercial evidence. Large blue counts can still represent polling.
Runtime channel activity
APIHub, A2A, CLI, and Solana aggregate counters.
Reliability products
Owner QA and external commercial evidence stay separate.
Settlement rails
Canonical default and explicit alternates
Rail availability is not rail demand. Base remains canonical even when an alternate is technically active.
Base mainnet
eip155:8453
Polygon mainnet
eip155:137
Solana mainnet
solana:5eykt4UsFv8P8NJdTREpY1vzqKqZKvdp
Integrity
Health, reconciliation, and privacy
The dashboard should fail visibly when accounting no longer reconciles or buyer-level data appears.
Accounting checks
Receipt and evidence reconciliation from the canonical aggregate.
Operating health
Cumulative errors are separated from the current UTC day.
Aggregate movement tape
Only real deltas appear here
This browser keeps its own aggregate baseline. It does not store buyer details and does not create synthetic activity.