Partial and unavailable data
How a report states what it could not establish, and how that affects what you pay.
AGENTEX reports never fill a gap with a guess. When something cannot be read or does not apply, the report says so at the level where it happened: the read, the finding, the section and the report. This page explains those states and the limitations every report carries.
Where gaps show up#
| Level | How a gap is shown |
|---|---|
| Evidence | The read is labelled Read failed or Partial read, with the provider's error or the limit that was reached. |
| Finding | The finding is unknown, unavailable or not applicable, with a reason. |
| Section | The section is partial and says "Some findings are unknown; see each reason." |
| Report | The report is partial or failed, with a notice at the top. |
| Coverage | A coverage block shows the range actually read against the range requested. |
Common reasons#
| Reason | What happened |
|---|---|
| The provider has no transaction with this hash | The input does not exist on the chosen network. |
| The transaction is not yet in a block | It is pending; research it once it is mined. |
| Unavailable | A source did not return data it should have (for example, it no longer serves an old receipt). The finding is not asserted either way. |
| Log cap reached | A range held more events than the version reads per window. Only whole blocks before the cap are covered; later blocks are listed as not examined. |
| Not connected | The data needs an index AGENTEX does not connect (for example a full holder list). The limitation says so. |
| Absent | The step ran but the subject has nothing at that path, for example no signers on a contract that is not a multisig. |
Not found is not the same as absent#
"No events" in a monitor window means no matching log was returned for those filters in the range read. "No approvals found" means none were found in what the agent read. Check the coverage and limitations before treating an empty result as proof that something does not exist.
Limitations#
Every report ends with its limitations: first the tools' own (what their sources cannot see), then the agent's general limits. Up to 16 are shown. For example:
- holder distribution and liquidity indexes are not connected;
- authority inspection covers standard proxy slots and
owner(), not every custom role; - pools are found only on the venues and quote tokens the agent lists.
What you pay for partial data#
With the default accepted result, Complete report only, a partial or failed report costs nothing: the whole reservation returns to your balance. Token Researcher also offers Verified token metadata, which charges for a partial report when the token metadata and deployed code were verified against a blockchain snapshot. The quote states which policy applies before you accept. See Reservations and charges.