Today's the big day, we just deployed kimi-k2 and qwen3-coder:480b to our api. If you want to play around with this, hop on our discord: https://discord.com/invite/DmaHAdGcNy

Alright @everyone it's the big day.

This is work in progress. We are doing a ton of stuff that you can't see, but it is up and we would appreciate testing and feedback. The inferencing API is now running on B200's. Right now everyone has access to all the models, we'll be closing this down as we go along.

We'll be launching paid subscriptions, we had a lot of discussions and honestly these models are so powerful that we'll probably be targeting $99/mo, but we'll start with $75/mo as a welcome offer. You won't have to use phantom, it'll be email and stripe (we'll do crypto too don't worry). We will be giving stakers access to what we consider reasonable limits (input/output tokens per month), but they'll be less than the subscriptions at least initially. Eventually we hope we can just map stakers to these plans, but for the moment we just added a bunch of 24/7 infra, which we're running in parallel to the GPU workloads most of you are familiar with.

The models on the api include the hermes3:70b and llama3:70b, both now running at 64K context (thanks B200s), but the big news is kimi-k2 and qwen3-coder. Right now everyone with an api key has access to these models. We'll be limiting them to stakers and subscribers later this week.

Keep in mind these are monstrous models and you might hit the Cloudflare's request timeouts after 100 seconds. That's not us - that's a cloudflare "feature". We're working on the api.compute3.ai (with an 'e') deployment as we speak, and that will be naked (no cloudflare, just a couple of load balancers) so it won't have that issue. We'll be adding instructions on how to set all of this up with claude code, qwen code and probably codex as well. In the mean time feel free to test, api.comput3.ai is now running a litellm-proxy so it should handle most of the shenanigans that the coding agents need. However, we're not routing /anthropic/* (or /openai/ for that matter) to our models yet, we're looking for a reasonable way to be able to leave you control over which goes where instead of picking one for you. I do believe overloading the /model should work, but I haven't tested this yet.

Enjoy and let us know how it goes. Here's some curls to get you started.

$ curl -X GET https://api.comput3.ai/v1/models | jq
{
  "data": [
    {
      "id": "hermes3:70b",
      "object": "model",
      "created": 1677610602,
      "owned_by": "openai"
    },
    {
      "id": "kimi-k2",
      "object": "model",
      "created": 1677610602,
      "owned_by": "openai"
    },
    {
      "id": "qwen3-coder:480b",
      "object": "model",
      "created": 1677610602,
      "owned_by": "openai"
    },
    {
      "id": "llama3:70b",
      "object": "model",
      "created": 1677610602,
      "owned_by": "openai"
    }
  ],
  "object": "list"
}

You can access these as a normal /v1 API.

curl -X POST https://api.comput3.ai/v1/chat/completions \
-H "Authorization: Bearer c3_api_YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
      "model": "kimi-k2",
      "messages": [
        {
          "role": "system",
          "content": "You are a helpful assistant."
        },
        {
          "role": "user",
          "content": "What is 2+2?"
        }
      ]
    }'
{"id":"chatcmpl-007e9d34e4474e78902934247b1f72bc","created":1755501320,"model":"kimi-k2","object":"chat.completion","system_fingerprint":null,"choices":[{"finish_reason":"stop","index":0,"message":{"content":"2 + 2 = 4","role":"assistant","tool_calls":null,"function_call":null},"provider_specific_fields":{"stop_reason":163586}}],"usage":{"completion_tokens":8,"prompt_tokens":24,"total_tokens":32,"completion_tokens_details":null,"prompt_tokens_details":null},"service_tier":null,"prompt_logprobs":null,"kv_transfer_params":null}