AYZO uses a provider-neutral evidence layer
AYZO may rely on blockchain RPC infrastructure, indexers and other data providers to retrieve network-specific information. The product is designed so provider output is normalized into AYZO evidence semantics rather than exposed as an unexplained provider score.
Source categories
| Source category | Purpose |
|---|---|
| Blockchain / RPC data | Network state, transactions and other chain-native evidence. |
| Indexed blockchain data | Efficient discovery of holder, history or relationship evidence when available. |
| AYZO normalization | Converts provider-specific responses into consistent evidence, coverage and finding structures. |
| AYZO methodology | Controls what the product is allowed to conclude from an observed signal. |
Providers can change without changing the evidence rule
AYZO's goal is not to make a provider brand the product. Data providers can evolve over time; the stable layer should be the definition of the evidence, the limitations attached to it and the way findings are communicated.
What AYZO does not disclose here
This page is product transparency documentation, not infrastructure documentation. It does not expose API credentials, private implementation details or security-sensitive configuration.