API

Access VERROW token reports through a read-only JSON API. Reports include available on-chain evidence, risk signals and coverage. Checks that cannot be completed are marked as Unknown.

Endpoint

Read-only token reports on Elysium.

GET https://elyverrow.xyz/api/scan/{address}

{address} is any 42-character 0x… contract address on Elysium (chain ID 99901). Results may be cached per address to reduce repeated upstream requests. Provider latency and available evidence vary.

Example request

curl https://elyverrow.xyz/api/scan/0xYourTokenAddressHere

Example response (success)

{
  "ok": true,
  "cached": false,
  "report": {
    "schemaVersion": 1,
    "address": "0x...",
    "chainId": 99901,
    "generatedAt": "2026-11-04T10:00:00.000Z",
    "identity": { "name": { "known": true, "value": "Example Token" }, "symbol": { "known": true, "value": "EXT" }, ... },
    "risk": { "score": 35, "level": "medium", "coveragePercent": 86, "findings": [ ... ], "criticalSummary": [ ... ] },
    "contract": { ... },
    "ownership": { ... },
    "holders": { ... },
    "liquidity": { ... },
    "liquidityLock": { ... },
    "deployer": { ... },
    "transferMechanics": { ... },
    "evidenceSources": [ ... ],
    "explorerUrl": "https://scan.elysp.com/#/token/0x...",
    "dexscreenerUrl": "https://styxn.fun/token/0x...",
    "warnings": []
  }
}

Every field that may legitimately be unavailable is shaped as { known: boolean, value | reason } rather than being omitted or defaulted to a falsy value — see the Methodology page for scoring context and data limits. This is an evolving schema; schemaVersion will be incremented on any breaking change.

Errors

Non-2xx responses share this shape.

{
  "ok": false,
  "error": { "code": "RATE_LIMITED", "message": "Human-readable explanation." }
}

Code	HTTP status	Meaning
INVALID_ADDRESS	400	Not a valid EVM address, or not found on Elysium.
IS_EOA	400	Address is a regular wallet, not a contract.
NOT_A_TOKEN	400	Contract exists but exposes no recognizable ERC-20 metadata.
BLOCKSCOUT_ERROR	502	The upstream block explorer could not be reached.
RPC_ERROR	502	The upstream RPC endpoint could not be reached.
RATE_LIMITED	429	Too many requests from this client in the current window.
UNKNOWN_ERROR	500	An unexpected server error occurred.

Rate limits

Requests are limited per client IP address to a small number per minute, enough for normal interactive use and light scripting. If you are rate-limited, the response includes a Retry-After header (seconds) and an HTTP 429 status. A key-based tier for sustained higher-volume access is planned .

Terms of use

This API is provided as-is, without uptime guarantees, for an independent, non-commercial MVP.
Do not use VERROW output as the sole basis for a financial decision — see the disclaimer below.
Please cache responses on your end rather than polling faster than the data actually changes.
Abusive or excessive traffic may be blocked without notice.

This is not a safety guarantee.

VERROW does not label any token as "safe" or "a scam." This report only reflects risk signals that could be verified from public on-chain data and the sources listed above at the time of the scan. Missing or unverifiable data is shown as Unknown and is treated as a risk factor, never as a safe default. Always do your own research before interacting with any token.

Risk reports are informational only and do not constitute financial advice.