Every trader wonders: how high could this token really go? The price prediction API from Token Metrics lets you explore Moon, Base, and Bear scenarios for any asset—grounded in market-cap assumptions like $2T, $8T, $16T and beyond. In this guide, you’ll call /v2/price-prediction, render scenario bands (with editable caps), and ship a planning feature your users will bookmark. Start by creating a key at Get API Key, then Run Hello-TM and Clone a Template to go live fast.

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches Price Predictions via /v2/price-prediction for any symbol (e.g., BTC, SUI).
  
  
• A simple UI pattern showing Moon / Base / Bear ranges and underlying market-cap scenarios.
  
  
• Optional one-liner curl to smoke-test your API key.
  
  
• Endpoints to add next: /v2/tm-grade (quality context), /v2/trading-signals / /v2/hourly-trading-signals (timing), /v2/resistance-support (stop/target placement), /v2/quantmetrics (risk/return framing).

Why This Matters

Scenario planning beats guessing. Prices move, narratives change, but market-cap scenarios provide a common yardstick for upside/downside. With the price prediction API, you can give users transparent, parameterized ranges (Moon/Base/Bear) and the assumptions behind them—perfect for research, allocation, and position sizing.

Build investor trust. Pair scenario ranges with TM Grade (quality) and Quantmetrics (risk-adjusted performance) so users see both potential and risk. Add optional alerts when price approaches a scenario level to turn curiosity into action—without promising outcomes.

Where to Find 

Find the cURL request for Price Predictions in the top right corner of the API Reference. Use it to easily pull up predictions for your project.

👉 Keep momentum: Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• Scenario Planner (Dashboard): Select a token, choose caps (e.g., $2T / $8T / $16T), and display Moon/Base/Bear ranges with tooltips.
  
  
• Portfolio Allocator: Pair scenario bands with Quantmetrics and TM Grade to justify position sizes and rebalances.
  
  
• Alert Bot (Discord/Telegram): Ping when price approaches a scenario level; link to the dashboard for context.
  
  

Fork a scenario planner or alerting template, plug in your key, and deploy. Confirm your environment by Running Hello-TM, and when you’re scaling users or need higher limits, review API plans.

How It Works (Under the Hood)

The Price Prediction endpoint maps market-cap scenarios to implied token prices, then categorizes them into Bear, Base, and Moon bands for readability. Your inputs can include a symbol and optional market caps; the response returns a scenario array you can plot or tabulate.

A common UX path is: Token selector → Scenario caps input → Prediction bands + context. For deeper insight, link to TM Grade (quality), Trading Signals (timing), and Support/Resistance (execution levels). This creates a complete plan–decide–act loop without overpromising outcomes.

Polling vs webhooks. Predictions don’t require sub-second updates; short-TTL caching and batched fetches work well for dashboards. If you build alerts (“price within 2% of Base scenario”), use a scheduled job and make notifications idempotent to avoid duplicates.

Production Checklist

• Rate limits: Understand your tier caps; add client throttling and worker queues.
  
  
• Retries & backoff: Exponential backoff with jitter for 429/5xx; capture request IDs.
  
  
• Idempotency: De-dup alerts and downstream actions (e.g., avoid repeat pings).
  
  
• Caching: Memory/Redis/KV with short TTLs; pre-warm popular symbols.
  
  
• Batching: Fetch multiple symbols per cycle; parallelize within rate limits.
  
  
• User controls: Expose caps (e.g., $2T/$8T/$16T) and save presets per user.
  
  
• Display clarity: Label Bear/Base/Moon and show the implied market cap next to each price.
  
  
• Compliance copy: Add a reminder that scenarios are not financial advice; historical outcomes don’t guarantee future results.
  
  
• Observability: Track p95/p99 latency and error rate; log alert outcomes.
  
  
• Security: Store API keys in secrets managers; rotate regularly.
  
  

Use Cases & Patterns

• Bot Builder (Headless): Size positions relative to scenario distance (smaller size near Moon, larger near Bear) while confirming timing with /v2/trading-signals.
  
  
• Dashboard Builder (Product): Add a Predictions tab on token pages; let users tweak caps and export a CSV of bands.
  
  
• Screener Maker (Lightweight Tools): Rank tokens by upside to Base or distance to Bear; add alert toggles for approach thresholds.
  
  
• PM/Allocator: Create policy rules like “increase weight when upside-to-Base > X% and TM Grade ≥ threshold.”
  
  
• Education/Content: Blog widgets showing scenario bands for featured tokens; link to your app’s detailed page.
  
  

Next Steps

• Get API Key — generate a key and start free.
  
  
• Run Hello-TM — verify your first successful call.
  
  
• Clone a Template — deploy a scenario planner or alerts bot today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale confidently with API plans.
  
  

FAQs

1) What does the Price Prediction API return?
A JSON array of scenario objects for a symbol—each with a market cap and implied price, typically labeled Bear, Base, and Moon for clarity.

2) Can I set my own scenarios?
Yes, you can pass custom market caps (e.g., $2T, $8T, $16T) to reflect your thesis. Store presets per user or strategy for repeatability.

3) Is this financial advice? How accurate are these predictions?
No. These are scenario estimates based on your assumptions. They’re for planning and research, not guarantees. Always test, diversify, and manage risk.

4) How often should I refresh predictions?
Scenario bands typically don’t need real-time updates. Refresh on page load or at a reasonable cadence (e.g., hourly/daily), and cache results for speed.

5) Do you offer SDKs and examples?
REST is straightforward—see the JavaScript and Python snippets above. The docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

6) How do I integrate predictions with execution?
Pair predictions with TM Grade (quality), Trading Signals (timing), and Support/Resistance (SL/TP). Alert when price nears a scenario and route to your broker logic (paper-trade first).

7) Pricing, limits, and SLAs?
Start free and scale up as you grow. See API plans for rate limits and enterprise SLA options.

‍

The biggest gains in crypto rarely come from the majors. They come from Moonshots—fast-moving tokens with breakout potential. The Moonshots API surfaces these candidates programmatically so you can rank, alert, and act inside your product. In this guide, you’ll call /v2/moonshots, display a high-signal list with TM Grade and Bullish tags, and wire it into bots, dashboards, or screeners in minutes. Start by grabbing your key at Get API Key, then Run Hello-TM and Clone a Template to ship fast.

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches Moonshots via /v2/moonshots (optionally filter by grade/signal/limit).
  
  
• A UI pattern to render symbol, TM Grade, signal, reason/tags, and timestamp—plus a link to token details.
  
  
• Optional one-liner curl to smoke-test your key.
  
  
• Endpoints to add next: /v2/tm-grade (one-score ranking), /v2/trading-signals / /v2/hourly-trading-signals (timing), /v2/resistance-support (stops/targets), /v2/quantmetrics (risk sizing), /v2/price-prediction (scenario ranges).
  
  

