02 - Authentication - AIone API (English)

AIone supports both the OpenAI-compatible protocol and the Anthropic native protocol. Choose the appropriate authentication header and Base URL based on your client type.

OpenAI-Compatible Format

Use this for the OpenAI SDK, Cursor, Cline, Continue, and any custom client that supports OpenAI-compatible endpoints.

Base URL: https://api.nexara.net/v1

Authentication header:

Example:

Anthropic Native Format

Use this for Claude Code, the Anthropic SDK, and clients that call the Messages API directly.

Base URL: https://api.nexara.net

Authentication headers:

Example:

If your client only asks for a Base URL, use https://api.nexara.net for Anthropic native clients. The SDK will automatically append /v1/messages as required by the protocol.

Security Best Practices

API Keys use the sk-nex- prefix and can be created and managed in the AIone Console.

Never commit API Keys to source control repositories

Never hardcode API Keys in frontend code

Store keys in environment variables:

Key Management

Action	Description
Create	Console > API Keys > Create; optionally restrict which models the key can access
Rotate	Create a new key, migrate your workloads, then disable or delete the old key
Disable / Enable	Temporarily suspend or reactivate a key
Delete	Permanently remove a key (irreversible)

02 - Authentication

OpenAI-Compatible Format#

Anthropic Native Format#

Security Best Practices#

Key Management#

OpenAI-Compatible Format

Anthropic Native Format

Security Best Practices

Key Management