ModelsPricingDocs
ConsoleRequest access
Documentation

Build with Astrelay

Everything you need to send your first request and run in production.

Quickstart

  1. Create an API key in the console. Give it a spend limit and an expiry.
  2. Set the base URL of your OpenAI-compatible SDK to the value below.
  3. Pick a model ID from the pricing page and send a request.
Base URL
https://aidgu.com/v1
API key
From Console → API keys
curl https://aidgu.com/v1/chat/completions \
  -H "Authorization: Bearer $ASTRELAY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"model": "<model-id>", "messages": [{"role": "user", "content": "Hello"}]}'

Authentication

Send your key as a bearer token in the Authorization header. Anthropic-format requests may use x-api-key instead.

Never ship an API key in browser or mobile app code. Call the API from your server.

Endpoints

MethodPathPurpose
POST/v1/chat/completionsChat completions (OpenAI format), streaming supported
POST/v1/responsesResponses (OpenAI format)
POST/v1/messagesMessages (Anthropic format)
GET/v1/modelsModels available to your key

Errors

StatusMeaningWhat to do
400Invalid request, or a feature that isn’t enabled for this modelFix the request; don’t retry automatically.
401Missing or invalid API keyCheck the key and the Authorization header.
403The key may not use this model, or the route doesn’t matchCheck the key’s model allow-list.
413Request larger than the limitTrim history or tool definitions.
429Rate or concurrency limit reachedFollow Retry-After if present. Otherwise, wait at least 5 seconds and increase the delay if the limit persists.
502Upstream could not be reachedThe request may already be billed. Check usage logs before retrying.
503Upstream paused, budget reached, or prices under reviewRetry later; nothing was forwarded.

Limits

Request size
256 KiB per request, history and tool definitions included
Output
Up to 32,768 tokens per request
Rate
60 requests per minute per account by default; ask us to raise it
Retries
We never retry a billed request for you

Data & privacy

We store account details, balances, API keys and request metadata (time, model, token counts, status code, request ID) to bill and support you. Prompt and response content is not written to our logs by default. Your requests are processed by the upstream provider that serves the model you choose.

Support

Email [email protected] with the request ID from your usage log. We aim to reply within one business day.