Why This Matters

Discovery that converts. Users want more than price tickers—they want a curated, explainable list of high-potential tokens. The moonshots API encapsulates multiple signals into a short list designed for exploration, alerts, and watchlists you can monetize.

Built for builders. The endpoint returns a consistent schema with grade, signal, and context so you can immediately sort, badge, and trigger workflows. With predictable latency and clear filters, you can scale to dashboards, mobile apps, and headless bots without reinventing the discovery pipeline.

Where to Find 

The Moonshots API cURL request is right there in the top right of the API Reference. Grab it and start tapping into the potential!

‍

👉 Keep momentum: Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• Moonshots Screener (Dashboard): A discover tab that ranks tokens by TM Grade and shows the latest Bullish tags and reasons.
  
  
• Alert Bot (Discord/Telegram): DM when a new token enters the Moonshots list or when the signal flips; include S/R levels for SL/TP.
  
  
• Watchlist Widget (Product): One-click “Follow” on Moonshots; show Quantmetrics for risk and a Price Prediction range for scenario planning.
  
  

Fork a screener or alerting template, plug your key, and deploy. Validate your environment with Hello-TM. When you scale users or need higher limits, compare API plans.

How It Works (Under the Hood)

The Moonshots endpoint aggregates a set of evidence—often combining TM Grade, signal state, and momentum/volume context—into a shortlist of breakout candidates. Each row includes a symbol, grade, signal, and timestamp, plus optional reason tags for transparency.

For UX, a common pattern is: headline list → token detail where you render TM Grade (quality), Trading Signals (timing), Support/Resistance (risk placement), Quantmetrics (risk-adjusted performance), and Price Prediction scenarios. This lets users understand why a token was flagged and how to act with risk controls.

Polling vs webhooks. Dashboards typically poll with short-TTL caching. Alerting flows use scheduled jobs or webhooks (where available) to smooth traffic and avoid duplicates. Always make notifications idempotent.

Production Checklist

• Rate limits: Respect plan caps; batch and throttle in clients/workers.
  
  
• Retries & backoff: Exponential backoff with jitter on 429/5xx; capture request IDs.
  
  
• Idempotency: De-dup alerts and downstream actions (e.g., don’t re-DM on retries).
  
  
• Caching: Memory/Redis/KV with short TTLs; pre-warm during peak hours.
  
  
• Batching: Fetch in pages (e.g., limit + offset if supported); parallelize within limits.
  
  
• Sorting & tags: Sort primarily by tm_grade or composite; surface reason tags to build trust.
  
  
• Observability: Track p95/p99, error rates, and alert delivery success; log variant versions.
  
  
• Security: Store keys in a secrets manager; rotate regularly.
  
  

Use Cases & Patterns

• Bot Builder (Headless):
  
  
  
  • Universe filter: trade only tokens appearing in Moonshots with tm_grade ≥ X.
    
    
  • Timing: confirm entry with /v2/trading-signals; place stops/targets with /v2/resistance-support; size via Quantmetrics.
    
    
• Dashboard Builder (Product):
  
  
  
  • Moonshots tab with Badges (Bullish, Grade 80+, Momentum).
    
    
  • Token detail page integrating TM Grade, Signals, S/R, and Predictions for a complete decision loop.
    
    
• Screener Maker (Lightweight Tools):
  
  
  
  • Top-N list with Follow/alert toggles; export CSV.
    
    
  • “New this week” and “Graduated” sections for churn/entry dynamics.
    
    
• Community/Content:
  
  
  
  • Weekly digest: new entrants, upgrades, and notable exits—link back to your product pages.
    
    

Next Steps

• Get API Key — generate a key and start free.
  
  
• Run Hello-TM — verify your first successful call.
  
  
• Clone a Template — deploy a screener or alerts bot today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale confidently with API plans.
  
  

FAQs

1) What does the Moonshots API return?
A list of breakout candidates with fields such as symbol, tm_grade, signal (often Bullish/Bearish), optional reason tags, and updated_at. Use it to drive discover tabs, alerts, and watchlists.

2) How fresh is the list? What about latency/SLOs?
The endpoint targets predictable latency and timely updates for dashboards and alerts. Use short-TTL caching and queued jobs/webhooks to avoid bursty polling.

3) How do I use Moonshots in a trading workflow?
Common stack: Moonshots for discovery, Trading Signals for timing, Support/Resistance for SL/TP, Quantmetrics for sizing, and Price Prediction for scenario context. Always backtest and paper-trade first.

4) I saw results like “+241%” and a “7.5% average return.” Are these guaranteed?
No. Any historical results are illustrative and not guarantees of future performance. Markets are risky; use risk management and testing.

5) Can I filter the Moonshots list?
Yes—pass parameters like min_grade, signal, and limit (as supported) to tailor to your audience and keep pages fast.

6) Do you provide SDKs or examples?
REST works with JavaScript and Python snippets above. Docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

7) Pricing, limits, and enterprise SLAs?
Begin free and scale up. See API plans for rate limits and enterprise options.

‍

Most traders still draw lines by hand in TradingView. The support and resistance API from Token Metrics auto-calculates clean support and resistance levels from one request, so your dashboard, bot, or alerts can react instantly. In minutes, you’ll call /v2/resistance-support, render actionable levels for any token, and wire them into stops, targets, or notifications. Start by grabbing your key on Get API Key, then Run Hello-TM and Clone a Template to ship a production-ready feature fast.

‍

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches Support/Resistance via /v2/resistance-support for a symbol (e.g., BTC, SOL).
  
  
• A one-liner curl to smoke-test your key.
  
  
• A UI pattern to display nearest support, nearest resistance, level strength, and last updated time.
  
  
• Endpoints to add next: /v2/trading-signals (entries/exits), /v2/hourly-trading-signals (intraday updates), /v2/tm-grade (single-score context), /v2/quantmetrics (risk/return framing).

Why This Matters

Precision beats guesswork. Hand-drawn lines are subjective and slow. The support and resistance API standardizes levels across assets and timeframes, enabling deterministic stops and take-profits your users (and bots) can trust.

Production-ready by design. A simple REST shape, predictable latency, and clear semantics let you add levels to token pages, automate SL/TP alerts, and build rule-based execution with minimal glue code.

Where to Find 

Need the Support and Resistance data? The cURL request for it is in the top right of the API Reference for quick access.

