Base URLhttps://sinecloud.dev/api/gateway/v1
Before your first request
Select your organization, prepare resources in Console, and issue an organization API key with the required product scopes. Current permissions, resource access, budget and available funds are checked on every call.
Choose an available route from the model catalog and use its ID as model. The catalog covers model discovery, chat completions, responses, messages, embeddings, images, audio, generation and durable task lifecycle. Use the appropriate native protocol and preserve JSON, streaming SSE, multipart and binary body formats. Review current model access, supported operations and billing in Console.
Grant modelRead to list routes and modelInvoke for inference and task operations. Project restrictions and route policies apply on every request. Managed routes require available funds and budget; own-key routes use the organization’s provider credentials. Keep original task IDs and inspect durable status before retrying uncertain execution.
Organization key authentication and base URL
The production API origin is https://sinecloud.dev; the documentation origin does not serve product requests. The path prefix is /api/gateway/v1. Use the complete path documented for the operation, replacing resource IDs, models and endpoint revisions with your actual selections.
Authorization: Bearer $SINECLOUD_API_KEY
Set SINECLOUD_API_KEY to your own environment variable value; never use platform service credentials. Each operation lists required scopes in x-sinecloud-scopes.
This reference is read-only. Run requests in Console or your own client. Browsing documentation never creates a key, starts execution or incurs an execution charge. Keep request IDs and execution receipts; a lost connection does not cancel work. Follow the operation’s recovery instructions before submitting again.
