# GET /v1/solana/account/{address}/fee-readiness

Can this Solana account pay the fees of N transactions now?

## Purpose

Checks on finalized state whether `address` can pay the base fees of `transactions` transactions of `signatures` signatures each, at 5,000 lamports per signature, under the validator's fee-payer rules. `account_kind` is `none` (no account or 0 lamports), `system` (a System wallet), `nonce` (an initialized System nonce account) or `other` (it cannot pay fees, an uninitialized nonce account included). After the fees a System wallet must hold 0 or at least the live rent-exempt minimum for 0 bytes, and a nonce account at least the live rent-exempt minimum for 80 bytes. Blockers: account_not_found, not_fee_payer, insufficient_sol_for_fees. Warning: nonce_account. `required_fee_sol` is the total base fee in SOL; priority fees are excluded. No balance is returned. Every figure is read at finalized commitment, so it can lag the tip of the chain by about 13 seconds; `meta.slot` is the lowest context slot of the reads behind the answer.

## When to use

Before sending one or more transactions from a wallet: to learn whether it can pay their base fees without dropping below its rent-exempt minimum.

## When not to use

To check one SOL or token transfer end to end (use `/v1/solana/transfer-readiness`), or to read a balance (none is returned).

## Parameters

| Name | In | Required | Description | Constraints | Example |
|---|---|---|---|---|---|
| `address` | path | yes | Fee-payer account. | A base58 string that decodes to exactly 32 bytes (a Solana public key); anything else is a 400 | `83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri` |
| `transactions` | query | no | Number of transactions to pay for. | Integer from 1 to 1000; default 1 | `10` |
| `signatures` | query | no | Signatures per transaction. | Integer from 1 to 10; default 1 | `2` |

## Request example

```sh
curl -s "https://api.criptonlabs.com/v1/solana/account/83astBRguLMdt2h5U1Tpdq5tjFoJ6noeGwaY3mDLVcri/fee-readiness?transactions=10&signatures=2"
```

## Response example (200)

```json
{
  "ready": true,
  "account_kind": "system",
  "required_fee_sol": "0.0001",
  "blockers": [],
  "warnings": [],
  "meta": {
    "slot": 468263848,
    "commitment": "finalized",
    "as_of": "2026-11-11T20:51:35.997Z",
    "age_seconds": 0,
    "cache": "miss",
    "stale": false
  }
}
```

## Errors

- 400 [invalid-parameters](https://api.criptonlabs.com/errors/invalid-parameters.md)
- 429 [rate-limited](https://api.criptonlabs.com/errors/rate-limited.md)
- 503 [upstream-unavailable](https://api.criptonlabs.com/errors/upstream-unavailable.md)

## Caching

Fresh for 4 seconds; on upstream failure the last good value is served for up to 30 seconds (`meta.stale` is `true`), then the service answers 503. See the [freshness guide](https://api.criptonlabs.com/docs/guides/freshness.md).

## Rate limit

Tier `expensive`. See the [rate-limits guide](https://api.criptonlabs.com/docs/guides/rate-limits.md).

## MCP tool

The MCP tool `solana_fee_readiness` returns the same data. See the [MCP quickstart](https://api.criptonlabs.com/docs/guides/mcp-quickstart.md).
