# Axiom Pulse Filter Presets: What to Set for What You Are Hunting

> Six Pulse filter presets, one per thing you might be looking for, with what each filter demonstrably excludes and the tradeoff it accepts. No performance claims, no invented thresholds.

Source: https://axiompedia.com/guides/trading/axiom-pulse-filter-presets

Pulse gives you fourteen filters and no guidance on what to do with them. This page is the missing half: six things you might be hunting, and which filters to move for each, with what every filter demonstrably excludes and what that exclusion costs you.

Nobody sets all fourteen filters every session. Each preset below moves three or four, and one of the six moves none at all, because the thing it asks for is not a Pulse filter.

## How to use these presets

Every value below goes in the same place: the filter panel on the  [Pulse](/guides/trading/axiom-pulse-explained) feed, which sits above the three lifecycle columns. Pick the column first, because it decides what the filters are even filtering, then set the three or four filters the preset names and save the set. Filters persist between sessions, which is worth remembering the next time a feed looks empty for no obvious reason.

If a filter name below does not mean what you assumed it means, [every Pulse column, filter and signal is defined one term at a time](/guides/trading/axiom-pulse-glossary), with the source for each and an explicit note wherever Axiom publishes no definition. Several of the fourteen are in that second category, and the presets here say so where it matters.

**One thing this page will not do is hand you a number.** Axiom publishes no recommended value for any Pulse filter, and the correct liquidity floor for a $50 position is not the correct floor for a $5,000 one. Where a value is determinate, such as a Dev Holding maximum of 0, it is stated. Where it is not, the preset gives the direction and the reasoning and leaves the number to you, which is the same line this site holds on [slippage and priority fees](/guides/trading/best-axiom-trade-settings).

## Preset: brand-new launches

**Column: New Pairs.** Filters: Age (mins) capped low, Dev Holding % capped or set to 0, Bundle % capped or set to 0, Snipers % capped.

Age is the filter that defines what new means for you, and it is measured from creation. Dev Holding at 0 excludes any token where wallets Axiom attributes to the developer still hold supply. Bundle % at 0 excludes any token holding supply in wallets Axiom marks as bundled. Snipers % capped excludes tokens where a high share of early buyers were classified as snipers, which Axiom's own documentation says may indicate bot activity.

**The tradeoff.** On a token that is minutes old, every one of those numbers is computed from very little history, so a clean reading at two minutes is a clean reading of two minutes. The distribution filters get more meaningful as a token ages, and this preset excludes exactly the window in which they would.

## Preset: post-migration

**Column: Migrated to Raydium.** Filters: Liquidity ($) minimum sized to your position, Holders minimum, Num Buys and Num Sells both visible.

Liquidity is the filter that decides what slippage a given trade size costs, so set it before you size a position rather than after. The Holders minimum excludes tokens held by very few wallets, though Axiom's own framing is worth keeping: more holders usually indicate adoption, wallets are not people, and holder count is cheap to manufacture, so read it as a floor on plausibility. Num Buys and Num Sells belong together because either count alone says very little about which way flow is running.

**The tradeoff.** Migration means the bonding curve completed and a Raydium pool exists. Axiom's documentation is explicit that it says nothing about the project, the team, or whether the token still trades tomorrow. This preset filters for a structural event, not for quality.

## Preset: dev has sold

**Column: any.** Filters: Dev Holding % maximum 0, Top 10 Holders % capped.

The first filter excludes every token where wallets Axiom attributes to the developer still hold any share of supply. The second one is there because a developer exiting into ten fresh wallets is not the outcome the first filter appears to promise, and capping concentration is the only thing in the filter set that pushes back on it.

**The tradeoff.** This is the preset with the widest gap between what it filters and what it means. Axiom does not publish how it decides which wallets belong to the developer, so Dev Holding is Axiom's attribution rather than an on-chain fact. Supply moved to a wallet Axiom has not attributed reads as 0 here, and nothing in Pulse will tell you that happened.

## Preset: low holder concentration

**Column: any.** Filters: Top 10 Holders % capped, Holders minimum, Insiders % capped.

Top 10 Holders is the share of supply in the ten largest wallets, and Axiom describes lower values as more decentralized. The Holders minimum matters alongside it because it sets the denominator that concentration is measured against. Insiders % excludes supply Axiom classifies as held by private sales and team members, which is Axiom's own definition and carries none of the securities-law sense of the word.

**The tradeoff.** Ten wallets can be ten people or one person with ten wallets, and no number in the filter set can tell them apart. This preset filters the shape of a distribution, not who stands behind it.

## Preset: no bundlers

**Column: any.** Filter: Bundle % maximum 0. Then run the Bundle Checker separately, because it is not a filter.

Bundle % at 0 excludes tokens holding any supply in bundle-marked wallets. The Bundle Checker is a different thing entirely: a tool that flags four or more transactions landing in the same block, working at any point in a token's life rather than only at launch.

**The tradeoff.** Bundle carries two meanings inside Axiom alone, and this is the preset where that costs you something concrete. A token can read 0% on Bundle % and still get flagged by the Bundle Checker, because one measures a share of supply and the other measures a block-level pattern. Setting the filter is not the same as running the check, and a preset cannot run the check for you.

