FAQ

FAQ

What AI runs the bot?

Anthropic Claude Opus 4.8 is the decision engine. Every buy gate, every exit trigger, every self-grade after a sell runs through it. We chose Opus 4.8 specifically for its long-context reasoning — it can hold the full position history + multi-source live market data + all our rules in one shot when deciding what to do next.

How much does it cost?

Nothing. The signal feed is free. We may sell an operator-dashboard product in the future, but the signal feed itself is and will remain free.

How do I get a key?

Submit your email at /pricing. We email an API key back within ~60 seconds. No payment, no card, no auto-renew. One key per email at a time.

Why do keys expire after 30 days?

Operational rotation. We cap active keys at 50 to keep the feed sustainable. 30-day expiration keeps slots flowing so new requests can be served without forcing manual revocations. After your key expires, claim another (still free) if a slot is open.

What if all 50 keys are claimed?

You can join the waitlist or DM us on Telegram. As current keys expire (30 days) or get revoked for non-use (14 days of zero MCP calls), slots open up and queued requests are auto-issued in order.

Why is there a 50-key cap?

To keep the service sustainable while the bot is in beta. The signal-distribution infrastructure has a real per-key cost; uncapped issuance would force us to charge. Capping at 50 keeps it free for the active subscribers who actually use it.

What if I stop using my key?

A daily cron revokes keys with zero MCP calls in the prior 14 days. This frees up your slot for someone who will actually use the feed. If you go on vacation and stop briefly, no problem — just re-claim when you come back if a slot is open.

How do signals arrive?

Via the Model Context Protocol (MCP). Configure your MCP client (Claude Code, Cursor, etc.) with the API key — see /docs.

What is an MCP client?

A program that consumes the MCP protocol. The most common are AI coding assistants like Claude Code and Cursor. We supply setup snippets for both at /docs.

How do I automate trades on my own VPS?

See the full setup guide at /guide — it walks through provisioning a Frankfurt VPS, creating a dedicated Solana trading wallet, installing the Node.js executor, choosing a position-sizing mode (mirror our entries at a fraction, fixed size, or % of wallet), risk controls, and running as a systemd service. You sign your own swaps; we never touch your funds.

Can I add an AI layer to filter signals?

Yes — the /guide#part-13 section walks through wiring Nous Hermes (open-source LLM via OpenRouter or self-hosted via Ollama) on top of the executor. Hermes votes BUY or SKIP on each incoming signal and can scale your position size by its confidence score. Optional and additive — your DAILY_LOSS_CAP, MAX_POSITION_SOL and MIN_POSITION_SOL caps still apply on top.

Is there a paid operator dashboard?

Not yet — but planned. We have an internal trading dashboard (live positions, OH risk-score breakdown, live review reasoning, charts) that we use ourselves. If you trade manually and want early access, DM us on Telegram and we can chat. Future paid product depending on bot success — the signal feed itself stays free regardless.

Do you ever touch my funds?

Never. Signals are one-way push from our backend to your MCP client. You execute trades from your own wallet. We have no key access, no swap-on-behalf, no custody.

Slippage?

Your concern — the signal contains the bot entry price; you size and slip on your own swap rail (we suggest Jupiter swap from your wallet).