What is ARCHR Shield?
ARCHR Shield applies Jupiter Shield risk signals to tokens before an auto-buy executes, and can either block the trade or allow it with a warning depending on your setting.
Risk controls
LiveEvery auto-buy is screened before it executes. ARCHR checks the token against Jupiter Shield risk data, then against your own market-cap, holder, and social filters — and private keys stay encrypted throughout.
Risk data
Jupiter Shield
Secret encryption
AES-256 at rest
Custody
Non-custodial
Agent key access
No retrieval path
Configuration
Every auto-buy passes through each of these in order. Any one of them can stop the trade, and the alert still reaches you.
Shield flags
Block or warn
Market cap
Floor and ceiling
Holder count
Minimum required
Social presence
Verification check
Signal gate
Per-source auto-buy toggle
Global gate
Auto-trading master switch
Explainer
Updated 2026-07-27
Screening a Solana token means checking a short list of things that can make a position unrecoverable regardless of price action: whether the token can actually be sold, whether authorities that let someone freeze or mint remain active, how concentrated the holders are, and whether the liquidity is real enough to exit through.
Those checks are mechanical, which is what makes them automatable. ARCHR Shield uses Jupiter Shield data to flag the structural problems and can block an auto-buy outright or downgrade it to a warning. On top of that sit your own filters — market-cap bounds, minimum holder count, social verification — which encode what you personally consider worth touching.
The second half of security has nothing to do with tokens. A trading bot holds keys that can move your funds, so how those keys are stored matters as much as what it screens. In ARCHR, private keys and agent API keys are AES-256 encrypted at rest, excluded from normal logging, and used only to sign actions you initiated or explicitly configured. The AI agent has no tool that can reveal a key, because no such tool exists to be misused.
None of this makes trading safe, and it would be dishonest to imply otherwise. Filters reduce avoidable, mechanical losses — the sellability trap, the token you would not have bought if you had checked. They do nothing about market risk, and a token that passes every check can still go to zero because the market simply stopped caring.
Token risk
Jupiter Shield surfaces the structural red flags — sellability problems, active authorities, and related contract-level risks. ARCHR reads those signals and applies your chosen posture: block the trade, or let it through with a warning.
Screening runs before execution, on the same path every buy takes, whether it originated from a signal, a copy trade, the agent, or a manual command.
Your rules
Shield decides whether a token is structurally broken. Your filters decide whether it is interesting. Market-cap floors keep you out of the first chaotic minutes; ceilings keep you out of things that have already run. Holder minimums and social checks are crude proxies for whether anyone other than the deployer is present.
These are per-signal, so a source you trust can run looser rules than one you are still evaluating.
Account security
Keys are encrypted at rest and used only for actions you authorized. Telegram ID is the identity surface, and sensitive messages are handled with that in mind.
The agent cannot retrieve a private key. That is not a permission setting you could accidentally flip — the capability is absent, which is the only version of that guarantee worth having.
Common questions
Direct answers, including the ones where the honest answer is “no”.
ARCHR Shield applies Jupiter Shield risk signals to tokens before an auto-buy executes, and can either block the trade or allow it with a warning depending on your setting.
Partially. Automated screening catches mechanical problems like unsellable tokens, active mint or freeze authorities, and extreme holder concentration. It cannot detect a team that simply abandons a legitimate-looking token, and no filter set removes market risk.
ARCHR is non-custodial in the sense that keys are yours and are AES-256 encrypted at rest, used only to sign actions you initiated or explicitly configured for automation. They are stored encrypted in ARCHR's database rather than on your device.
No. There is no tool in the agent's toolset that returns a private key, so there is no prompt that can make it do so.
Shield risk posture, market-cap floor and ceiling, minimum holder count, and social verification — each configurable per signal source, on top of the global auto-trading switch.
Keep reading
ARCHR runs in Telegram. @archr_signal_bot — free to start, 1% platform fee on trades.
Memecoin trading is highly volatile and can result in total loss of capital. ARCHR provides software tools, not financial advice. Read the full risk disclosure and terms of use.