## Preset: mint authority revoked

**This one does not exist, and that is the useful finding.**

Mint authority and freeze authority are not among the fourteen filters Axiom documents for Pulse. No combination of Age, Top 10 Holders, Dev Holding, Snipers, Insiders, Bundle, Holders, Pro Traders, Liquidity, Volume, Market Cap, Txns, Num Buys or Num Sells delivers that check, because none of them looks at it.

The reason is structural rather than an oversight: mint authority is a property of the token account, and Pulse filters describe the feed. The check happens on a block explorer against the mint address, outside Axiom entirely. Any guide showing you a Pulse mint-authority toggle is describing something Axiom does not document, which is worth knowing before you go looking for a control that is not there.

## Which filters to leave alone, and why

Four of the fourteen are better left unset in most sessions, and one is worth ignoring outright.

**Market Cap ($)** is price multiplied by supply, and on a fresh launch that figure moves fast enough to be stale by the time you read it. Filtering on it mostly filters on latency.

**Volume ($)** and **Txns** describe activity rather than distribution or depth, so they tend to duplicate what Liquidity and the buy and sell counts already tell you, while narrowing the feed further than you probably intended.

**Pro Traders** is the one to ignore. Axiom describes it as the share of experienced traders holding or trading a token, and publishes nothing about what qualifies a trader as experienced. That makes it the least reproducible number in the set, and a filter you cannot reproduce is a filter you cannot reason about.

## What these presets cannot tell you

This is the section that decides whether the rest of the page is worth quoting, so it is deliberately blunt.

**No preset here claims to perform better than another.** Not one line above quotes a hit rate, a win rate, a return, or a token it caught. Producing any of those honestly would mean keeping trading records across many executions, and nobody is keeping them. Every justification on this page is a statement about what a filter demonstrably excludes according to Axiom's documentation, which is a claim this site can stand behind.

**Several of the filters are Axiom's judgment rather than chain data.** Dev Holding, Snipers, Insiders, Bundle and Pro Traders are all underspecified in Axiom's own documentation: the numbers are published, the method that produces them is not. Filtering on them is filtering on a classification you cannot audit. That is not a reason to avoid them, but it is a reason not to read a clean number as a clean token.

**Filters describe a moment.** Every value is computed from the history a token has so far, which on a New Pairs listing is minutes. A token that passes a filter set at 12:00 has told you about 12:00.

**And filters do not price your trade.** They decide what you see. The order ticket decides what you pay for acting on it, and [the settings worth changing before your first entry](/guides/trading/best-axiom-trade-settings) covers the slippage and priority-fee side. If a filtered feed goes empty or a trade off it fails, [the Axiom faults with known causes](/troubleshooting) covers what is usually happening.

These presets were last checked against the filter set Axiom documents on August 25, 2026. Axiom ships fast, so if a filter name here does not match what you see, the documentation is the tiebreaker rather than this page.

You may republish these presets with attribution and a link to https://axiompedia.com/guides/trading/axiom-pulse-filter-presets.

## Related reading

-  [How Axiom Pulse works](/guides/trading/axiom-pulse-explained), the three columns and what the feed is for
- [The Pulse glossary](/guides/trading/axiom-pulse-glossary), every column, filter and signal defined with its source
-  [The settings worth changing before your first trade](/guides/trading/best-axiom-trade-settings), slippage, priority fees and tips
-  [Axiom MEV protection modes](/guides/trading/axiom-mev-protection-modes-explained), the setting that decides how your fill is routed

## FAQ

### What are the best Axiom Pulse filter settings?

There is no single best setting, and anyone publishing one as a number is guessing. Axiom publishes no recommended value for any of the fourteen Pulse filters, and the right liquidity floor depends on the size of the trade you intend. What generalizes is which filters to set for what you are hunting and what each one excludes, which is what this page gives.

### How many filters does Axiom Pulse have?

Fourteen documented filters: Age in minutes, Top 10 Holders percent, Dev Holding percent, Snipers percent, Insiders percent, Bundle percent, Holders, Pro Traders, Liquidity in dollars, Volume in dollars, Market Cap in dollars, Txns, Num Buys and Num Sells. Most traders save a set of three or four rather than adjusting all fourteen every session.

### Can I filter Axiom Pulse for revoked mint authority?

No. Mint authority and freeze authority are not among the fourteen filters Axiom documents for Pulse, so no combination of Pulse filters delivers that check. It is a property of the token account rather than of the feed, and it gets checked on a block explorer against the mint address.

### What is the difference between Bundle percent and the Bundle Checker?

Bundle percent is a filter measuring the share of supply held in wallets Axiom marks as bundled. The Bundle Checker is a separate tool that flags four or more transactions landing in the same block, at any point in a token's life. A token can read zero on the filter and still be flagged by the tool, because they measure different things.

### Do these presets say which tokens will perform well?

No, and nothing on this page claims a preset performs better than another. Every preset is justified by what its filters demonstrably exclude according to Axiom's documentation. Claiming a hit rate or a return would require trading records that nobody is keeping.
