/messari/assets/search

POST /api/messari/assets/search

Price: 1 credit

Screen and rank crypto assets by sector, market cap, and price performance

How to use it

Screen crypto assets with optional filters (sector, sub-sector, category, min/max market cap) and sort them by market cap, fully diluted market cap, 24h volume, price, rank, or price change over 24h/7d/30d. Each result has the asset's id, name, slug, symbol, sectors, sub-sectors, category, live price, 24h volume, circulating and fully diluted market cap, rank, circulating supply, and price change percentages. Use it to find top assets by market cap, gainers and losers, or assets within a sector.

Parameters

• access-token string required

Request body

• timeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)
• count integer required — Max number of assets to return (min: 1)
• sector string nullable — Filter by top-level sector (one of: "Networks", "DeFi", "Stablecoins", "AI", "Meme", "DePIN", "CeFi", "Gaming", "NFTs", "Tools", "Blockchain Infrastructure", "Blockchain Services", "Others")
• sub_sector string nullable — Filter by sub-sector (e.g. 'Layer-1', 'Layer-2')
• category string nullable — Filter by classification category (e.g. 'Cryptocurrency', 'Networks')
• market_cap_min number nullable — Minimum circulating market cap in USD (min: 0)
• market_cap_max number nullable — Maximum circulating market cap in USD (min: 0)
• sort string — Field to sort results by (default: "marketCap"; one of: "marketCap", "fullyDilutedMarketCap", "volume24h", "price", "rank", "priceChange24h", "priceChange7d", "priceChange30d")
• order string — Sort order (default: "desc"; one of: "desc", "asc")

Response

• @type string (default: "MessariAssetResult")
• id string required
• name string nullable
• slug string nullable
• symbol string nullable
• sectors array (default: [])
• sub_sectors array (default: [])
• category string nullable
• price number nullable
• market_cap number nullable
• fully_diluted_market_cap number nullable
• volume_24h number nullable
• market_cap_rank integer nullable
• circulating_supply number nullable
• price_change_percentage_24h number nullable
• price_change_percentage_7d number nullable
• price_change_percentage_30d number nullable

Errors

• 422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.
• 408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.
• 412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.
• 429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.
• 500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.
• 529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.

Response headers

• X-Error — Error message text (present only on error)
• X-Request-ID — Unique request identifier
• X-Execution-Time — Execution time in seconds
• X-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.
• X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.
• X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.
• X-Retry-After — Seconds to wait before retrying. Present only on 429.