CryptoQuant XRP Entity Status API
The XRP Entity Status API from CryptoQuant — 1 operation(s) for xrp entity status.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/cryptoquant:cryptoquant-xrp-entity-status-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
version: 1.3.0
title: CryptoQuant Data XRP Entity Status API
termsOfService: https://cryptoquant.com/terms-of-service
contact:
name: API Support
email: contact@cryptoquant.com
description: The CryptoQuant Data API provides simple and powerful endpoints to get information on general transaction data and aggregate on-chain statistics straight from the blockchain. The API root endpoint URL is `https://api.cryptoquant.com/v1/`.
servers:
- url: https://api.cryptoquant.com/v1
description: Default server
tags:
- name: XRP Entity Status
paths:
/xrp/entity-status/entity-list:
get:
tags:
- XRP Entity Status
summary: Entity List
description: 'This endpoint returns entity list to serve data.
| Entity Type | Description |
|------------------------|----------------------|
| exchange | centralized exchange |
| builder | entities contributing to xrp ledger |
| team | xrp project related team or related individuals|
| foundation | xrp foundation |
| custody | custody service |
| otc | otc service |
| bank | bank |
| bridge | bridge |'
operationId: getXRPEntityList
parameters:
- description: A type from the entity
explode: false
in: query
name: type
required: false
schema:
type: string
style: form
example: exchange
- description: A format type about return message type. Supported formats are json, csv.
explode: false
in: query
name: format
required: false
schema:
type: string
default: json
style: form
example: json
x-codeSamples:
- lang: Shell
source: 'curl -X GET "https://api.cryptoquant.com/v1/xrp/status/entity-list" \
-H "Authorization: Bearer <YOUR_API_KEY>"'
- lang: JavaScript
source: "fetch(\"https://api.cryptoquant.com/v1/xrp/status/entity-list\", { headers: { \"Authorization\": \"Bearer <YOUR_API_KEY>\"} })\n .then(response => response.json())\n .then(data => console.log(data))"
- lang: NodeJS
source: "require('axios')\n .get(\"https://api.cryptoquant.com/v1/xrp/status/entity-list\", { headers: { Authorization: 'Bearer <YOUR_API_KEY>' } })\n .then(response => console.log(response))"
- lang: Ruby
source: 'require ''net/http''
uri = URI("https://api.cryptoquant.com/v1/xrp/status/entity-list")
req = Net::HTTP::Get.new(uri)
req["Authorization"] = "Bearer <YOUR_API_KEY>"
res = Net::HTTP.start(uri.hostname, uri.port, use_ssl: true) { |http| http.request(req) }
puts res.body'
- lang: Python
source: 'import requests
headers = {''Authorization'': ''Bearer <YOUR_API_KEY>''}
url = "https://api.cryptoquant.com/v1/xrp/status/entity-list"
print(requests.get(url, headers=headers).json())'
responses:
'200':
description: Entity list on a given type.
content:
application/json:
schema:
type: object
required:
- status
- result
properties:
status:
type: object
description: The status object is return with most of requests and indicates if the request was successful. If it is not successful, error information is included.
properties:
code:
type: integer
format: int32
description: HTTP status code
message:
type: string
description: Text description of the error or success.
required:
- code
- message
result:
type: object
required:
- type
- data
properties:
type:
type: string
description: Type of given entity list. This field is one of "exchange", "miner"
data:
type: array
items:
type: object
required:
- name
- symbol
- is_validated
- market_type
properties:
name:
type: string
description: The name of entity.
symbol:
type: string
description: The name of calling symbol.
is_validated:
type: integer
description: Entity is validated or in progress.
market_type:
type: integer
description: Market type of entity.
example:
status:
code: 200
message: success
result:
type: string
data:
- symbol: example
security:
- AccessToken: []
components:
securitySchemes:
AccessToken:
type: http
scheme: bearer
bearerFormat: JWT
description: 'For each API request, include this HTTP header:
`Authorization` with the `Bearer <YOUR_API_KEY>`. Bearer access token is the type of HTTP Authorization. You have to include access token to the HTTP header and note that leading bearer is required.
You must include your access token in HTTP header in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please [upgrade your plan](https://cryptoquant.com/pricing) to Professional or Premium plan. You''ll be able to see your access token on the [API tab](https://cryptoquant.com/settings/api) of your profile page after the subscription.'
QueryParameter:
type: apiKey
name: api_key
in: query
description: 'For each API reqeust, include `api_key` parameter.
You must request with your access token in query parameter in every request you make. The token is unique, issued for each client, and regularly changed(once a year). To obtain an access token, please [upgrade your plan](https://cryptoquant.com/pricing) to Professional or Premium plan. You''ll be able to see your access token on the [API tab](https://cryptoquant.com/settings/api) of your profile page after the subscription.
If you are using Excel, you can use the `api_key` parameter to request with your access token to return data either in `json` or `csv`.'
x-tagGroups:
- name: Discovery
tags:
- Available Endpoints
- Supported Stablecoin List
- Supported ERC20 List
- Supported Alt List
- name: Bitcoin
tags:
- BTC Entity Status
- BTC Exchange Flows
- BTC Flow Indicator
- BTC Market Indicator
- BTC Network Indicator
- BTC Miner Flows
- BTC Inter Entity Flows
- BTC Fund Data
- BTC Market Data
- BTC Miner Data
- BTC Network Data
- BTC Mempool Statistics
- BTC Lightning Statistics
- name: Ethereum
tags:
- ETH Entity Status
- ETH Exchange Flows
- ETH Flow Indicator
- ETH Market Indicator
- ETH 2.0
- ETH Fund Data
- ETH Market Data
- ETH Network Data
- name: XRP
tags:
- XRP Entity Status
- XRP Entity Flows
- XRP Flow Indicator
- XRP Market Data
- XRP Network Data
- XRP Network Indicator
- XRP Dex Data
- XRP AMM Data
- name: TRX
tags:
- TRX Market Data
- TRX Network Data
- TRX DEFI
- name: Stablecoin
tags:
- Stablecoin Entity Status
- Stablecoin Exchange Flows
- Stablecoin Flow Indicator
- Stablecoin Market Data
- Stablecoin Network Data
- name: ERC20
tags:
- ERC20 Entity Status
- ERC20 Exchange Flows
- ERC20 Flow Indicator
- ERC20 Market Data
- ERC20 Network Data
- name: Alt
tags:
- Alt Market Data
- name: Utilities
tags:
- Latency
x-provenance:
method: harvested
publisher: CryptoQuant
source: https://docs.cryptoquant.com/openapi/v1.json
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)