👉 Keep momentum: Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• SL/TP Alerts Bot (Telegram/Discord): Ping when price approaches or touches a level; include buffer %, link back to your app.
  
  
• Token Page Levels Panel (Dashboard): Show nearest support/resistance with strength badges; color the latest candle by zone.
  
  
• TradingView Overlay Companion: Use levels to annotate charts and label potential entries/exits driven by Trading Signals.
  
  

Kick off with our quickstarts—fork a bot or dashboard template, plug your key, and deploy. Confirm your environment by Running Hello-TM. When you’re scaling or need webhooks/limits, review API plans.

How It Works (Under the Hood)

The Support/Resistance endpoint analyzes recent price structure to produce discrete levels above and below current price, along with strength indicators you can use for priority and styling. Query /v2/resistance-support?symbol=<ASSET>&timeframe=<HORIZON> to receive arrays of level objects and timestamps.

Polling vs webhooks. For dashboards, short-TTL caching and batched fetches keep pages snappy. For bots and alerts, use queued jobs or webhooks (where applicable) to avoid noisy, bursty polling—especially around market opens and major events.

Production Checklist

• Rate limits: Respect plan caps; add client-side throttling.
  
  
• Retries/backoff: Exponential backoff with jitter for 429/5xx; log failures.
  
  
• Idempotency: Make alerting and order logic idempotent to prevent duplicates.
  
  
• Caching: Memory/Redis/KV with short TTLs; pre-warm top symbols.
  
  
• Batching: Fetch multiple assets per cycle; parallelize within rate limits.
  
  
• Threshold logic: Add %-of-price buffers (e.g., alert at 0.3–0.5% from level).
  
  
• Error catalog: Map common 4xx/5xx to actionable user guidance; keep request IDs.
  
  
• Observability: Track p95/p99; measure alert precision (touch vs approach).
  
  
• Security: Store API keys in a secrets manager; rotate regularly.
  
  

Use Cases & Patterns

• Bot Builder (Headless):
  
  
  
  • Use nearest support for stop placement and nearest resistance for profit targets.
    
    
  • Combine with /v2/trading-signals for entries/exits and size via Quantmetrics (volatility, drawdown).
    
    
• Dashboard Builder (Product):
  
  
  
  • Add a Levels widget to token pages; badge strength (e.g., High/Med/Low) and show last touch time.
    
    
  • Color the price region (below support, between levels, above resistance) for instant context.
    
    
• Screener Maker (Lightweight Tools):
  
  
  
  • “Close to level” sort: highlight tokens within X% of a strong level.
    
    
  • Toggle alerts for approach vs breakout events.
    
    
• Risk Management:
  
  
  
  • Create policy rules like “no new long if price is within 0.2% of strong resistance.”
    
    
  • Export daily level snapshots for audit/compliance.

Next Steps

• Get API Key — generate a key and start free.
  
  
• Run Hello-TM — verify your first successful call.
  
  
• Clone a Template — deploy a levels panel or alerts bot today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale confidently with API plans.
  
  

FAQs

1) What does the Support & Resistance API return?
A JSON payload with arrays of support and resistance levels for a symbol (and optional timeframe), each with a price and strength indicator, plus an update timestamp.

2) How timely are the levels? What are the latency/SLOs?
The endpoint targets predictable latency suitable for dashboards and alerts. Use short-TTL caching for UIs, and queued jobs or webhooks for alerting to smooth traffic.

3) How do I trigger alerts or trades from levels?
Common patterns: alert when price is within X% of a level, touches a level, or breaks beyond with confirmation. Always make downstream actions idempotent and respect rate limits.

4) Can I combine levels with other endpoints?
Yes—pair with /v2/trading-signals for timing, /v2/tm-grade for quality context, and /v2/quantmetrics for risk sizing. This yields a complete decide-plan-execute loop.

5) Which timeframe should I use?
Intraday bots prefer shorter horizons; swing/position dashboards use daily or higher-timeframe levels. Offer a timeframe toggle and cache results per setting.

6) Do you provide SDKs or examples?
Use the REST snippets above (JS/Python). The docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

7) Pricing, limits, and enterprise SLAs?
Begin free and scale as you grow. See API plans for rate limits and enterprise SLA options.

‍

Most traders see price—quants see probabilities. The Quantmetrics API turns raw performance into risk-adjusted stats like Sharpe, Sortino, volatility, drawdown, and CAGR so you can compare tokens objectively and build smarter bots and dashboards. In minutes, you’ll query /v2/quantmetrics, render a clear performance snapshot, and ship a feature that customers trust. Start by grabbing your key at Get API Key, Run Hello-TM to verify your first call, then Clone a Template to go live fast.

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches Quantmetrics for a token via /v2/quantmetrics (e.g., BTC, ETH, SOL).
  
  
• A smoke-test curl you can paste into your terminal.
  
  
• A UI pattern that displays Sharpe, Sortino, volatility, max drawdown, CAGR, and lookback window.
  
  
• Endpoints to add next: /v2/tm-grade (one-score signal), /v2/trading-signals / /v2/hourly-trading-signals (timing), /v2/resistance-support (risk placement), /v2/price-prediction (scenario planning).

Why This Matters

Risk-adjusted truth beats hype. Price alone hides tail risk and whipsaws. Quantmetrics compresses edge, risk, and consistency into metrics that travel across assets and timeframes—so you can rank universes, size positions, and communicate performance like a pro.

Built for dev speed. A clean REST schema, predictable latency, and easy auth mean you can plug Sharpe/Sortino into bots, dashboards, and screeners without maintaining your own analytics pipeline. Pair with caching and batching to serve fast pages at scale.

Where to Find 

The Quant Metrics cURL request is located in the top right of the API Reference, allowing you to easily integrate it with your application.

‍

👉 Keep momentum: Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• Risk Snapshot Widget (Dashboard): Show Sharpe, Sortino, volatility, and drawdown per token; color-code by thresholds.
  
  
• Allocator Screener: Rank tokens by Sharpe, filter by drawdown < X%, and surface a top-N list.
  
  
• Bot Sizer: Use Quantmetrics to scale position sizes (e.g., lower risk = larger size), combined with Trading Signals for entries/exits.
  
  

Kick off from quickstarts in the docs—fork a dashboard or screener template, plug your key, and deploy in minutes. Validate your environment with Run Hello-TM; when you need more throughput or webhooks, compare API plans.

How It Works (Under the Hood)

Quantmetrics computes risk-adjusted performance over a chosen lookback (e.g., 30d, 90d, 1y). You’ll receive a JSON snapshot with core statistics:

