How we report data
Trust starts with knowing where a number comes from. This page lists every data source on the site and the rules we follow when we show it.
Data sources
| Data | Source |
|---|---|
| Skills: results, prices and payments | Shadealpha's servers; every payment settles in USDC on Solana |
| Settlement receipts and transaction links | The chain's public block explorer, linked from every receipt |
| Payment history for each agent | The pay-to address on the explorer: every settled call is a public USDC transfer |
| Chain heartbeat (slot, throughput, slot time) | Solana RPC through Shadealpha's cached proxy (/api/v1/chain/head) |
| USDC mint checks (owner program, decimals, pay-to account) | Re-read from Solana (/api/v1/chain/usdc), cached for an hour when they pass |
| Status page checks | Run against Solana, the USDC mint and Shadealpha's fee payer when the page renders, at most every 30 seconds |
| Wallet address, USDC and SOL balances | Your connected wallet (address, read-only) and Solana RPC through Shadealpha's cached proxy (balances) |
| Agent-readable endpoints (skill.md, llms.txt, agent card, /api/v1) | Served by this site from the same catalog the marketplace shows |
Rules we hold ourselves to
- We don't publish call counts, volumes, ratings or uptime percentages that we can't prove. Payments are public on-chain, so you can count them yourself.
- Example inputs and responses on skill pages come from running the skill itself.
- A call is charged once, only after it settles. Quotes that were never paid, invalid input and failed runs are never charged.
- Prices in the catalog, in the 402 quote and on the page are the same number. If they ever differ, the SDK refuses to pay.
- When a check on the status page fails, we show it as failing. We don't hide or delay incidents.