Skip to main content
EchoZero uses a few core objects. This page defines them and how they relate.

Entity model

ObjectWhat it is
DeveloperRegistered builder with API keys, Stripe Connect, and payout rails
AgentMarketplace listing that receives signals and fans out to subscribers
StrategyAutomated trading bot configuration (risk rules, conditions). In API copy, strategy and trading bot refer to the same resource (/api/v1/strategies)
SignalOne inbound trade intent (TradeSignal row) from webhook, WebSocket, Telegram, Discord, or API
SubscriberEnd user with an active paid or free subscription to your agent
Position / tradeExecuted buy/sell row tied to a subscriber wallet
Success feePercent of profitable trade notional charged to subscribers on the success-fee model

Agent vs strategy

  • Agent = marketplace persona + signal ingress + subscriber graph.
  • Strategy = bot logic for automated trading on EchoZero (conditions, risk management, pause/play).
Signal-group and webhook agents focus on ingress + fan-out. Strategies are optional automation layers subscribers can also run.

Glossary

TermMeaning
positionRefsignalId or entry idempotencyKey for lifecycle events (sell, amend, cancel)
idempotencyKeyStable dedupe key; always send on every signal for replay protection
betaStatuspending-reviewbetapublic (or rejected)
signalSourceKindwebhook (HTTP ingress) or signal_group (Telegram/Discord)
ez_live_ / ezs_API key id / secret (REST HMAC)
ezw_Per-agent inbound webhook signing secret
Virtual modePaper trading with simulated wallet balances
MCP sessionmcp-session-id header bound to the credential used at initialize
REST HMACx-signature + x-timestamp (ms, method, path, body)
Inbound HMACX-EZ-Signature + X-EZ-Timestamp (seconds, canonical JSON)
Outbound HMACx-echozero-signature on signal.execution callbacks

Credential cheat sheet

See the full Authentication guide for when to use each credential type.