• Sharpe ratio: excess return per unit of total volatility.
  
  
• Sortino ratio: penalizes downside volatility more than upside.
  
  
• Volatility: standard deviation of returns over the window.
  
  
• Max drawdown: worst peak-to-trough decline.
  
  
• CAGR / performance snapshot: geometric growth rate and best/worst periods.
  
  

Call /v2/quantmetrics?symbol=<ASSET>&window=<LOOKBACK> to fetch the current snapshot. For dashboards spanning many tokens, batch symbols and apply short-TTL caching. If you generate alerts (e.g., “Sharpe crossed 1.5”), run a scheduled job and queue notifications to avoid bursty polling.

Production Checklist

• Rate limits: Understand your tier caps; add client-side throttling and queues.
  
  
• Retries & backoff: Exponential backoff with jitter; treat 429/5xx as transient.
  
  
• Idempotency: Prevent duplicate downstream actions on retried jobs.
  
  
• Caching: Memory/Redis/KV with short TTLs; pre-warm popular symbols and windows.
  
  
• Batching: Fetch multiple symbols per cycle; parallelize carefully within limits.
  
  
• Error catalog: Map 4xx/5xx to clear remediation; log request IDs for tracing.
  
  
• Observability: Track p95/p99 latency and error rates; alert on drift.
  
  
• Security: Store API keys in secrets managers; rotate regularly.
  
  

Use Cases & Patterns

• Bot Builder (Headless): Gate entries by Sharpe ≥ threshold and drawdown ≤ limit, then trigger with /v2/trading-signals; size by inverse volatility.
  
  
• Dashboard Builder (Product): Add a Quantmetrics panel to token pages; allow switching lookbacks (30d/90d/1y) and export CSV.
  
  
• Screener Maker (Lightweight Tools): Top-N by Sortino with filters for volatility and sector; add alert toggles when thresholds cross.
  
  
• Allocator/PM Tools: Blend CAGR, Sharpe, drawdown into a composite score to rank reallocations; show methodology for trust.
  
  
• Research/Reporting: Weekly digest of tokens with Sharpe ↑, drawdown ↓, and volatility ↓.
  
  

Next Steps

• Get API Key — start free and generate a key in seconds.
  
  
• Run Hello-TM — verify your first successful call.
  
  
• Clone a Template — deploy a screener or dashboard today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale with API plans.
  
  

FAQs

1) What does the Quantmetrics API return?
A JSON snapshot of risk-adjusted metrics (e.g., Sharpe, Sortino, volatility, max drawdown, CAGR) for a symbol and lookback window—ideal for ranking, sizing, and dashboards.

2) How fresh are the stats? What about latency/SLOs?
Responses are engineered for predictable latency. For heavy UI usage, add short-TTL caching and batch requests; for alerts, use scheduled jobs or webhooks where available.

3) Can I use Quantmetrics to size positions in a live bot?
Yes—many quants size inversely to volatility or require Sharpe ≥ X to trade. Always backtest and paper-trade before going live; past results are illustrative, not guarantees.

4) Which lookback window should I choose?
Short windows (30–90d) adapt faster but are noisier; longer windows (6–12m) are steadier but slower to react. Offer users a toggle and cache each window.

5) Do you provide SDKs or examples?
REST is straightforward (JS/Python above). Docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

6) Polling vs webhooks for quant alerts?
Dashboards usually use cached polling. For threshold alerts (e.g., Sharpe crosses 1.0), run scheduled jobs and queue notifications to keep usage smooth and idempotent.

7) Pricing, limits, and enterprise SLAs?
Begin free and scale up. See API plans for rate limits and enterprise SLA options.

‍

‍

Timing makes or breaks every trade. The crypto trading signals API from Token Metrics lets you surface bullish and bearish calls directly in your product—no spreadsheet wrangling, no chart gymnastics. In this guide, you’ll hit the /v2/trading-signals endpoint, display actionable signals on a token (e.g., SOL, BTC, ETH), and ship a conversion-ready feature for bots, dashboards, or Discord. Start by creating a key on Get API Key, then Run Hello-TM and Clone a Template to go live fast.

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches Trading Signals via /v2/trading-signals for one symbol (e.g., SOL).
  
  
• A copy-paste curl to smoke-test your key.
  
  
• A UI pattern to render signal, confidence/score, and timestamp in your dashboard or bot.
  
  
• Endpoints to add next: /v2/hourly-trading-signals (intraday updates), /v2/resistance-support (risk placement), /v2/tm-grade (one-score view), /v2/quantmetrics (risk/return context).

Why This Matters

Action over analysis paralysis. Traders don’t need more lines on a chart—they need an opinionated call they can automate. The trading signals API compresses technical momentum and regime reads into Bullish/Bearish events you can rank, alert on, and route into strategies.

Built for dev speed and reliability. A clean schema, predictable performance, and straightforward auth make it easy to wire signals into bots, dashboards, and community tools. Pair with short-TTL caching or webhooks to minimize polling and keep latency low.

Where to Find 

You can find the cURL request for Crypto Trading Signals in the top right corner of the API Reference. Use it to access the latest signals!

👉 Keep momentum: Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• Trading Bot Starter: Use Bullish/Bearish calls to trigger paper trades; add take-profit/stop rules with Support/Resistance.
  
  
• Dashboard Signal Panel: Show the latest call, confidence, and last-updated time; add a history table for context.
  
  
• Discord/Telegram Alerts: Post signal changes to a channel with a link back to your app.
  
  

Fork a quickstart from the docs, plug your key, and deploy. Validate your environment by Running Hello-TM. When you need more throughput or webhooks, compare API plans.

How It Works (Under the Hood)

Trading Signals distill model evidence (e.g., momentum regimes and pattern detections) into Bullish or Bearish calls with metadata such as confidence/score and timestamp. You request /v2/trading-signals?symbol=<ASSET> and render the most recent event, or a small history, in your UI.

For intraday workflows, use /v2/hourly-trading-signals to update positions or alerts more frequently. Dashboards typically use short-TTL caching or batched fetches; headless bots lean on webhooks, queues, or short polling with backoff to avoid spiky API usage.

Production Checklist

• Rate limits: Know your tier caps; add client-side throttling and queues.
  
  
• Retries/backoff: Exponential backoff with jitter; treat 429/5xx as transient.
  
  
• Idempotency: Guard downstream actions (don’t double-trade on retries).
  
  
• Caching: Memory/Redis/KV with short TTLs for reads; pre-warm popular symbols.
  
  
• Webhooks & jobs: Prefer webhooks or scheduled workers for signal change alerts.
  
  
• Pagination/Bulk: Batch symbols; parallelize with care; respect limits.
  
  
• Error catalog: Map common 4xx/5xx to clear fixes; log request IDs.
  
  
• Observability: Track p95/p99 latency, error rate, and alert delivery success.
  
  
• Security: Keep keys in a secrets manager; rotate regularly.
  
  

