Universal Search
Metacore
Universal Search
GET
Universal Search
Documentation Index
Fetch the complete documentation index at: https://docs.mobula.io/llms.txt
Use this file to discover all available pages before exploring further.
Filters
Universal Search accepts an optionalfilters query parameter. The parameter is parsed as JSON, so you can either send a JSON object or a JSON string (for example, filters={"blockchains":"1,solana"} or its URL-encoded form). Keys and values are case-insensitive and surrounding whitespace is ignored.
blockchains
- Accepts either a comma-separated string or a JSON array.
- Supports both numeric chain identifiers (for example
1,8453,42161) and string identifiers (for examplesolana,evm:1,tron:sol). - You can freely mix numeric and string identifiers in the same request; the backend normalizes them before querying.
- Passing multiple IDs limits the search results to tokens that exist on any of the provided chains.
eth while restricting the results to Base (8453), Ethereum (1), Arbitrum (42161), Optimism (10), and Solana.
Search Modes
Prefix Search (default)
By default, the search performs a prefix match on token names and symbols. For example, searchingW will return tokens like “WETH”, “WBTC”, “Wrapped SOL”, etc.
Exact Match (advanced)
Wrap your search term in double quotes to perform an exact match on the symbol. This is useful when you want to find a specific token without getting results that merely start with your query. Example:"W" will only return tokens with the exact symbol “W” (like Wormhole), not “WETH” or “WBTC”.
You can sort by an array of metrics using sortBy (default: searchScore):
volume24hmarketCapcreatedAtvolume1hfeesPaid5minfeesPaid1hfeesPaid24hvolume5minholdersCountorganicVolume1htotalFeesPaidUsdsearchScoretrendingScore24hliquidity
limit parameter (1 to 20, default: 5).
Alpha Feature: When searching by address, the search also returns all tokens deployed by that address (deployer match).
Cookbook: multi-chain filtering
- Identify the chain identifiers you want to include. You can use numeric IDs (
1,56,8453) or string-based IDs (solana,evm:1,evm:8453). Both styles are supported in the same request. - Build the JSON payload for
filters. Set theblockchainsproperty to a comma-separated string of the identifiers (e.g."blockchains":"8453,1,solana"). You may also send an explicit JSON array such as"blockchains":["8453","1","solana"]. - URL-encode the JSON when embedding it inside a query string. Most HTTP libraries will do this automatically if you pass an object.
- Call
/api/2/fast-search?input=<term>&filters=<encoded-json>. The API returns only the top matches that exist on any of the requested chains, making it straightforward to focus on supported networks without enabling all chains globally.
limit and sortBy parameters to surface the most liquid matches on the networks that matter to you.
🔀 Need AND / OR / NOT filters?
The POST variant accepts a JSON body with the same payload shape as a single pulse v2
view — top-level chainId / poolTypes / sortBy / limit, plus a Prisma-like filters tree with AND / OR / NOT and the full leaf-operator set (gte, lte, in, contains, startsWith, …). Useful for per-chain conditional constraints that can’t be expressed as flat GET filters.Query Parameters
Search query string
Type of results to return
Available options:
tokens, assets, pairs JSON string with filter options: blockchains, poolTypes, excludeBonded, bondedOnly
Sort field for search results
Available options:
volume24h, marketCap, createdAt, volume1h, feesPaid5min, feesPaid1h, feesPaid24h, volume5min, holdersCount, organicVolume1h, totalFeesPaidUsd, searchScore, trendingScore24h, liquidity Exclude bonded tokens from results
Maximum number of results (1-20, default: 5)
Response
200 - application/json
Universal Search response