Plan your first research workflow

Confirm availability

Check the capabilities enabled for your project. Preview documentation does not prove that access or an integration is active.

Inspect the result

Keep the response evidence, limitations and receipt. Uncertain consumption should be reconciled before repeating a request.

Keep execution separate

Research, simulation and testnet actions have distinct requirements. Any eligible testnet action requires a specific wallet signature and subsequent reconciliation. Production trading is not offered by this guide.

A bounded integration workflow

Agree the workflow and permitted inputs before integrating. This public outline describes the user journey; implementation material is shared through authorized access.

1. Confirm the workflow, permitted inputs and enabled project capabilities.
2. Review the usage quote before requesting analysis.
3. Inspect the result, its evidence and any unavailable information.
4. Keep the receipt; reconcile uncertain requests before repeating them.
5. Review simulation separately. Testnet execution requires an eligible
   environment and a fresh wallet signature for the specific order.

SDK setup and interface details are supplied through the authorized workspace.
This outline is not executable code and does not activate a service.

If a request times out or returns an uncertain receipt, keep its request ID and use GET /v1/requests/{request_id}. Do not automatically repeat a billable POST.

Check the service before integration

Check enabled capabilities in the authorized workspace before use. Public documentation does not activate a service. Simulation and testnet prototypes do not establish live trading availability.