So your AI agent never has to guess.

Read APIs made only for AI agents. Every answer says how old it is and where it came from, so your agent can decide whether to act. Today: XRP Ledger and Solana.

Try a request Open the API

Base URL: https://api.criptonlabs.com

Try asking

  • What is the XRPL fee right now?xrpl_fee
  • Can this Solana account pay its fees?solana_fee_readiness
  • Is this Solana token safe to receive?solana_token
  • What does the XRP/USD order book look like?xrpl_orderbook
  • Are the XRPL nodes healthy?xrpl_network_health
  • Will this XRPL payment succeed?xrpl_payment_readiness

GET /v1/xrpl/fee

Current XRPL fee tiers in drops with a congestion score.

ledger_index
100234567
as_of
2026-10-06T12:00:03.000Z
age_seconds
1
cache
hit
stale
false

stale is true only when cache is stale.

{
  "fee": {
    "economy": "10",
    "standard": "10",
    "priority": "12"
  },
  "congestion": {
    "score": 4,
    "band": "low",
    "load_factor_assumed": false
  },
  "queue_full": false,
  "escalation_multiplier": "1",
  "base_fee": "10",
  "median_fee": "5000",
  "minimum_fee": "10",
  "open_ledger_fee": "10",
  "current_queue_size": "0",
  "max_queue_size": "2000",
  "meta": {
    "ledger_index": 100234567,
    "as_of": "2026-10-06T12:00:03.000Z",
    "age_seconds": 1,
    "cache": "hit",
    "stale": false
  }
}
A static example from the docs. Call the API from a server; browsers are blocked (no CORS). Docs: /docs/xrpl-fee.md

38 read endpoints on two chains

27 on the XRP Ledger and 11 on Solana. All are GET, all return the same JSON conventions, and each route has a paid /v1/pro mirror.

Parameters, examples and error types are in the API docs and openapi.json. The discovery entries at the end are not counted.

XRPL market data and metrics

Fees, ledger, order books, slippage, AMM pools and derived market metrics. 10 endpoints.

  • /v1/xrpl/fee

    Current XRPL fee tiers in drops with a congestion score.

  • /v1/xrpl/ledger/latest

    Latest validated ledger index, hash and close time.

  • /v1/xrpl/orderbook

    CLOB order book for a currency pair with unfunded offers removed.

  • /v1/xrpl/slippage

    Slippage and average price for buying or selling an amount of base currency.

  • /v1/xrpl/amm/{a}/{b}

    AMM pool reserves and trading fee for an asset pair.

  • /v1/xrpl/metrics/pressure

    Buy or sell pressure of a pair's funded order book: a score from 0 to 100 and its band, from the depth near mid.

  • /v1/xrpl/metrics/peg

    How far a registry stablecoin trades from its peg on the XRP Ledger DEX: the deviation of each price route, their median and a status.

  • /v1/xrpl/metrics/fx-basis

    The EUR/USD rate the XRP Ledger DEX implies through the EUR registry stablecoin against each USD registry stablecoin, and its basis to the ECB reference rate.

  • /v1/xrpl/metrics/arbitrage

    Whether a pair's AMM pool and its order book are apart after the AMM fee: per direction the gap, the executable size and the profit after transfer fees.

  • /v1/xrpl/metrics/liquidity-stress

    How stressed a registry stablecoin's liquidity is against its peg default: a score from 0 to 100, its band and the four weighted components behind it.

XRPL accounts and payments

