# Solana verdicts

The Solana endpoints answer one question each and return a **verdict**, not raw chain data. Every figure is read at `finalized` commitment, so it can lag the tip of the chain by about 13 seconds. They are a second data network next to the XRP Ledger; the XRPL endpoints are unchanged.

| Question | Endpoint | MCP tool and A2A skill |
|---|---|---|
| Will this transfer of SOL or an SPL or Token-2022 token succeed? | `GET /v1/solana/transfer-readiness` | `solana_transfer_readiness` |
| Is this token safe to hold or receive? | `GET /v1/solana/token/{mint}` | `solana_token` |
| How fresh is the finalized view? | `GET /v1/solana/slot/latest` | `solana_latest_slot` |
| Is Solana data being served right now? | `GET /v1/solana/health` | `solana_network_health` |
| How reliable was it? | `GET /v1/solana/health/history` | none (REST only) |

## The meta object

Solana responses carry `meta` with `slot` (the finalized context slot of the read), `commitment` (always `finalized`), `as_of`, `age_seconds`, `cache` and `stale`. There is no `ledger_index`. On the health endpoint `meta.slot` is 0 while no probe sample is stored or Solana data is not configured.

## Verdicts

- Transfer readiness returns `ready`, every matched blocker and warning code and the derived figures (raw amount, rent of a missing destination token account, Token-2022 transfer fee, net amount). It is not a simulation of the exact transaction: priority fees and program logic are out of scope.
- Token returns `SAFE`, `WARN` or `DANGER` with every matched reason code. It reads only the mint account: no holders, liquidity, price or metadata.
- A mint with no account or that is not an SPL Token or Token-2022 mint answers 404 `solana-mint-not-found`.

## Using the paid mirror

Each endpoint has a mirror under `/v1/pro/solana/*` and the same tools exist on `/mcp/pro`; see the payments guide for when they are charged.