Use Cases & Patterns

• Bot Builder (Headless): Route Bullish into candidate entries; confirm with /v2/resistance-support for risk and TM Grade for quality.
  
  
• Dashboard Builder (Product): Add a “Signals” module per token; color-code state and show history for credibility.
  
  
• Screener Maker (Lightweight Tools): Filter lists by Bullish state; sort by confidence/score; add alert toggles.
  
  
• Community/Discord: Post signal changes with links to token pages; throttle to avoid noise.
  
  
• Allocator/PM Tools: Track signal hit rates by sector/timeframe to inform position sizing (paper-trade first).
  
  

Next Steps

• Get API Key — create a key and start free.
  
  
• Run Hello-TM — confirm your first successful call.
  
  
• Clone a Template — deploy a bot, dashboard, or alerting tool today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale usage and unlock higher limits with API plans.
  
  

FAQs

1) What does the Trading Signals API return?
A JSON payload with the latest Bullish/Bearish call for a symbol, typically including a confidence/score and generated_at timestamp. You can render the latest call or a recent history for context.

2) Is it real-time? What about latency/SLOs?
Signals are designed for timely, programmatic use with predictable latency. For faster cycles, use /v2/hourly-trading-signals. Add caching and queues/webhooks to reduce round-trips.

3) Can I use the signals in a live trading bot?
Yes—many developers do. A common pattern is: Signals → candidate entry, Support/Resistance → stop/targets, Quantmetrics → risk sizing. Always backtest and paper-trade before going live.

4) How accurate are the signals?
Backtests are illustrative, not guarantees. Treat signals as one input in a broader framework with risk controls. Evaluate hit rates and drawdowns on your universe/timeframe.

5) Do you provide SDKs and examples?
You can integrate via REST using JavaScript and Python snippets above. The docs include quickstarts, Postman collections, and templates—start with Run Hello-TM.

6) Polling vs webhooks for alerts?
Dashboards often use cached polling. For bots/alerts, prefer webhooks or scheduled jobs and keep retries idempotent to avoid duplicate trades or messages.

7) Pricing, limits, and enterprise SLAs?
Begin free and scale as you grow. See API plans for allowances; enterprise SLAs and support are available.

‍

Hype is loud, but code is what lasts. The Technology Grade API helps you measure the engineering strength behind a token—scalability, innovation, and real code quality—so you can prioritize serious projects in your bots, dashboards, or research tools. In this guide, you’ll query the /v2/technology-grade endpoint, embed the score in your UI, and ship a feature that turns technical due diligence into a single actionable signal. Start by grabbing your key at Get API Key, Run Hello-TM to validate your first call, then Clone a Template to go live fast.

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches Technology Grade for any symbol via /v2/technology-grade.
  
  
• A copy-paste curl to smoke-test your key.
  
  
• A starter UX pattern: display the headline Technology Grade + component breakdown (scalability, innovation, code quality).
  
  
• Endpoints to add next for full context: /v2/fundamental-grade (business quality), /v2/tm-grade (technicals/sentiment/momentum), /v2/trading-signals (timing), /v2/quantmetrics (risk/return).

Why This Matters

Separate hype from substance. Whitepapers and roadmaps are cheap; shipped code, throughput, and upgrade cadence are not. The Technology Grade API rolls engineering reality into a comparable score so you can rank ecosystems, filter listings, and surface projects with staying power.

Faster diligence, clearer decisions. For bot builders, Technology Grade is an upstream filter that keeps low-quality projects out of your universe. For dashboard builders, it adds credibility—users can see why a project ranks well. And for screeners, it’s a one-score signal that’s easy to sort, badge, and alert on with low latency.

Where to Find 

For the Technology Grade information, check the top right of the API Reference. You'll find the cURL request to connect effortlessly.

‍

‍

👉 Next: Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• Investor/Due-Diligence Token Page: Show a Technology Grade dial with component bars and a “What improved?” changelog snippet.
  
  
• Screener/Leaderboard: Rank by Technology Grade; add sector and market-cap filters; badge “Rising Tech” week-over-week.
  
  
• Bot Universe Filter: Require a minimum Technology Grade before a token is eligible for strategies; combine with signals for entries/exits.
  
  

Kick off from quickstarts in the docs—fork a dashboard or screener and deploy. Validate your environment with Run Hello-TM, then scale usage. When you need higher limits and SLAs, compare API plans.

How It Works (Under the Hood)

Technology Grade synthesizes engineering-centric evidence—such as throughput/scalability, rate of innovation (feature velocity, upgrade cadence), and code quality (maintainability, robustness cues)—into a normalized score and grade (e.g., Strong / Average / Weak). It’s designed to be comparable across projects and stable enough to inform filters, tiers, and badges.

At query time, you request /v2/technology-grade?symbol=<ASSET>. The response includes the headline score and component scores you can display in bars or a radar chart. For dashboards with many assets, use batched calls and short-TTL caching. If you push upgrade/downgrade alerts, queue notifications or use webhooks to avoid bursty polling.

Production Checklist

• Rate limits: Understand your tier’s caps; add client-side throttling.
  
  
• Retries & backoff: Use exponential backoff with jitter; handle 429/5xx gracefully.
  
  
• Idempotency: Ensure retried fetches don’t double-trigger downstream actions.
  
  
• Caching: Memory/Redis/KV with short TTLs; pre-warm popular symbols; ETag if available.
  
  
• Webhooks & jobs: Prefer queued jobs or webhooks for grade-change alerts.
  
  
• Pagination/Bulk: Batch symbols; parallelize with care; respect limits.
  
  
• Error catalog: Map common 4xx/5xx to remediation steps; log request IDs.
  
  
• Observability: Track p95/p99 latency and error rates per endpoint; alert on drift.
  
  
• Security: Keep API keys in secrets managers; rotate and scope keys.
  
  

Use Cases & Patterns

• Bot Builder (Headless): Apply a Technology Grade threshold to define your tradable universe; then confirm timing with /v2/trading-signals and place risk with /v2/resistance-support.
  
  
• Dashboard Builder (Product): Add a “Tech” tab on token pages with the headline grade, components, and a short narrative for users (“What’s driving this score?”).
  
  
• Screener Maker (Lightweight Tools): Ship a Top-N by Technology Grade leaderboard; add badges for “Rising Tech” based on week-over-week deltas.
  
  
• Listing/Research Teams: Gate listings or research coverage using Technology Grade plus Fundamental Grade for balanced quality screens.
  
  
• Enterprise Due Diligence: Export grades nightly to internal systems; alert on downgrades crossing critical thresholds.
  
  

