What is Balchemy?

Choose a goal first. Use Run an agent for the operator path, or Integrate an agent for a safe read-only SDK path.

Balchemy is an operations product for autonomous Solana/Base trading agents, built on a two-layer wallet model: your main wallet stays in your custody (sign-in is signature-only), while each agent trades from a separate, platform-managed wallet that you fund and your rules cap. See Security for the full custody model.

The active product model is:

• Hub — create, fund, authorize, monitor, and improve an always-on trading agent.
• Explorer — browse verified public agents and public metadata.

Studio is retired as a separate bot workspace. Studio-era routes and docs can remain temporarily for migration or compatibility, but new public product flows should start from Hub.

Balchemy has no plan, tier, subscription, Stripe billing, or enterprise access model. Every user gets the same standard product access. Revenue comes from the global swap-fee model on executed swaps.

Choose the right surface

Hub

Hub is the operating surface for autonomous trading agents. From Hub you can:

• create or resume a Hub agent,
• write natural-language rules,
• inspect runtime state and degraded evidence,
• monitor positions, trades, activity, and logs,
• configure Signal Sources,
• manage scoped MCP/API access,
• connect Solana/Base wallets through authorized product flows.

Hub is not a bot builder. It should not force operators through heavy strategy forms before an agent can exist.

Explorer

Explorer is a public discovery surface. Use it to browse public agents, profiles, capabilities, and strategy metadata. Explorer supports discovery and trust, but it is not the operating workspace.

How trading works

Every trading path follows the same safety-oriented shape:

1. Intent — a user instruction, rule, runtime event, or MCP/API request arrives.
2. Plan — Balchemy resolves the requested action and available facts.
3. Policy — scopes, risk settings, approval rules, and safety checks run before execution.
4. Execute — the trading engine routes supported swaps through the chain-specific execution path.
5. Verify — the result is reconciled against order and position state.
6. Notify — Hub activity, logs, or user-facing output receives the outcome.

Submission is not completion. A trade is complete only when reconciliation proves the terminal state.

Supported chain focus

Balchemy focuses on:

Do not assume every EVM chain, token, or route is available unless the current trading engine and frontend prove it.

Fees and attribution

Balchemy charges a global swap fee on executed swaps. There are no monthly subscription fees or access tiers.

Referral attribution and Signal Source attribution are separate product systems. Do not treat either as guaranteed payout rails unless the product exposes and verifies that settlement flow.

Where to start

I want to create or resume an agent. Start with Hub Overview, then use Hub sign-in when you are ready to operate.

I want walletless onboarding. Read Agent Onboarding.

I want to understand MCP. Read MCP Integration. Hub agent MCP/API access is managed from Hub Agents & Keys.

I want to understand Telegram or Discord. Read Signal Sources. Telegram and Discord are source/verification surfaces, not Hub chat bots.

You are done when

You can explain the difference between identity sign-in, agent funding, runtime mode, approval, submission, and reconciliation—and you have chosen either the operator or integration path above.

---

Related pages

• Hub Overview
• Agent Onboarding
• Rules and Runtime
• Signal Sources
• Revenue
• MCP Integration
• Trading Fees