Quickstart

From registration to first response with the current MVP.

This page is written for developers validating the current rollout. It assumes you are using the OpenAI-compatible chat completions path and a console-issued API key.

Open Console Jump to Code Open Troubleshooting

curl https://api.anlinkai.com/api/v1/chat/completions \
  -H "Authorization: Bearer ak_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen-flash",
    "messages": [
      {"role": "system", "content": "You are a concise assistant."},
      {"role": "user", "content": "Write a release note headline."}
    ]
  }'

Steps

Recommended integration order

Keep the first pass simple. Validate account access, key issuance, and a single successful request before you expand your traffic shape.

1. Register and sign in

Open the console and create your account
Confirm you can reach the overview page after login
Check that trial credit is visible in the balance area

2. Create an API key

Create one key for your current test environment
Copy the plaintext key immediately after creation
Store it in server-side environment variables

3. Choose an active model

Use the model catalog on the docs home page or in the console
Start with a model currently marked active
Use the exact exposed code such as qwen-flash

4. Send a chat completions request

Target https://api.anlinkai.com/api/v1/chat/completions
Pass your key as Authorization: Bearer ...
Use a small prompt first so failures are easy to inspect

5. Validate the result

Confirm the response body is valid JSON
Open Usage Logs in the console
Check request status, token counts, and recorded cost

6. Manage failures

Keep the request ID from failed calls when possible
Check whether the model is still active
Check whether the account still has remaining credit

Examples

Reference request shapes

These examples are written against the current MVP surface, not a future multi-endpoint release.

cURL

curl https://api.anlinkai.com/api/v1/chat/completions \
  -H "Authorization: Bearer ak_your_key" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "qwen-flash",
    "messages": [
      {"role": "system", "content": "You are a concise assistant."},
      {"role": "user", "content": "Write a release note headline."}
    ]
  }'

JavaScript

const response = await fetch("https://api.anlinkai.com/api/v1/chat/completions", {
  method: "POST",
  headers: {
    "Authorization": "Bearer " + process.env.ANLINK_API_KEY,
    "Content-Type": "application/json"
  },
  body: JSON.stringify({
    model: "qwen-flash",
    messages: [
      { role: "system", content: "You are a concise assistant." },
      { role: "user", content: "Write a release note headline." }
    ]
  })
});

const data = await response.json();
console.log(data);

Python

import os
import requests

resp = requests.post(
    "https://api.anlinkai.com/api/v1/chat/completions",
    headers={
        "Authorization": f"Bearer {os.environ['ANLINK_API_KEY']}",
        "Content-Type": "application/json",
    },
    json={
        "model": "qwen-flash",
        "messages": [
            {"role": "system", "content": "You are a concise assistant."},
            {"role": "user", "content": "Write a release note headline."},
        ],
    },
    timeout=60,
)

print(resp.status_code)
print(resp.json())

Checklist

Before you move beyond test traffic

Do not expose your API key in browser-side bundles.
Use one key per environment so revocation stays manageable.
Record failures and compare them with Usage Logs in the console.
Keep prompts and concurrency small until the route is validated.
Do not assume self-service recharge exists in the current MVP.

Console URL

https://console.anlinkai.com

API base

https://api.anlinkai.com/api/v1

Primary endpoint

POST /chat/completions

FAQ

https://www.anlinkai.com/faq