Next Steps

• Get API Key — create a key and start free.
  
  
• Run Hello-TM — confirm your first successful call.
  
  
• Clone a Template — deploy a screener or token page today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale usage and unlock higher limits with API plans.
  
  

FAQs

1) What does the Technology Grade API return?
A JSON payload with an overall score/grade plus component scores (e.g., scalability, innovation, code quality) and timestamps. Use the overall score for ranking and components for explanation.

2) Is this real-time, and what about latency/SLOs?
The endpoint is engineered for predictable latency suitable for dashboards and filters. For frequent refresh or alerts, combine short-TTL caching with queued jobs or webhooks to minimize round-trips.

3) How should I combine Technology Grade with other signals?
A common pattern: Technology Grade (engineering quality) + Fundamental Grade (business quality) + TM Grade (technicals/sentiment) + Trading Signals (timing) + Support/Resistance (risk placement).

4) How “accurate” is Technology Grade?
It’s an opinionated synthesis of engineering evidence, not financial advice. Use it as part of a diversified framework; validate with your own backtests and risk controls.

5) Do you provide SDKs or examples?
You can integrate via REST (JS/Python examples above). The docs include quickstarts, Postman collections, and templates—start by Run Hello-TM.

6) Polling vs webhooks for grade changes?
For UI pages, cached polling is fine. For alerts (upgrades/downgrades), prefer webhooks or scheduled jobs to avoid spiky traffic and rate-limit issues.

7) Pricing, limits, and enterprise SLAs?
Begin free and scale up as needed. See API plans for allowances; enterprise SLAs and support are available.

‍

Most traders chase price action; Fundamental Grade API helps you see the business behind the token—community traction, tokenomics design, exchange presence, VC signals, and DeFi health—consolidated into one score you can query in code. In a few minutes, you’ll fetch Fundamental Grade, render it in your product, and ship a due-diligence UX that drives trust. Start by grabbing your key at the Get API Key page, Run Hello-TM to verify your first call, then Clone a Template to go live fast.

‍

What You’ll Build in 2 Minutes

• A minimal script to fetch Fundamental Grade from /v2/fundamental-grade for any symbol (e.g., BTC).
  
  
• Optional curl to smoke-test your key in seconds.
  
  
• A drop-in pattern to display the grade + key drivers in dashboards, screeners, and research tools.
  
  
• Endpoints to consider next: /v2/tm-grade (technical/sentiment/momentum), /v2/price-prediction (scenario planning), /v2/resistance-support (risk levels), /v2/quantmetrics (risk/return stats).

Why This Matters

Beyond price, toward quality. Markets are noisy—hype rises and fades. Fundamental Grade consolidates hard-to-track signals (community growth, token distribution, liquidity venues, investor quality, DeFi integrations) into a clear, comparable score. You get a fast “is this worth time and capital?” answer for screening, allocation, and monitoring.

Build trust into your product. Whether you run an investor terminal, exchange research tab, or a portfolio tool, Fundamental Grade lets users justify positions. Pair it with TM Grade or Quantmetrics for a balanced picture: what to buy (fundamentals) and when to act (signals/levels).

Where to Find 

The Fundamental Grade is easily accessible in the top right of the API Reference. Grab the cURL request for seamless access!

👉 Ready to build? Get API Key • Run Hello-TM • Clone a Template

Live Demo & Templates

• Due-Diligence Token Page: Show Fundamental Grade with a component breakdown (community, tokenomics, exchange presence, VC, DeFi).
  
  
• Screener/Ranker: Sort by Fundamental Grade, add market-cap bands, and flag “rising fundamentals” week-over-week.
  
  
• Allocation Dashboard: Combine Fundamental Grade with TM Grade and Quantmetrics for resilient portfolio construction.
  
  

Kick off from our quickstarts—fork a dashboard or screener template, plug your key, and deploy. If you’re new here, Run Hello-TM first to confirm your environment, then scale into product features. When you outgrow the free tier, compare API plans.

How It Works (Under the Hood)

Fundamental Grade aggregates multiple project-quality signals into a normalized score and label (e.g., Strong / Average / Weak). Typical sub-signals include:

• Community: momentum across channels (dev activity/user traction signals where applicable).
  
  
• Tokenomics: supply schedule, distribution, unlock dynamics, incentives.
  
  
• Exchange Presence: venue coverage, depth/liquidity proxies.
  
  
• VC/Investor Signals: quality/durability of backing and ecosystem support.
  
  
• DeFi Health: integrations, TVL context, composability footprint.
  
  

At query time, you call /v2/fundamental-grade with a symbol; responses include the overall score plus component scores you can visualize. For dashboards with many assets, batch fetches and short-TTL caching keep pages responsive. If you push alerts (e.g., “Fundamental Grade upgraded”), prefer webhooks or queued jobs to avoid hammering the API.

Production Checklist

• Rate limits: Know plan caps; add client throttling and request queues.
  
  
• Retries/backoff: Exponential backoff + jitter; surface actionable error messages.
  
  
• Idempotency: Prevent duplicate downstream actions on retried calls.
  
  
• Caching: Use memory/Redis/KV with short TTLs; pre-warm popular symbols.
  
  
• Webhooks & jobs: For alerts, use signed webhooks or scheduled jobs; log delivery outcomes.
  
  
• Pagination/Bulk: When covering many tokens, paginate or process in batches.
  
  
• Error catalog: Map 4xx/5xx to user-visible fixes; log request IDs.
  
  
• Observability: Track p95/p99 and error rate per endpoint; alert on spikes.
  
  
• Security: Keep API keys in secrets managers; rotate regularly.
  
  

Use Cases & Patterns

• Screener Maker: Rank tokens by Fundamental Grade, filter by market cap/sector, and add “rising fundamentals” badges for discovery.
  
  
• Dashboard Builder: On each token page, show the headline grade with a component chart; link to methodology for transparency.
  
  
• Research & PM Tools: Flag downgrades/upgrades to prompt re-evaluation; attach notes to component changes (e.g., DeFi health drop).
  
  
• Allocator / Risk: Require a minimum Fundamental Grade before inclusion; rebalance only when grade crosses thresholds.
  
  
• Community/Discord: Post weekly upgrades as digest messages with links back to your app.
  
  

Next Steps

• Get API Key — generate a key and start free.
  
  
• Run Hello-TM — verify your first successful call.
  
  
• Clone a Template — deploy a screener or token page today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: Scale confidently with API plans.
  
  

FAQs

