Developer Quickstart

Make your first ASI:One request, read the response, and know where to go next.

Prerequisites

• An ASI:One API key
• Basic knowledge of HTTP requests
• Python, or any HTTP client

Step 1: Get your API key

1. Sign up at ASI:One
2. Navigate to the Developer section
3. Click Create New
4. Name your API key and save it somewhere safe

Step 2: Make your first request

$
curl -X POST https://api.asi1.ai/v1/chat/completions \
>
  -H "Content-Type: application/json" \
>
  -H "Authorization: Bearer $ASI_ONE_API_KEY" \
>
  -d '{
>
    "model": "asi1",
>
    "messages": [
>
      {"role": "user", "content": "Hello! How can you help me today?"}
>
    ]
>
  }'

Step 3: Understand the response

Your API call will return a response like this:

1
{
2
    "id": "ec3e76554baa4ebb838173e7f32fdb94",
3
    "choices": [{
4
        "finish_reason": "stop",
5
        "index": 0,
6
        "message": {
7
            "content": "Hey there! 👋 ...",
8
            "role": "assistant",
9
            "tool_calls": null,
10
            "reasoning_content": null
11
        }
12
    }],
13
    "created": 1768409272,
14
    "model": "asi1",
15
    "object": "chat.completion",
16
    "usage": {
17
        "completion_tokens": 149,
18
        "prompt_tokens": 2105,
19
        "total_tokens": 2254,
20
        "prompt_tokens_details": {
21
            "cached_tokens": 1920
22
        },
23
        "reasoning_tokens": 0
24
    }
25
}

The two you will read first:

• choices[0].message.content - the assistant’s reply.
• choices[0].finish_reason - why generation stopped. stop is a normal completion.

Every field, including token accounting and reasoning, is described on the Chat Completions API page.

Step 4: Pick your endpoint

Everything above used /v1/chat/completions. ASI:One also implements OpenAI’s Responses API at /v1/responses, which holds state for you: a response gets an id you can fetch later or chain the next turn onto. Which one to use is mostly a matter of which OpenAI format your code already speaks. See Responses API.

Next steps

1. Chat Completions API - The endpoint you just used, in full: streaming, multi-turn, and every response field
2. Responses API - The stateful alternative, with retrieve and chaining
3. ASI:One Models - Choosing between asi1, asi1-ultra and asi1-mini
4. Tool Calling - Let the model call your own functions