Account state and pre- and post-payment checks. 11 endpoints.

  • /v1/xrpl/account/{address}/summary

    XRP balance, sequence, owner count, transfer rate and trust lines (capped) for an account.

  • /v1/xrpl/account/{address}/lines

    One page of an account's trust lines, with an opaque cursor for the next page.

  • /v1/xrpl/account/{address}/transactions

    One page of an account's most recent validated transactions, newest first.

  • /v1/xrpl/payment-readiness

    Pre-payment check: can this payment from source to destination succeed now?

  • /v1/xrpl/paths

    Multi-hop payment paths and their source cost.

  • /v1/xrpl/address/{address}/kind

    What kind of XRPL address is this, and what does a payment to it need?

  • /v1/xrpl/payment/verify

    Did this settled payment deliver the expected asset and amount to the expected account?

  • /v1/xrpl/x402/preflight

    Can this payer settle this x402 payment requirement right now?

  • /v1/xrpl/domain/{domain_id}/eligibility

    Is this account a member of this XRPL permissioned domain, as its owner or through an accepted, unexpired credential?

  • /v1/xrpl/account/{address}/offers

    One page of an account's open DEX offers, with how funded each one is.

  • /v1/xrpl/account/{address}/commitments

    An account's escrows, payment channels and checks by direction, its deposit preauthorizations, tickets and owner reserve, and what blocks deleting it.

XRPL assets

Issuers, MPT issuances and canonical stablecoins. 3 endpoints.

  • /v1/xrpl/token/{asset}

    Issuer data for an issued asset: flags, domain, transfer fee and total issued.

  • /v1/xrpl/mpt/{mpt_issuance_id}

    MPT issuance: issuer, supply, scale, transfer fee and flags.

  • /v1/xrpl/stablecoin/{asset}

    Is this XRPL issued currency the canonical stablecoin it claims to be?

Solana

Finalized verdicts for transfers, tokens, wallets and payments. 9 endpoints.

  • /v1/solana/transfer-readiness

    Will this Solana transfer succeed? A verdict for SOL or an SPL or Token-2022 token.

  • /v1/solana/token/{mint}

    Is this Solana token safe to hold or receive? A SAFE, WARN or DANGER verdict.

  • /v1/solana/slot/latest

    Latest finalized Solana slot and its block time.

  • /v1/solana/account/{address}/fee-readiness

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

  • /v1/solana/account/{address}/token-hygiene

    Which of this wallet's Solana token accounts can be closed for rent, or are delegated or frozen?

  • /v1/solana/address/{address}/kind

    What kind of Solana account is this address, and should a payment go to it?

  • /v1/solana/stablecoin/{mint}

    Is this Solana mint the canonical stablecoin it claims to be?

  • /v1/solana/payment/verify

    Did this settled Solana payment deliver the expected amount to the expected recipient?

  • /v1/solana/x402/preflight

    Can this payer settle this x402 payment requirement right now?

Health and discovery

Upstream status and the machine-readable entry points. 5 endpoints and 7 discovery resources.

  • /v1/xrpl/health XRPL

    Overall and per-node health of the upstream XRPL nodes (alias of network health).

  • /v1/xrpl/network/health XRPL

    Overall and per-node health of the upstream XRPL nodes.

  • /v1/xrpl/health/history XRPL

    Bucketed upstream probe history with uptime and latency per node.

  • /v1/solana/health Solana

    Whether Solana data is currently being served: latest probe status and finalized slot.

  • /v1/solana/health/history Solana

    Bucketed history of Solana probe results over 1 hour, 24 hours or 7 days.

  • /openapi.json Both

    OpenAPI 3.1 description of every REST route.

  • /llms.txt Both

    Plain-text index of the API for language models.

  • /.well-known/agent-card.json Both

    A2A 1.0 agent card; lists /a2a first, then the MCP endpoints.

  • /v1/pro/requirements Both

    Free price index: every priced route and tool.

  • MCP /mcp Both

    Stateless MCP over Streamable HTTP; views at /mcp/xrpl and /mcp/solana.

  • POST /a2a Both

    Stateless A2A 1.0 JSON-RPC endpoint; each tool is a skill.

  • /status Both

    Live status dashboard of the upstream nodes.

Four ways in for agents

The same data over four entry points. Use the one your client already speaks; no SDK is required.