1) What does the Fundamental Grade API return?
A JSON payload with the overall score/grade plus component scores (e.g., community, tokenomics, exchange presence, VC backing, DeFi health) and timestamps. Use the overall grade for ranking and component scores for explanations.

2) How fast is the endpoint? Do you publish SLOs?
The API is engineered for predictable latency. For high-traffic dashboards, add short-TTL caching and batch requests; for alerts, use jobs/webhooks to minimize round-trips.

3) Can I combine Fundamental Grade with TM Grade or signals?
Yes. A common pattern is Fundamental Grade for quality filter + TM Grade for technical/sentiment context + Trading Signals for timing and Support/Resistance for risk placement.

4) How “accurate” is the grade?
It’s an opinionated synthesis of multiple inputs—not financial advice. Historical studies can inform usage, but past performance doesn’t guarantee future results. Always layer risk management and testing.

5) Do you offer SDKs and examples?
You can use REST directly (see JS/Python above). The docs include quickstarts, Postman, and ready-to-clone templates—start with Run Hello-TM.

6) Polling vs webhooks for fundamentals updates?
For UI pages, cached polling works well. For event-style notifications (upgrades/downgrades), prefer webhooks or scheduled jobs to avoid spiky traffic.

7) What about pricing, limits, and enterprise SLAs?
Begin free and scale as you grow. See API plans for allowances; enterprise SLAs and support are available—contact us.

‍

Cluttered charts and whipsaw price action make it hard to act with conviction. The TM Grade API turns that noise into a single, opinionated signal you can build on—ideal for trading bots, dashboards, and research tools. In this guide, you’ll pull TM Grade in code, see how it powers products, and ship something useful in minutes. Start with the Get API Key, then Run Hello-TM in the docs and Clone a Template to go live fast.

‍

What You’ll Build in 2 Minutes

• A minimal script that fetches TM Grade from /v2/tm-grade for a given token (e.g., BTC).
  
  
• An optional curl call to test the endpoint instantly.
  
  
• A path to production using a copy-ready template (bot, dashboard, or screener).
  
  
• (Mentioned endpoints you can add next: /v2/trading-signals, /v2/price-prediction, /v2/resistance-support.)

Why This Matters

One score, clear decision. TM Grade distills technicals, sentiment, and momentum into a single, interpretable value from Strong Sell → Strong Buy. Instead of juggling indicators, you get an opinionated, trade-ready signal you can rank, alert on, and route into strategies.

Built for builders. Developers integrate TM Grade to filter universes, power dashboards, or trigger bots—with predictable performance and a schema designed for programmatic use. Pair it with webhooks and caching to slash latency and polling costs.

Where to Find 

In the top right of the API Reference you can find the curl request for your desired language. This is what you can use to access the TM Grade endpoint. 

‍

👉 Ready to go further? Get API Key • Run Hello-TM 

Live Demo & Templates

• Trading Bot Starter: Use TM Grade to filter a trade universe and gate entries with your own risk rules.
  
  
• Dashboard Token Page: Show TM Grade alongside price, S/R levels, and signals for instant context.
  
  
• Screener/Leaderboard: Rank tokens by TM Grade and highlight movers.
  
  

You can start from our quickstarts in the docs—fork, plug your key, and deploy in minutes. Run Hello-TM to see the first call succeed, then scale into a bot or dashboard. When you’re ready for higher limits, compare API plans.

How It Works (Under the Hood)

TM Grade blends multiple evidence streams—technical momentum, market structure, sentiment, and other model inputs—into a single normalized score (e.g., 0–100) and a label (Strong Sell to Strong Buy). This opinionated synthesis is what separates TM Grade from raw market data: it’s designed to be actionable.

Polling vs webhooks. For screens and dashboards, lightweight polling (or cached fetches) is fine. For trading agents and alerting, use webhooks or short polling with backoff and caching to cut latency and call volume. Combine TM Grade with endpoints like /v2/trading-signals for timing or /v2/resistance-support for risk placement.

Production Checklist

• Rate limits: Know your plan caps; add client-side throttling.
  
  
• Retries/backoff: Exponential backoff + jitter; avoid thundering herd.
  
  
• Idempotency: Ensure repeated calls don’t double-execute downstream actions.
  
  
• Caching: Short-TTL cache for reads (memory/Redis/KV); ETag if available.
  
  
• Webhooks: Use signatures/secret validation; queue and retry on failure.
  
  
• Pagination/Bulk: If fetching many symbols, batch requests with pagination.
  
  
• Error catalog: Map 4xx/5xx to user-visible fixes; log status, payload, and request ID.
  
  
• Observability: Track p95/p99 latency and error rate per endpoint; alert on spikes.
  
  

Use Cases & Patterns

• Bot Builder (Headless): Filter tradable universes to Strong Buy/Buy, then confirm with timing from /v2/trading-signals before placing orders.
  
  
• Dashboard Builder (Product): Show TM Grade on token pages with badges, color states, and last-updated timestamps; add S/R lines for context.
  
  
• Screener Maker (Lightweight Tools): Build a Top-N by TM Grade list with sector filters; cache results and add one-click alerts.
  
  
• Research/Allocation: Surface grade trends (rising/falling) to inform rebalances and risk budgets.
  
  
• Community/Discord: Post grade changes to channels; rate-limit announcements and link to token detail views.

Next Steps

• Get API Key — start free and generate a key in seconds.
  
  
• Run Hello-TM — verify your first successful call.
  
  
• Clone a Template — ship a bot, dashboard, or screener today.
  
  
• Watch the demo: VIDEO_URL_HERE
  
  
• Compare plans: When you’re ready to scale, review API plans.
  
  

FAQs

1) What does the TM Grade API return?
A JSON payload with fields like symbol, score (e.g., 0–100), and a categorical grade from Strong Sell to Strong Buy, designed for programmatic ranking, filtering, and display.

2) How fast is it? Do you have latency/SLOs?
TM endpoints are engineered for reliability with predictable latency. For mission-critical bots, add short-TTL caching and webhooks to minimize round-trips and jitter.

3) Can I use TM Grade in trading bots?
Yes. Many developers use TM Grade to pre-filter tokens and pair it with /v2/trading-signals for entries/exits. Always backtest and paper-trade before going live.

4) How accurate is TM Grade?
TM Grade is an opinionated model synthesizing multiple inputs. Backtests are illustrative—not guarantees. Use it as one component in a diversified strategy with risk controls.

5) Do you have SDKs and examples?
Yes—JavaScript and Python examples above, plus quickstarts and templates in the docs: Run Hello-TM.

6) Polling vs webhooks—what should I pick?
Dashboards: cache + light polling. Bots/alerts: prefer webhooks (or event-driven flows) to reduce latency and API usage.

