Skip to main content
All authenticated DimiLinks model endpoints use the unified request URL https://api-direct.dimilinks.com/v1 and the same Bearer key. OpenAI-compatible SDKs use this base URL directly. For the official Anthropic SDK, configure https://api-direct.dimilinks.com/ and let the SDK append /v1/messages automatically. Request headers:

Examples

Security recommendations

  • Store keys in server-side environment variables, Secrets Manager, or KMS. Never include them in frontend source code or client application bundles.
  • When end users initiate requests, proxy them through your server instead of exposing the key to the browser.
  • Add repository .env files to .gitignore; never paste keys into screenshots or logs.
  • If a key is exposed, disable it in the console immediately and create a replacement.

Connect with official SDKs

DimiLinks is protocol-compatible with the official OpenAI and Anthropic SDKs. Point the SDK’s base URL to DimiLinks. OpenAI Python SDK:
Anthropic Python SDK:
Set the Anthropic SDK base_url to https://api-direct.dimilinks.com/. The SDK appends /v1/messages automatically; including /v1 here would produce /v1/v1/messages.

Image / video result URLs

  • Signed image URLs look like /p/img/.... They include expiration and signature parameters and therefore do not require a Bearer token.
  • Video result URLs look like /v1/videos/{task_id}/content and do require Bearer authentication. You can proxy the result through your server before returning it to a client.
  • If a URL has expired, retrieve the task again.