Turn Over MCP POST /mcp Over A2A POST /a2a
Your agent asks for the XRPL fee
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "xrpl_fee",
    "arguments": {}
  }
}
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "SendMessage",
  "params": {
    "message": {
      "messageId": "m1",
      "role": "ROLE_USER",
      "parts": [{
        "data": {
          "skill": "xrpl_fee",
          "arguments": {}
        },
        "mediaType": "application/json"
      }]
    }
  }
}
The API answers with the same JSON
{
  "result": {
    "content": [
      { "type": "text", "text": "{…}" }
    ],
    "structuredContent": {
      "fee": {
        "economy": "10",
        "standard": "10",
        "priority": "12"
      },
      …,
      "meta": {
        "ledger_index": 108456038,
        "as_of": "2026-11-20T14:57:25.810Z",
        "age_seconds": 0,
        "cache": "miss",
        "stale": false
      }
    }
  },
  "jsonrpc": "2.0",
  "id": 1
}
{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
    "message": {
      "role": "ROLE_AGENT",
      "messageId": "b3d803c1-…",
      "contextId": "babae180-…",
      "parts": [{
        "data": {
          "fee": {
            "economy": "10",
            "standard": "10",
            "priority": "12"
          },
          …,
          "meta": {
            "ledger_index": 108456038,
            "as_of": "2026-11-20T14:57:25.810Z",
            "age_seconds": 0,
            "cache": "hit",
            "stale": false
          }
        },
        "mediaType": "application/json"
      }]
    }
  }
}
Your agent acts

Fresh enough. Sending the payment with a 10 drop fee.

One question asked over MCP and over A2A, captured from the live API on 20 November 2026 and abridged with "…". Both replies carry the body of GET /v1/xrpl/fee, meta included.
MCP
Every REST endpoint is also an MCP tool, over stateless Streamable HTTP with no session and no authentication on the free endpoint. Load one network with a view. /mcp/mcp/xrpl/mcp/solana/mcp/pro MCP quickstart
A2A
A2A 1.0 over JSON-RPC 2.0. Send a message with a skill and its arguments; the reply is the same JSON the REST endpoint returns. POST /a2a/.well-known/agent-card.json A2A guide
OpenAPI
OpenAPI 3.1 description of every REST route, with the free list of priced routes alongside it. /openapi.json/v1/pro/requirements openapi.json
llms.txt
A plain-text overview of the API and its discovery resources, so a model can find the right endpoint without browsing the docs. /llms.txt llms.txt

Connect over MCP

Save as .mcp.json

{
  "mcpServers": {
    "agent-apis": {
      "type": "http",
      "url": "https://api.criptonlabs.com/mcp"
    }
  }
}

Or from a shell: claude mcp add --transport http agent-apis https://api.criptonlabs.com/mcp

What happens when a node fails

Public XRPL and Solana nodes are rate limited and sometimes unavailable. The API smooths that over and tells you when it couldn't.

Each response states its ledger or slot, when it was read and how old it is, so you decide what is fresh enough.

  1. Reads start at the cache

    Hot reads are served from cache, so the nodes are not hit on every call. The TTL is listed on each endpoint page.

    cache: "hit"
  2. A failing node is cut out

    Reads go through several node providers. A failing node is cut out by its circuit breaker and the next one answers.

    cache: "miss"
  3. When every node fails, the last good value answers

    The API serves the last good value and marks it stale, so you know you are reading a copy.

    cache: "stale", stale: true
  4. Past max-stale, the API says no

    A stale value is never older than the endpoint's max-stale. Beyond that, the API answers 503 instead of an old number.

    503 upstream-unavailable

See the current upstream state on the live status page.

Free to read, pay per call for more

Start without an account. Move to the pro namespace when you need higher limits; you pay per call or from a prepaid balance.

Free and pro plans compared
Feature Free Pro
Access No API key or account Pay per call with x402, or spend prepaid credits with a bearer token
Routes All read endpoints under /v1/xrpl and /v1/solana A mirror of every route under /v1/pro/*
MCP and A2A MCP at /mcp and A2A at /a2a Paid MCP endpoint at /mcp/pro with the same tools
Rate limit per IP 60 requests a minute on light routes, 15 on heavier ones, 240 on MCP 240 requests a minute
Daily quota 50 free requests per IP per UTC day (default) Paid per call or from a prepaid balance
Payment assets None EURC or USDC on Solana, RLUSD on XRPL
VAT Not applicable Included in the price