7) Pricing, limits, and enterprise SLAs?
You can start free and scale up as you grow. See API plans for rate limits and tiers. Enterprise options and SLAs are available—contact us.

‍

If you’ve been waiting for a simple, rules-based way to own the TM Global 100—without micromanaging tokens—this hub is for you. TM Global 100 is a rules-based crypto index that holds the top 100 assets in bull markets and moves to stablecoins in bear markets, with weekly rebalancing and transparent holdings/transaction logs you can verify at any time. It’s designed for hands-off allocators who want disciplined exposure and for active traders who want a core that adapts to regimes—without guesswork or endless rebalancing. Below you’ll find how it works, who it’s for, and exactly how to join the waitlist so you’re first in line when trading opens.

→ Join the waitlist to be first to trade TM Global 100.

TL;DR (snippet)

• What it is: A rules-based index that holds the top-100 in bull markets and exits to stablecoins in bear markets.
  
  
• Why it matters: Weekly rebalances + transparent holdings and transaction logs.
  
  
• Who it’s for: Hands-off allocators and active traders who want a disciplined core.
  
  
• Next step: Join the waitlist to be first to trade TM Global 100.
  
  

Why Indices Matter in October 2025

Search intent right now: investors want credible, rules-based crypto exposure that can participate in upside while reducing drawdown pain. A crypto index is a basket of assets selected and maintained by rules—so you avoid one-off bets and constant manual rebalancing.

With liquidity rotating quickly across sectors, weekly rebalancing helps maintain alignment with current market-cap leaders, while regime switching provides a disciplined, pre-defined response to bearish conditions. The result is a clear, consistent process that removes emotional decision-making and operational drag.

Definition (snippet-friendly): A crypto index is a rules-based basket of digital assets that’s constructed, weighted, and rebalanced on a set schedule.

How the TM Global 100 Index Works (Plain English)

• Regime switching:
  
  
  
  • Bullish: Hold the top-100 crypto assets by market cap.
    
    
  • Bearish: Exit all positions into stablecoins and wait for a new bullish signal.
    
    
• Weekly rebalancing: Reflects updated rankings and weights across the market-cap universe.
  
  
• Transparency: Strategy modal shows methodology and thresholds; Gauge → Holdings Treemap → Transactions Log make every change visible.
  
  
• What you’ll see on launch: Price tile, gauge (“rebalances weekly”), 100 tokens, one-click Buy Index flow, and a 90-second checkout via embedded wallet.
  
  

Soft CTA: See the strategy and rules.

Benefits at a Glance (Why This Beats DIY)

• Time saved: No more manual coin-picking, sizing, and calendar rebalances.
  
  
• Lower execution drag: One click vs. dozens of individual orders that can add slippage.
  
  
• Stay current: Weekly rebalances help you capture market-cap changes without constant monitoring.
  
  
• Discipline in drawdowns: Automatic switch to stablecoins removes panic decisions.
  
  
• Radical visibility: Holdings treemap, table, and transactions log show what you own and what changed—every week.
  
  
• Operational simplicity: Embedded wallet and a unified dashboard; no juggling chains and exchanges.
  
  

Step-by-Step: How to Get Early Access (Waitlist)

1. Open the Indices Hub: Head to the Token Metrics Indices hub.
   
   
2. Choose TM Global 100: Open the index page and review the Gauge → Strategy → Holdings.
   
   
3. Join the Waitlist: Add your email to be notified the moment trading opens.
   
   
4. (Optional) Connect Wallet: Pre-connect your wallet for a faster launch-day checkout.
   
   
5. Launch-Day Flow (~90 seconds): Tap Buy Index, review fees/slippage, confirm, and see your position in My Indices.
   
   
6. Track Rebalances: After each weekly rebalance or regime change, check the Transactions Log for updates.
   
   

→ Join the waitlist to be first to trade TM Global 100.

Decision Guide: Is This Right for You?

• Hands-Off Allocator: Want broad exposure without micromanaging? Yes—rules-based + weekly rebalances.
  
  
• Active Trader: Need a core that sits in stables during bears while you hunt edges elsewhere? Fits.
  
  
• TM Member/Prospect: Already trust TM research? This is the rules-based version of “own the market.”
  
  
• Risk-Aware Newcomer: Prefer a clear framework over vibes? Methodology is visible and auditable.
  
  
• DIY Basket Builder: Tired of missed rebalances and slippage? One click can reduce execution drag.
  
  
• Data-First Analyst: Want to verify? See the holdings, weights, and transaction history anytime.

‍

FAQs

1) What is a TM Global 100 index?
It’s a rules-based crypto index that holds the top 100 assets by market cap in bullish regimes and moves to stablecoins in bearish regimes. It rebalances weekly and shows transparent holdings and transactions.

2) How often does the index rebalance?
Weekly, with additional full-portfolio switches when the market regime changes.

3) What triggers the move to stablecoins?
A proprietary market signal. When bearish, the index exits all token positions into stablecoins and waits for a bullish re-entry signal.

4) Can I fund with USDC or fiat?
At launch, funding and settlement options surface based on the embedded wallet and supported chains. USDC payouts are supported for selling; additional entry options may be introduced later.

5) Is the wallet custodial?
No. The Embedded Wallet is self-custodial—you control your funds while using a streamlined, on-chain checkout.

6) How are fees shown?
Before you confirm, the Buy flow shows estimated gas, platform fee, maximum slippage, and the minimum expected value.

7) How do I join the waitlist?
Go to the Token Metrics Indices hub or the TM Global 100 strategy page and submit your email. We’ll notify you the moment trading opens.

Security, Risk & Transparency

• Self-custody: Embedded smart wallet; you hold the keys.
  
  
• 2FA & session hygiene: Use strong auth practices for your TM account.
  
  
• Fee clarity: Gas, platform fee, and slippage are displayed before you confirm.
  
  
• Auditability: Holdings, treemap, and transactions log are always visible.
  
  
• Model limits: Regime logic can be wrong, and markets can gap; rules reduce discretion—not risk.
  
  
• Regional availability: Product surfaces may vary by region as we expand.
  
  

Crypto is volatile and can lose value. Past performance is not indicative of future results. This article is for research/education, not financial advice.

Conclusion + Related Reads

If you want a disciplined, rules-based core that adapts to market regimes, TM Global 100 is built for you. Weekly rebalances, transparent holdings, and one-click buy remove operational friction so you can focus on your strategy.

→ Join the waitlist to be first to trade TM Global 100.

Related Reads

• TM Global 100 strategy
  
  
• Token Metrics Indices hub
  
  
• Best Cryptocurrency Exchanges 2025 (coming to the Token Metrics blog)
  
  

‍