# General filters

General filters

The **General** category includes two main subcategories: **Main** and **Price-Related** filters. These filters enable you to extract tokens based on fundamental criteria, allowing you to narrow down your selection efficiently. Let's explore each filter in more detail. ## Blokiments Score This is the primary score that consolidates all token metrics into a single value, ranging from 0 to 100 (with higher values being better). For a detailed explanation, refer to the [**Scores** section](/features/discovery-hub/filters-guide/our-scores.md). This filter is also **sortable**, meaning you can sort the token results based on their **Blokiments Score** for easier comparison and analysis.

Example of using Blokiments score as a filter and a sorting value.

## DEX Name
What is a DEX? A **DEX**, or **Decentralized Exchange**, is a place where people can trade cryptocurrencies **directly with each other** without needing a middleman like a bank or a traditional exchange. Instead of a company holding your money, a DEX runs on blockchain technology using **smart contracts**, which automatically match and process trades. You stay in control of your crypto the whole time. In short, a DEX allows you to swap cryptocurrencies with others directly and securely, utilizing **blockchain technology.**
In the decentralized world of blockchain, most trading occurs on decentralized exchanges, commonly referred to as **DEXes**. To trade any token created on a blockchain, that token must be listed on a decentralized exchange (DEX). Each blockchain can have multiple DEXes, and it's common for a single token to be traded across several of them. At **Blokiments**, we aggregate token data based on **DEX pools**. This filter allows you to extract only those tokens that are traded on a specific DEX. For example, if you want to see only tokens available on **Uniswap V3**, you can set the filter to `UniswapV3`. We support numerous DEXs across various blockchains, and our list is regularly updated. You can view the full list of supported decentralized exchanges (DEXes) [here](/roadmap-and-releases/supported-networks.md#supported-dexes). You can apply multiple `=` filters in a single query, and the same applies to the `!=` operator. However, the `=` and `!=` operators **cannot** be used together in the same query. When multiple filters are applied, they are treated as **OR** conditions β€” meaning the token only needs to match **one** of the specified criteria.

Example of setting up 2 DEX Name filters.

## Pair/Token Age in Days When researching tokens to trade, it's very common to filter by **token age** or **pair age**. These filters can be helpful in different scenarios: * If your strategy is to **"ape in" on early-launched tokens, you can use the filter to show only tokens created within** the last 5 days, for example. * If you prefer a **less risky** trading approach, consider looking for tokens that are older than 30 days. {% hint style="warning" %} **Note:** Trading newly launched tokens can be extremely risky. Over **95% of all rug pulls occur within the first day** after a token is launched. {% endhint %}
πŸŽ“ What is the difference between a token and a pool (pair)? A token is a digital asset issued on a blockchain, often following standards like ERC-20 on Ethereum. It represents a unit of value or utility. Its creation is an independent event that defines its supply and functionality. A liquidity pool (or pair) is a smart contract that enables decentralized trading by holding reserves of two tokens, typically the token in question and a base asset (like WETH, SOL or a stablecoin). These pools use Automated Market Maker (AMM) algorithms to facilitate swaps and provide liquidity. To draw an analogy, consider a token as an independently manufactured product. Liquidity pools are like different retail outlets where the product is sold. Here are the key points: * Multiple Pairings: A single token can be paired with various other tokens across different liquidity pools. Each pool acts as an independent market with its own liquidity depth, trading volume, and fee structure. * Sequence of Creation: The token must be deployed to the blockchain before creating any liquidity pool. In practice, liquidity pools can be launched much later than the token, allowing for evolving market opportunities. * Trading Dependency: Without an active liquidity pool, there is no mechanism for price discovery or trade execution. A token cannot be traded if it isn’t paired in a liquidity pool.
We offer **two separate filters**: * **Token Age**: Tracks how long ago the token itself was created. * **Pair Age**: Tracks how long ago the trading pair (pool) was created. These are not always the same β€” it's common for a trading pair to be launched days or even weeks after the token is created. If you're looking to discover **new projects**, filtering by **token age** is usually the better choice. The age metrics measure the number of full days since creation: * If a pair was created on September 1st and today is September 10th, the **pair age** will be **9 days** (counting full days passed). * If a token was created within the **last 24 hours**, its **token age** will be **0**. * If it was created between **24 and 48 hours ago**, the age will be **1**, and so on. These filters enable you to target tokens that align with your risk profile and trading strategy. {% hint style="info" %} The filter can also be used as a sort value. {% endhint %}

An example of filtering tokens newer than 3 days and sort them from the newest to the oldest.

## Price change in % This filter allows you to find tokens based on their **percentage price movement** over a specific time frame. 1. Enter the percentage threshold for the filter (e.g. `40` to filter tokens that moved 40% or more, depending on the operator you selected.) 2. Define the period over which the price change is measured. The available options are: 30d, 7d, 1d, 12h, 4h, 1h.
When you add **multiple filters**, they are evaluated using **AND logic**. This means that **all conditions must be true** for a token to appear in the results. For example, if you apply: 1. **Price Change β‰₯ 40% (1d)** 2. **Price Change ≀ 10% (12h)** Only tokens that satisfy **both conditions** β€” 40%+ change in the last 24 hours **and** no more than 10% change in the last 12 hours β€” will be included. ## Price trend If you don’t want to deal with exact percentage movements every time, you can use the **Price Trend** filter instead. In the background, we continuously calculate the trend for each token in real-time, classifying it as an uptrend, a sideways trend, or a downtrend. This gives you a quick way to assess the overall direction of a token's price without needing to set specific percentage thresholds. We currently support trend analysis over three time frames: * **1 day (1d)** * **7 days (7d)** * **30 days (30d)** For example, you can easily filter for tokens that have been in an **uptrend over the last 7 days**, making it easier to spot momentum without manual calculations.

A price trend filter usage example.

## Example This [example is configured](https://blokiments.com/s/0dbac572) to find **Solana-based tokens** that meet all of the following conditions: 1. **🟠 Blokiments Score β‰₯ 40** * Only includes tokens with a **Blokiments Score of 40 or higher**, indicating stronger fundamentals based on our internal metrics. 2. **🟠 DEX Name = PumpSwap AMM** * Filters for tokens that are **traded specifically on PumpSwap AMM**. 3. **🟠 Token Age β‰₯ 3 days** * Ensures tokens are **at least 3 days old**, avoiding newly launched tokens that may carry higher risk. 4. **🟠 Token Age ≀ 30 days** * Limits results to **tokens no older than 30 days**, focusing on relatively new projects. 5. **🟠 Price Change (1d) β‰₯ 40%** * Includes only tokens that have experienced a **price increase of 40% or more in the last 24 hours**, highlighting strong short-term momentum. 6. **🟠 Price Trend = Uptrend (7d)** * Filters for tokens that have shown a consistent **uptrend over the past 7 days**, according to our trend analysis model.

Filter configuration

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.blokiments.com/features/discovery-hub/filters-guide/general-filters.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.