Tooling that makes working with the OpenDunes API faster and easier to debug.
These tools and techniques reduce friction during development — from typed completions in your editor to request-level tracing in the dashboard.
The openai SDK ships full TypeScript types. Even if you write Python or Go, your IDE autocompletes request parameters, response fields, and error shapes — catching mistakes before they hit the wire.
X-Request-Id#Every response from the OpenDunes API includes an X-Request-Id header containing a UUID v7 trace identifier. Log it with every request so you can look up the exact call in your dashboard if something goes wrong.
Note. When contacting support about a failed request, always include the
X-Request-Id. It's the fastest way to locate the call server-side.
Your dashboard gives you a live view of:
Use the trace ID from X-Request-Id to jump directly to a specific request in the log.
Keep secrets out of source code. The one variable you always need:
For local development, a .env file works well — just make sure it's in .gitignore.
Two headers let you monitor spend inline without extra API calls:
| Header | Value |
|---|---|
X-Balance-Available | Remaining balance in micro-DA |
X-RateLimit-Remaining-RPM | Requests left in the current minute |
X-RateLimit-Reset | Unix timestamp when the limit resets |
Point at http://localhost:8000/v1 when running the stack locally. Everything — auth, billing, models — behaves identically to production.