REST API reference
Use the same Ultron tools through authenticated HTTP calls, with structured schemas, scopes and errors.
Call a tool
POST /api/tools/{tool_name} accepts the JSON argument object shown in the tool reference. Authenticate with a scoped Ultron Bearer key. Successful REST responses wrap the tool output in result. Check HTTP status and error fields before using a value.
curl https://ultrontrading.app/api/tools/network_status \
-H "Authorization: Bearer $ULTRON_ACCESS_KEY" \
-H "Content-Type: application/json" \
--data '{}'Machine-readable contracts
/openapi.json exposes the current tool paths, input schemas and required scope. MCP clients can list tools and resources at /mcp. The schemas are generated from the same registry used to validate calls, so they should be preferred over copied examples when a tool changes.
Errors and retries
Errors contain a code and a concise message; REST errors include a request ID. Rate-limited requests use HTTP429 with Retry-After where available. Upstream data failure remains unavailable rather than a fabricated quote.
GET-like reads can be retried with bounded backoff. Paid research initiation uses account-owned request IDs and browser approval. An unknown charged outcome must not be repeated automatically.
Keep requests bounded
The beta applies 120 authenticated requests per minute per account, tighter endpoint-specific limits, bounded source response sizes and timeouts. Do not poll complete tool catalogs or every wallet continuously. Cache public source metadata responsibly and retain source timestamps.