API Status Available

The Intelligence
Layer for Solana DeFi. The
Intelligence
Layer for
Solana DeFi.

Risk signals, safer swap context, creator launch flows, and practical analytics built around the Solana ecosystem.

Launch App Documentation
DATA & ECOSYSTEM SOURCES
Solana
Bags
Jupiter
Helius
Jito
Meteora
Raydium
Orca
DexScreener
Connect
Bags Shield
Scan before you sign
Paste token mint...
Scan
Quick Actions
Launch
Swap
Market
Status API/RPC
API Status Available
Home
Launch
Portfolio
Swap
Profile
Settings
Core Modules

Everything users need
to act with more context.

Scan, analyze, swap, and launch with clearer risk signals before interacting on-chain.

Token Risk Scan

Analyze token-level signals such as mint and freeze authority, metadata mutability, source coverage, liquidity context, holder distribution, and transfer restrictions when available.

Source Coverage

See which providers responded, what was verified, and what remains unknown. Missing data stays visible instead of being replaced by fake fallback values.

Safer Swap Context

Use Jupiter-powered execution with pre-swap risk context so users can review signals before signing.

Product Depth

More than a scanner.

Bags Shield brings together scanning, launching, portfolio tracking, swap context, wallet-linked profiles and safety settings in one Solana-focused app.

Scanner Home

Paste a token mint, run a scan, review recent scan history, and check API/RPC status directly from the main dashboard.

Guided Launchpad

Create Solana tokens through a guided launch flow with name, symbol, description, supply presets, image/metadata inputs and social links.

Creator Portfolio

Track launched tokens, review launch status, monitor lock context and see eligible Bags fee positions from one creator dashboard.

Fee Claims in App

Creators can review eligible Bags fee positions and prepare claim transactions directly from the app where supported.

Risk-Aware Swap

Use Jupiter-powered swap routing with pre-action context, market filters and token discovery views before signing.

Profile & Activity History

Wallet-linked profiles and activity history help users revisit scans, actions and account context across sessions.

Safety Settings

Review API/RPC health, wallet context, language preferences, slippage controls, max input settings and protected send roadmap items.

Launchpad active

Launch smarter on Solana

Bags Shield Launchpad combines token creation, guided setup, risk-aware context, and eligible fee visibility in a single creator flow.

Guided Token Creation

Create tokens through a cleaner flow designed to reduce setup mistakes and make key launch decisions easier to review.

Security-First Setup

Review critical configuration details before launch, with explicit wallet boundaries and risk-aware messaging.

Eligible Fee Visibility

Track supported Bags fee positions and prepare claims tied to trading activity from eligible launched tokens.

Post-Launch Context

Connect launch activity with scan context, monitoring signals, and creator-side visibility after the token goes live.

Bags fee visibility

Track eligible launch fees.

When eligible

Track supported Bags fee positions and prepare claims from the creator experience without exposing private keys or Bags API secrets in the browser.

Creator flow Launch, monitor, claim
Context layer Scanner + fee visibility
Explore Launchpad
Bags Shield is built as a practical security and execution layer: ShieldScore, source coverage, safer swap context, creator-oriented launch flows and fee-claim visibility where supported by the Bags flow.
Security-First Infrastructure

Infrastructure for
risk-aware execution.

How Bags Shield connects risk signals, swap context, creator flows, and eligible fee visibility through a server-side API.

MODEL

Jupiter Executes. Bags Shield Adds Context.

Jupiter handles routing. Bags Shield adds validation, ShieldScore signals, pre-swap context, and transparent fee metadata before the user signs.

  • Transparent fee metadata: 50 bps app fee where applicable.
  • Risk context: Signals are surfaced before execution.
  • Fee Visibility: Creator and app fee language stays explicit where supported.
TRUST

Scan Explain Act with Context.

Most scanners dump data. Bags Shield turns source coverage into clearer decisions by showing signals, reasons, and unknowns.

  • Pre-action risk signals: Risk context appears before wallet confirmation.
  • ShieldScore: A compact scoring layer for quick review.
  • Explainable reasons: Authorities, mutability, liquidity, and coverage.
