One-click endpoint

The endpoint you get from the arkor.ai home page: what it serves, how to call it, and how long it lasts.

The arkor.ai home page has a "Get your endpoint" button. Clicking it provisions a working OpenAI-compatible inference endpoint immediately, with no account and no credit card.

What you get

The page shows three things after provisioning:

• A base URL of the form https://<slug>.arkor.app/v1. It is OpenAI-compatible, so it drops into any OpenAI SDK as baseURL.
• An API key, shown exactly once. Copy it immediately; only a hash is stored, and Arkor Cloud cannot show it again.
• The model the endpoint serves by default. One-click endpoints are multi-model: they serve Arkor's public model catalog (no LoRA adapter attached), with the model shown on the page as the default. Callers pick a model per request via the OpenAI model field, and GET /v1/models lists the current ids.

Point any OpenAI client at it:

import OpenAI from "openai";

const client = new OpenAI({
  baseURL: "https://<slug>.arkor.app/v1",
  apiKey: "<your one-time key>",
});

const res = await client.chat.completions.create({
  // The model id shown with your endpoint, or any id from GET /v1/models.
  // Omitting `model` also works and uses the endpoint's default model.
  model: "<model id shown with your endpoint>",
  messages: [{ role: "user", content: "Hello!" }],
});

An unknown model value returns 404 with code model_not_found, so don't send a placeholder string. Two caveats among the listed ids:

• Anthropic models (claude-*) are served via Anthropic's native POST /v1/messages route rather than the OpenAI call above — sending one to chat.completions returns 400 with a message pointing at the right route. See dialects.
• Premium models are listed but require an account: calling one on an anonymous one-click endpoint returns 403 with code model_requires_signup. Sign up (and click the same button while logged in) to use them.

The full request specification (parameters, streaming, tool calling, error codes) is in the Chat Completions API reference.

How identity works

Everything in this section and the next applies to anonymous visitors; see Signed-in users for the other path.

The browser that clicked the button holds an anonymous identity in an httpOnly cookie. The endpoint belongs to that identity's own workspace; the bearer token behind it never reaches page JavaScript. Clearing cookies or switching browsers means Arkor Cloud can no longer show you that endpoint, but the endpoint URL and API key keep working until expiry.

Limits and expiry

• Endpoints expire after 7 days. The expiry is stamped at creation. After it passes, the endpoint stops resolving (requests return 404) and it is deleted along with its keys and stored runs.
• Up to 3 live endpoints per browser identity. Creating more trims the oldest.
• Clicking "Create another endpoint" always provisions a fresh endpoint with a fresh one-time key. Revisiting the page with an existing endpoint shows its URL again, but never re-reveals the key.

Signed-in users

Clicking the same button while logged in creates a normal account-owned endpoint instead: it lands in an App Server project in your organization, appears in that project's Endpoints tab, and is managed like any other project endpoint. No anonymous cookie is involved, the endpoint never expires, and the three-endpoint cap does not apply. Each click provisions a fresh endpoint with a fresh one-time key.

Keeping an endpoint

There is no flow for transferring an anonymous one-click endpoint into an account. When you need an endpoint that does not expire, sign up, create a project, and create an endpoint from the project's Endpoints tab (or use the one-click button while signed in, per above). Account-owned endpoints never expire, support multiple labelled API keys, and can serve your own fine-tuned adapters. See Managing endpoints.