COINPAPRIKA API USE CASES

# Crypto API use cases. What will you build?

Build trading dashboards, wallet valuations, research tools and AI agents with CoinPaprika cryptocurrency market data. Explore 44 use cases with API references, implementation steps and data requirements.

[Compare plans](https://coinpaprika.com/api/pricing) [Download catalog JSON](https://coinpaprika.com/api/use-cases.json) [Meet CoinPaprika API](https://coinpaprika.com/api)

44 use cases · 10 topics. Developer workflow catalog; suggested implementations, not prebuilt features or guaranteed exhaustive possibilities.

## Implementation types

- Direct data: render documented fields
- Build with data: calculate or implement logic
- Needs your data: combine with your own records
- DexPaprika: separate product

## Plans and licensing

Records marked Plan name the lowest plan their endpoints need; compare plans at [Pricing](https://coinpaprika.com/api/pricing). Records describing data shown to your customers carry a licence note: display to end customers needs an Enterprise licence, see [Licensing](https://coinpaprika.com/api/licensing).

## Pricing & displays

5 recipes

### Asset price pages

Type: Direct data.

A price page with identity, market context and freshness.

**Your implementation:** Resolve the asset ID, retrieve a ticker and attach metadata.

**What to account for:** Display the source timestamp and missing-value state; prices are not executable quotes.

**Licence:** Showing this data to your customers needs an Enterprise licence. [Licensing](https://coinpaprika.com/api/licensing)

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Asset metadata](https://docs.coinpaprika.com/api-reference/coins/get-coin-by-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-1)

### Multi-currency price displays

Type: Direct data.

USD, EUR or other supported quote displays.

**Your implementation:** Select a supported quote and retain that currency with every displayed value.

**What to account for:** Current-price and historical quote options differ; inspect the endpoint contract.

**Licence:** Showing this data to your customers needs an Enterprise licence. [Licensing](https://coinpaprika.com/api/licensing)

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Price conversion](https://docs.coinpaprika.com/api-reference/tools/price-converter)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-2)

### Market overview dashboards

Type: Direct data.

A market-wide overview alongside individual asset performance.

**Your implementation:** Combine global context with a clearly defined asset universe.

**What to account for:** Do not add an arbitrary subset of assets and label it the entire market.

**Licence:** Showing this data to your customers needs an Enterprise licence. [Licensing](https://coinpaprika.com/api/licensing)

Documentation: [Global market metrics](https://docs.coinpaprika.com/api-reference/global/get-market-overview-data) [Asset price universe](https://docs.coinpaprika.com/api-reference/tickers/get-tickers-for-all-active-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-3)

### Embeddable price widgets

Type: Build with data.

Price components for websites, media and applications.

**Your implementation:** Cache observations on your backend and render a small accessible component.

**What to account for:** Confirm redistribution rights, refresh cadence and attribution for your plan.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Asset metadata](https://docs.coinpaprika.com/api-reference/coins/get-coin-by-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-4)

### Oracle data inputs

Type: Needs your data. Plan: [Enterprise](https://coinpaprika.com/api/streaming) (Uses the Enterprise WebSocket stream).

A market-data input for your oracle infrastructure.

**Your implementation:** Feed retrieved observations into your own validation, aggregation and publication pipeline.

**What to account for:** The API alone is not an on-chain oracle. Delivery guarantees and oracle usage rights need agreement.

**Licence:** Showing this data to your customers needs an Enterprise licence. [Licensing](https://coinpaprika.com/api/licensing)

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Enterprise WebSocket](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-41)

## Trading & monitoring

5 recipes

### Venue and pair discovery

Type: Direct data.

A list of venues and trading pairs for an asset.

**Your implementation:** Join market rows to exchange identities and expose pair-level context.

**What to account for:** A listing is not proof of account eligibility or executable liquidity.

Documentation: [Markets by asset](https://docs.coinpaprika.com/api-reference/coins/get-markets-by-coin-id) [Exchanges by asset](https://docs.coinpaprika.com/api-reference/coins/get-exchanges-by-coin-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-5)

### Cross-venue price comparisons

Type: Build with data.

A screen showing differences between reported venue prices.

**Your implementation:** Normalize quote currencies and compare observations with aligned timestamps.

**What to account for:** Price differences are not executable arbitrage; fees, depth and latency require other inputs.

Documentation: [Markets by asset](https://docs.coinpaprika.com/api-reference/coins/get-markets-by-coin-id) [Markets by exchange](https://docs.coinpaprika.com/api-reference/exchanges/list-an-exchange-markets)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-6)

### Price and activity alerts

Type: Build with data. Plan: [Enterprise](https://coinpaprika.com/api/streaming) (Uses the Enterprise WebSocket stream).

Your own threshold notifications.

**Your implementation:** Evaluate your rules against retrieved observations and deliver notifications through your own service.

**What to account for:** CoinPaprika supplies observations; scheduling, deduplication and delivery belong to your app.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Enterprise WebSocket](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-7)

### Strategy signal inputs

Type: Needs your data. Plan: [Enterprise](https://coinpaprika.com/api/streaming) (Uses the Enterprise WebSocket stream).

Market observations for your strategy engine.

**Your implementation:** Combine observations with your signal rules, risk controls and execution infrastructure.

**What to account for:** Do not infer fills, latency or profitability from aggregated prices.

Documentation: [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin) [Historical OHLC](https://docs.coinpaprika.com/api-reference/coins/get-historical-ohlc) [Enterprise WebSocket](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-8)

### Stablecoin deviation monitoring

Type: Build with data.

A monitor for departures from a specified reference value.

**Your implementation:** Define the reference currency and threshold, then track observed deviations over time.

**What to account for:** A price deviation is not proof of reserve impairment or issuer insolvency.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-44)

## Wallets & valuation

5 recipes

### Portfolio valuation

Type: Needs your data.

Indicative values for users’ holdings.

**Your implementation:** Multiply your balance records by matching asset prices and show the quote currency.

**What to account for:** Wallet balances, custody and transaction records are separate integrations.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-9)

### Portfolio performance

Type: Needs your data.

A portfolio return view that accounts for cash flows.

**Your implementation:** Join historical prices with your dated trades, transfers and positions.

**What to account for:** Deposits, fees and withdrawals must be accounted for; price change alone is not portfolio return.

Documentation: [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin) [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-10)

### Treasury monitoring

Type: Needs your data.

A treasury exposure and valuation dashboard.

**Your implementation:** Join your treasury inventory with prices and your own accounting policy.

**What to account for:** Accounting treatment and asset ownership must be established independently.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-11)

### Indicative payment conversion

Type: Needs your data.

A price estimate before a user chooses how to pay.

**Your implementation:** Combine the conversion with your quote expiry and payment-provider flow.

**What to account for:** Conversion data does not settle payments, lock a rate or guarantee execution.

Documentation: [Price conversion](https://docs.coinpaprika.com/api-reference/tools/price-converter) [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-12)

### Collateral exposure monitoring

Type: Needs your data.

An indicative collateral valuation and exposure view.

**Your implementation:** Combine prices with your positions, loan terms, haircuts and risk policies.

**What to account for:** These are reference prices, not a liquidation engine or guaranteed realizable collateral value.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-42)

## Research & models

5 recipes

### Candlestick and indicator charts

Type: Build with data.

OHLC charts with your own indicators.

**Your implementation:** Calculate moving averages or other indicators over a documented interval.

**What to account for:** Mark incomplete current-day bars; history depth depends on plan.

Documentation: [Historical OHLC](https://docs.coinpaprika.com/api-reference/coins/get-historical-ohlc) [Current-day OHLC](https://docs.coinpaprika.com/api-reference/coins/get-today-ohlc) [Last full-day OHLC](https://docs.coinpaprika.com/api-reference/coins/get-ohlc-for-the-last-full-day)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-13)

### Backtesting datasets

Type: Needs your data.

Historical inputs for a repeatable strategy study.

**Your implementation:** Store asset IDs, date boundaries, missing points and strategy assumptions.

**What to account for:** Avoid survivorship and look-ahead bias; execution, fees and slippage need separate modeling.

Documentation: [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin) [Historical OHLC](https://docs.coinpaprika.com/api-reference/coins/get-historical-ohlc) [Asset directory](https://docs.coinpaprika.com/api-reference/coins/list-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-14)

### Volatility and correlation studies

Type: Build with data.

Derived risk and co-movement measures.

**Your implementation:** Align price observations, calculate returns and state the estimator and window.

**What to account for:** These are your calculations, not API-provided risk scores.

Documentation: [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-15)

### Custom baskets and indices

Type: Build with data.

An indicative index for a defined set of assets.

**Your implementation:** Specify selection rules, weights, rebalancing and missing-data behavior.

**What to account for:** Current membership is not historical membership; avoid presenting research baskets as licensed benchmarks.

Documentation: [Asset price universe](https://docs.coinpaprika.com/api-reference/tickers/get-tickers-for-all-active-coins) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-16)

### Accounting and tax valuation inputs

Type: Needs your data.

Price observations to support your reconciliation process.

**Your implementation:** Match your transaction records to asset IDs, dates, currencies and the valuation method you choose.

**What to account for:** Tax lots, jurisdiction rules, audit evidence and final calculations are your responsibility.

Documentation: [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin) [Price conversion](https://docs.coinpaprika.com/api-reference/tools/price-converter)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-43)

## Sectors & discovery

4 recipes

### Sector screeners

Type: Build with data.

A searchable asset view organized by category.

**Your implementation:** Join category membership with ticker observations and expose your filter rules.

**What to account for:** Tags can overlap; disclose treatment of multi-category assets.

Documentation: [Category directory](https://docs.coinpaprika.com/api-reference/tags/list-tags) [Category details](https://docs.coinpaprika.com/api-reference/tags/get-tag-by-id) [Asset price universe](https://docs.coinpaprika.com/api-reference/tickers/get-tickers-for-all-active-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-17)

### Category rotation dashboards

Type: Build with data.

Comparisons between sector baskets over time.

**Your implementation:** Record membership snapshots and calculate returns with consistent weights.

**What to account for:** The API’s current tags alone do not establish historical constituent membership.

Documentation: [Category details](https://docs.coinpaprika.com/api-reference/tags/get-tag-by-id) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-18)

### Asset search and autocomplete

Type: Direct data.

Search across assets and related entities.

**Your implementation:** Show the entity type and full identity before allowing selection.

**What to account for:** Symbols may be ambiguous; never identify an asset by its symbol alone.

Documentation: [Entity search](https://docs.coinpaprika.com/api-reference/tools/search) [Asset directory](https://docs.coinpaprika.com/api-reference/coins/list-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-19)

### Listing and coverage change tracking

Type: Build with data. Plan: [Starter+](https://coinpaprika.com/api/pricing) (Uses an endpoint that needs the Starter plan or higher).

A change log for assets in your supported universe.

**Your implementation:** Persist snapshots and compare active status, identifiers and coverage.

**What to account for:** A new entry in your snapshots is not necessarily a newly launched token.

Documentation: [Asset directory](https://docs.coinpaprika.com/api-reference/coins/list-coins) [Asset ID changelog](https://docs.coinpaprika.com/api-reference/changelog/get-id-changelog-for-all-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-20)

## Exchanges & markets

4 recipes

### Exchange directories and profiles

Type: Direct data.

Exchange profiles with reported market activity.

**Your implementation:** Use the directory for discovery and fetch details for the selected exchange.

**What to account for:** Reported volume or a data score is not a solvency, custody or regulatory assessment.

Documentation: [Exchange directory](https://docs.coinpaprika.com/api-reference/exchanges/list-exchanges) [Exchange profile](https://docs.coinpaprika.com/api-reference/exchanges/get-exchange-by-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-21)

### Pair concentration analysis

Type: Build with data.

Concentration of reported volume across an exchange’s pairs.

**Your implementation:** Calculate shares with a stated denominator and handle excluded/outlier rows consistently.

**What to account for:** Use the same snapshot and scope; pair counts do not measure liquidity.

Documentation: [Markets by exchange](https://docs.coinpaprika.com/api-reference/exchanges/list-an-exchange-markets)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-22)

### Venue coverage comparisons

Type: Build with data.

A comparison of assets and pairs supported by selected venues.

**Your implementation:** Normalize asset IDs and compare market lists.

**What to account for:** Listing availability does not guarantee that a venue serves a particular user.

Documentation: [Exchanges by asset](https://docs.coinpaprika.com/api-reference/coins/get-exchanges-by-coin-id) [Markets by exchange](https://docs.coinpaprika.com/api-reference/exchanges/list-an-exchange-markets) [Asset directory](https://docs.coinpaprika.com/api-reference/coins/list-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-23)

### Exchange activity history

Type: Build with data.

A time series assembled from recorded exchange snapshots.

**Your implementation:** Collect and persist observations at a chosen cadence before computing changes.

**What to account for:** These referenced endpoints provide snapshots; historical coverage requires your collection or an agreed dataset.

Documentation: [Exchange directory](https://docs.coinpaprika.com/api-reference/exchanges/list-exchanges) [Exchange profile](https://docs.coinpaprika.com/api-reference/exchanges/get-exchange-by-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-24)

## Metadata & identity

5 recipes

### Token identity by contract

Type: Direct data.

Resolve a tracked chain/contract to its market identity.

**Your implementation:** Require both network and contract address before looking up a ticker.

**What to account for:** Coverage is not universal; a matching contract does not certify token safety.

Documentation: [Contract platforms](https://docs.coinpaprika.com/api-reference/contracts/list-contracts-platforms) [Platform contract directory](https://docs.coinpaprika.com/api-reference/contracts/get-all-contract-addressess-for-a-given-platform) [Ticker by contract](https://docs.coinpaprika.com/api-reference/contracts/redirect-to-ticker-by-contract-address)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-25)

### Cross-provider ID migration

Type: Direct data. Plan: [Business+](https://coinpaprika.com/api/pricing) (Uses ID mappings, which need the Business plan or higher).

A maintained mapping between supported provider identifiers.

**Your implementation:** Use documented mappings, store provenance and process ID changes.

**What to account for:** Mapping access is plan-dependent; validate unresolved or changed assets.

Documentation: [Provider ID mappings](https://docs.coinpaprika.com/api-reference/coins/api-id-mappings) [Asset ID changelog](https://docs.coinpaprika.com/api-reference/changelog/get-id-changelog-for-all-coins)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-26)

### Asset research profiles

Type: Direct data.

Profiles with project information and linked people.

**Your implementation:** Present available metadata with links and retrieval dates.

**What to account for:** Metadata and team associations are not independent due diligence or identity verification.

Documentation: [Asset metadata](https://docs.coinpaprika.com/api-reference/coins/get-coin-by-id) [People & project roles](https://docs.coinpaprika.com/api-reference/people/get-person-by-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-27)

### Event calendars and watchlists

Type: Direct data.

Project-event views with available dates and source links.

**Your implementation:** Associate each event with the resolved asset and expose the linked evidence.

**What to account for:** Coverage may be incomplete; event schedules can change.

Documentation: [Asset events](https://docs.coinpaprika.com/api-reference/coins/get-coin-events-by-coin-id) [Asset metadata](https://docs.coinpaprika.com/api-reference/coins/get-coin-by-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-28)

### Contract-based historical research

Type: Direct data.

Historical market context for a tracked contract.

**Your implementation:** Resolve the contract on its platform and use the supported historical ticker redirect.

**What to account for:** This is aggregated asset history, not wallet transactions or per-pool execution history.

Documentation: [History by contract](https://docs.coinpaprika.com/api-reference/contracts/redirect-to-historical-ticks-by-contract-address) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-40)

## AI & developer tools

4 recipes

### Market questions through MCP

Type: Direct data.

Market-data tools in a compatible assistant.

**Your implementation:** Connect the hosted MCP service using the documented client configuration.

**What to account for:** Review available tools and transport support; tool access is not trade execution.

Documentation: [Hosted MCP](https://docs.coinpaprika.com/mcp-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-29)

### Custom research agents

Type: Build with data.

An agent that retrieves evidence for market analysis.

**Your implementation:** Allowlist tools and preserve IDs, query parameters, units and timestamps in the answer.

**What to account for:** Fail explicitly on missing data; do not let a model manufacture observations.

Documentation: [Agent skills](https://docs.coinpaprika.com/skills) [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Historical ticks](https://docs.coinpaprika.com/api-reference/tickers/get-historical-ticks-for-a-specific-coin)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-30)

### Terminal and scheduled research jobs

Type: Build with data.

Repeatable data collection from scripts or notebooks.

**Your implementation:** Use documented CLI or SDK operations and your own scheduler.

**What to account for:** Pin dependencies, handle request limits and keep credentials outside logs.

Documentation: [CLI](https://docs.coinpaprika.com/cli) [Python SDK](https://docs.coinpaprika.com/get-started/sdk-python)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-31)

### Editorial and educational tools

Type: Build with data.

Sourced market context for articles, lessons and briefs.

**Your implementation:** Combine retrieved facts with your own editorial process and link to sources.

**What to account for:** Publish the observation time and review generated interpretation before release.

Documentation: [Asset metadata](https://docs.coinpaprika.com/api-reference/coins/get-coin-by-id) [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Asset events](https://docs.coinpaprika.com/api-reference/coins/get-coin-events-by-coin-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-32)

## Streaming & operations

4 recipes

### Live market displays

Type: Build with data.

A continuously refreshed view for your application.

**Your implementation:** Subscribe to documented asset IDs and manage your client-side presentation.

**What to account for:** Enterprise WebSocket access requires an eligible key; use the relevant transport documentation.

Documentation: [Enterprise WebSocket](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-33)

### Subscription lifecycle management

Type: Build with data. Plan: [Enterprise](https://coinpaprika.com/api/streaming) (Uses the Enterprise WebSocket stream).

A backend that adjusts its market-data subscriptions.

**Your implementation:** Use subscribe/unsubscribe operations, heartbeat handling and reconnect policies.

**What to account for:** Do not assume automatic replay of missed observations; define gap recovery for your product.

Documentation: [Enterprise WebSocket](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-34)

### Data freshness monitoring

Type: Build with data. Plan: [Enterprise](https://coinpaprika.com/api/streaming) (Uses the Enterprise WebSocket stream).

Stale-data indicators for your own downstream systems.

**Your implementation:** Compare observation age against thresholds appropriate to your delivery contract.

**What to account for:** A successful request does not prove freshness; retain the source timestamp.

Documentation: [Ticker by asset](https://docs.coinpaprika.com/api-reference/tickers/get-ticker-for-a-specific-coin) [Enterprise WebSocket](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-35)

### API consumption dashboards

Type: Direct data. Plan: [Starter+](https://coinpaprika.com/api/pricing) (Uses an endpoint that needs the Starter plan or higher).

A view of your own API plan and usage.

**Your implementation:** Read key information on the documented paid API host and reconcile it with your request logs.

**What to account for:** Keep keys server-side; do not expose account details in public pages.

Documentation: [API key usage](https://docs.coinpaprika.com/api-reference/key/get-api-key-info)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-36)

## DEX & on-chain

3 recipes

### Pool and token discovery

Type: DexPaprika.

A DEX-oriented research interface.

**Your implementation:** Explore DexPaprika’s separate pool and token coverage.

**What to account for:** This uses DexPaprika, not an assumed capability of the CoinPaprika REST API.

Documentation: [DexPaprika documentation](https://docs.dexpaprika.com/introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-37)

### Pool liquidity research

Type: DexPaprika.

Pool-level inputs for on-chain liquidity analysis.

**Your implementation:** Use DexPaprika documentation to select chains, pools and available measures.

**What to account for:** Liquidity data is not an executable trade quote; verify chain and pool coverage.

Documentation: [DexPaprika documentation](https://docs.dexpaprika.com/introduction)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-38)

### CEX and DEX comparison

Type: DexPaprika.

A combined view across centralized and decentralized markets.

**Your implementation:** Join CoinPaprika markets to DexPaprika assets using validated chain/contract identity.

**What to account for:** Quotes, timestamps and market mechanics differ; do not match by symbol alone.

Documentation: [DexPaprika documentation](https://docs.dexpaprika.com/introduction) [Markets by asset](https://docs.coinpaprika.com/api-reference/coins/get-markets-by-coin-id)

[Link to this recipe](https://coinpaprika.com/api/use-cases#recipe-39)

## A requirement you don't see?

Scope it with our data team. Bring your data fields, asset universe, history and delivery requirements.

[Discuss your use case](https://coinpaprika.com/api/enterprise#contact)

## Know the boundaries

These recipes are patterns you can build. They do not imply that CoinPaprika provides custody, order execution, wallet transaction indexing, payment settlement, tax calculations, compliance screening, full order books or derivatives funding, open interest and liquidations through the referenced endpoints.

Follow the documented service's contract and confirm coverage and access. Legacy deprecated ticker and Twitter endpoints are intentionally excluded.

[Enterprise WebSocket docs](https://docs.coinpaprika.com/api-reference/streaming-api/streaming-introduction) [Full documentation index](https://docs.coinpaprika.com/llms.txt)

Content reviewed: 2026-10-15.