ENGINE

Built for scale and traceability.

A server-side stack designed with typed validation, request IDs, provider coverage, and transparent failure states.

  • Vercel + TypeScript: Server-side API routes with typed contracts.
  • Zod/AJV validation: Inputs are checked before upstream calls.
  • Provider coverage: Helius, Birdeye, DexScreener, Jupiter.
  • Request IDs: Traceable IDs on API calls.
  • Solana Mobile pathway: Wallet-aware UX direction where supported.
Documentation & API

Build with Bags Shield
without guessing the risk model

Understand how Bags Shield scans risk, adds pre-action context, prepares swaps, and supports creator launch flows on Solana.

API Reference Launch Standards Token Launchpad Eligible Fees Security Model Best Practices API Health

Documentation Overview

Every API surface is designed around typed validation, request traceability, explicit error states, no-store headers where appropriate, and provider coverage that remains visible when upstream data is partial.

Scanner Runs token-level checks with Solana RPC, Helius, DexScreener and optional provider context. Results are risk signals, not approvals.
Safe Swap Wraps quote and swap preparation with pre-action context. Jupiter handles routing; Bags Shield adds validation and fee transparency.
Launchpad Supports Bags token-info, fee quote, fee-share config, unsigned launch transaction creation and final signed broadcast with server-side guards.
Eligible Fee Visibility Shows explicit launch fee quotes, eligible fee-claim positions, and claim transaction preparation without exposing Bags API secrets in the browser.
Infrastructure Includes health checks, price lookup, market summaries and a Solana RPC HTTP proxy so sensitive upstream endpoints stay server-side.
Security Model Client input is untrusted. Backend validation, request IDs, upstream status reporting and fail-closed Launchpad gates keep risky states visible.
Launchpad Safety & Standards

Launch flows built around Solana-native safety patterns.

Bags Shield keeps launch steps explicit, wallet-signed, source-aware, and server-guarded so creators can review what matters before a token goes live.

Wallet signs Server-side secrets Source coverage Fail-closed gates Metadata clarity Token-2022 aware No fake fallback data
Wallet-Signed Transactions

Launch and claim flows prepare unsigned transactions, but the user signs in their own wallet. Bags Shield does not hold or expose user private keys.

Server-Side Secrets

BAGS_API_KEY, RPC keys, service roles, fee configuration, and admin secrets stay in the API environment, never in the browser bundle.

Metadata Clarity

Launch inputs should produce clear token metadata: name, symbol, image URI, metadata URI, and creator-facing context should be visible before signing.

Authority Awareness

The scanner and launch context surface authority-related signals such as mint authority, freeze authority, metadata mutability, and extension-driven restrictions when available.

Token-2022 Awareness

Bags Shield treats Token-2022 extensions as risk and compatibility context, including transfer fees, transfer hooks, permanent delegates, pausable mints, and non-transferable behavior when detected.

Fail-Closed Gates

When required launch or fee-share checks are incomplete, the flow should stop or return a clear setup-required state instead of silently continuing.

What Bags Shield checks before launch

A launch should never feel like a black box. Bags Shield documents what was prepared, what the wallet signs, what the API sends, and which checks were unavailable.

  • Required creator inputs
  • Token metadata context
  • Fee quote visibility
  • Fee-share configuration state
  • Wallet and signing boundaries
  • Launch transaction purpose
  • Claim eligibility context
  • Provider/source coverage
  • Unknown or unavailable states

What Bags Shield does not claim

Bags Shield is a decision-support layer. It surfaces signals, source coverage, and setup context so users and creators can make more informed choices before signing.

  • It does not certify that a token is safe.
  • It does not guarantee trading outcomes or fee revenue.
  • It does not replace user review or independent due diligence.
  • It does not sign user transactions.
  • It does not expose Bags API secrets or private keys in the browser.
  • It does not fabricate missing provider data.

API Reference

Selected public routes from the current API surface. Launchpad write-flow routes may be feature-gated while fee-share safety checks are active.

