Skip to main content

​
Base URL

Choose the domain for the protocol family you use. Both domains share the same Bearer key:
Protocol familyBase URLPrimary routes
OpenAI-compatiblehttps://dimilinks.com/v1/chat/completions, /models, /images/*, /videos/*, /tasks/{id}
Native Anthropichttps://api-direct.dimilinks.com//v1/messages
See Authentication for details.

​
Route overview

MethodFull URLDescription
GEThttps://dimilinks.com/v1/modelsList the models available to the current key
POSThttps://dimilinks.com/v1/chat/completionsOpenAI-compatible chat for GPT; also supports Claude and other text models through the OpenAI protocol
POSThttps://api-direct.dimilinks.com/v1/messagesNative Anthropic protocol; recommended for the Claude SDK and Claude Code
POSThttps://dimilinks.com/v1/images/generationsText-to-image generation with JSON reference-image extensions
POSThttps://dimilinks.com/v1/images/editsMultipart image-to-image generation and editing
POSThttps://dimilinks.com/v1/videos/generationsText-to-video and reference-image-to-video generation
GEThttps://dimilinks.com/v1/tasks/{task_id}Shared image and video task retrieval
GEThttps://dimilinks.com/v1/videos/{task_id}/contentDirect video task result (authentication required)
GEThttps://dimilinks.com/p/img/{task_id}/{idx}Signed image URL (no Bearer token required; the signature is embedded in the URL)

​
Protocol conventions

  • Text chat: compatible with the official OpenAI and Anthropic SDKs; point the SDK’s base URL to DimiLinks.
  • Images: responses follow OpenAI Images conventions. data[].url may be a relative path, an HTTPS URL, or a Data URL.
  • Videos: asynchronous by default. Submission returns a task_id immediately; poll /v1/tasks/{task_id} for progress.
POST https://dimilinks.com/v1/images/generations?async=true   # Submit an image task
POST https://dimilinks.com/v1/videos/generations              # Submit a video task (always asynchronous)
GET  https://dimilinks.com/v1/tasks/{task_id}                 # Shared task retrieval
Image and video generation times vary. The asynchronous workflow avoids long-lived connections, gateway timeouts, and tasks being lost when a page closes.