Skip to main content
External developers test against the production API host - there is no separate public staging environment and you do not need access to EchoZero source code. Base URL: https://mcp.echozero.app/api

1. Create a developer account and API key

  1. Sign in at devportal.echozero.app.
  2. Register as a developer and create an API key.
  3. Export the key and its secret locally:
Every API-key request must be signed with the secret, so the examples below use the ez helper:
See API keys and HMAC for how signing works.

2. Dry-run sandbox endpoints

The Sandbox API group provides dry-run simulators - they validate ownership and return simulated results with no real execution.

Simulate a trade for your agent

Simulate signal parsing for an agent

List sandbox signal history

The response is data.items plus data.pagination. The spec lists no paging query parameters for this route, so do not rely on page or limit. See the Sandbox tag in the API Reference sidebar for full request/response schemas.

3. Virtual wallet (paper trading)

Switch to virtual wallet mode and add simulated funds before testing buy/sell flows:
Virtual trades use simulated balances - no on-chain execution. amountInSol is deprecated; use amountInUsdc.

4. Portal demo signals

To record a demo signal row for an agent (isolated from live subscriber execution), use the route below. It is not in the public API spec, so its body is undocumented. The developerAgentId field name here is unconfirmed (other material may call it agentId). Treat this call as unsupported and prefer the sandbox endpoints above:
Demo signals appear in developer signal history but do not trigger the live trade bridge.

5. Test inbound webhook signing

Create a webhook agent (signalSourceKind: webhook, with an agentVenue) in the Dev Portal or through the API. Save the inboundWebhookSigningSecretReveal (ezw_...) shown once at creation. Inbound signals use the agent’s ezw_ secret, a timestamp in seconds, and canonical JSON (keys sorted alphabetically). This helper does all three:
Write numbers in plain form (100, 100.5), not 1.0, 100.50 or 1E+3. jq keeps numbers as typed, but the server re-serialises them the JavaScript way, so the signature would not match. Send only documented fields too: the server drops unknown top-level fields before it verifies the signature, and jq would sign them. If you need arbitrary numbers, use an SDK.
Use virtual wallet mode so execution uses simulated balances. Full signing details are in Webhook security.

6. Dev Portal UI

Many flows (agent setup, signal preview, subscriber analytics) can also be exercised from the Dev Portal before you wire up production bots.
Use a dedicated test agent with no real subscribers while iterating. When you are ready for live execution, switch to production webhook or structured signal ingestion paths documented in the Signal envelope and Webhook security guides.