Review candidate decisions
Inspect the signal, matching rule, evidence, and policy result before live execution is enabled.
Autonomous trading, bounded by design
Balchemy watches Solana and Base markets, explains what it would do, and enters execution only inside the rules, funded limits, runtime mode, and approvals you set.
Shadow firstObserve decisions before execution is armed.
Funded boundarySign-in does not grant spending authority.
Named statesHeld, submitted, and reconciled stay distinct.
Illustrative shadow decision
SOL volatility moved outside the observation band.
Public market signal · illustrative sample
Observe in shadow when price evidence is delayed.
Plain-language rule matched
One price source is delayed; confidence is reduced.
Degraded evidence remains visible
Hold the action in shadow mode.
Policy prevents submission
Not submitted.
No wallet or chain action started
No funds moved.
The trace remains inspectable
Evidence before commitment
Trust comes from named controls and honest limits, not another badge.
Connection proves identity. It does not grant spending.
Supported checks show their source, freshness, and limits.
Unavailable evidence is not rewritten as a safe result.
Inspect the agent runtime.
Runtime and source health after sign-in.
How control works
Balchemy separates observation, decision, authorization, execution, and reconciliation so each commitment can be understood before the next one begins.
Read how runtime control worksWrite the rule in plain language. Limits and approval intent stay visible beside the behavior they qualify.
Shadow mode records what the agent sees and proposes without allowing execution.
Runtime mode, funded wallet boundary, scope, risk evidence, and approval policy determine whether an action can progress.
Held, blocked, submitted, executed, and reconciled are named separately. Submission is never presented as completion.
Built for the operator
The product proof is not a performance claim. It is the ability to see why an action progressed, stopped, or still needs attention.
Inspect the signal, matching rule, evidence, and policy result before live execution is enabled.
Keep observing while delayed or unavailable sources prevent a confident live decision.
Separate identity sign-in from the agent wallet, funding boundary, scopes, and live authorization.
Use durable order and transaction references to follow an action through reconciliation.
Choose the right entry
Operator sign-in and builder onboarding are different jobs. Each has a short path and a different commitment.
For traders and operators
Connect an identity wallet, create or resume an agent, write a rule, and observe the first decision before live execution is armed.
For developers and external agents
Choose CLI, SDK, or MCP, make one safe read-only call, verify the result, then add privileged capability intentionally.
npx balchemyCopy the canonical CLI command.
Before money moves
Inspect before you connect