Status and health Scan and market context Quote and swap preparation Launchpad token creation Fee visibility and claim preparation
Route Map One API surface, multiple guarded flows.

Status, scan, quote, swap, Launchpad, and fee visibility routes stay grouped by purpose while sharing typed validation, explicit error states, and request traceability.

  • Health
  • Scan
  • Quote
  • Swap
  • Launch
  • Claims
GET/api/health

Operational health check for API availability.

Use for uptime checks before calling scan, swap or launch flows.
GET/api/scan?mint=<mint>

Reads scan context for a Solana token mint.

Also supports POST with JSON fields such as mint, wallet, amount, slippage and locale.
GET/api/quote

Requests a Jupiter quote with inputMint, outputMint, amount and slippageBps.

Platform fee bps are injected server-side and returned with request metadata.
POST/api/swap

Prepares a swap transaction from a validated quote and wallet context.

The wallet signs client-side. The API does not sign user transactions.
GET/api/price

Returns normalized token price data when upstream price coverage is available.

Missing prices stay missing; the app does not fabricate zero-dollar values.
POST/api/rpc

HTTP Solana RPC proxy for browser clients.

Keeps configured RPC URLs off the public bundle and returns upstream JSON as-is.
POST/api/launchpad/token-info

Creates Bags token info metadata context from validated launch inputs.

Returns tokenMint and metadata URI data when Bags accepts the request.
POST/api/launchpad/fee-quote

Computes the explicit launch fee quote shown before wallet signing.

Tips are disabled by default; fee-share basis points are server controlled.
POST/api/launchpad/create-config

Creates or checks Bags fee-share configuration for Launch v2.

Returns safe-mode or setup-required states when a separate setup transaction would be needed.
POST/api/launchpad/create-launch-transaction

Requests an unsigned Bags launch transaction after token-info and config validation.

Requires tokenMint, wallet, metadata URI, initialBuyLamports and configKey.
POST/api/launchpad/send

Broadcasts a final signed launch transaction envelope.

Only final launch purpose is allowed; fee-share setup broadcast is blocked.
GET/api/launchpad/fee-claims/positions

Lists claimable fee positions for a valid wallet query parameter.

Pairs with POST /api/launchpad/fee-claims/transactions for claim transaction preparation.

Example Flows

Short integration paths for common app actions.

Scan before swap

Show risk context before a wallet signs.

  1. GET /api/scan with the output token mint.
  2. GET /api/quote for the proposed route.
  3. POST /api/swap only after the user reviews context.
Launch token

Keep launch steps explicit and traceable.

  1. POST /api/launchpad/token-info.
  2. POST /api/launchpad/fee-quote and /api/launchpad/create-config.
  3. POST /api/launchpad/create-launch-transaction, then wallet signs, then /api/launchpad/send.
Claim eligible fees

Prepare claim transactions without hiding the fee source.

  1. GET /api/launchpad/fee-claims/positions?wallet=<wallet>.
  2. POST /api/launchpad/fee-claims/transactions.
  3. Wallet signs the returned transaction if the user chooses to claim.

Security Notes & Developer Notes

Bags Shield is a decision-support layer. It should not replace user review, wallet confirmation or independent due diligence.

No absolute safety claims

ShieldScore, badges and provider coverage describe observed signals. They are not guarantees and should be shown with source context.

Keep secrets server-side

BAGS_API_KEY, RPC keys, service roles and admin secrets belong in the API environment, never in a browser bundle.

Respect signed-transaction boundaries

The API may prepare unsigned transactions, but users sign in their wallet. Do not retry signed transactions automatically.

Best Practices

  • Scan before signing.
  • Review source coverage.
  • Treat unknowns as risk.
  • Verify wallet prompts.
  • Keep secrets server-side.
  • Never fabricate fallback data.
  • Use fee claims only through supported Bags flows.
  • Fail closed on launch and claim flows when required context is missing.
# Health check GET https://api.bagsshield.org/api/health
# Token scan by mint POST https://api.bagsshield.org/api/scan { "mint": "<solana-token-mint>", "locale": "en" }