Meet Aleria at NVIDIA GTC Berlin · 21 and 22 October · GTC Berlin · Booth 3054Book 20 minutes

Build on Aleria, under the same rules.

The gateway API for models, the Aleria API for your organization's experts, an MCP server and the CLI. One sign-in, and the same permissions and audit log as everyone in your organization, inside your border.

Sign in, then open Settings and choose API keys.

Three steps to the first call.

  1. 1
    Get a keySign in to Aleria, open Settings, then API keys. A new key is shown once.
  2. 2
    Call a model or an expertREST, the SDK or the CLI.
  3. 3
    Connect your toolsPoint any MCP client at your Aleria.
# one API for every model, inside the country
curl https://gateway.your-org.aleria.ai/v1/chat/completions \
  -H "Authorization: Bearer $ALERIA_KEY" \
  -d '{
    "model": "aleria-reason",
    "messages": [{"role": "user",
      "content": "Summarise the Q3 risks"}]
  }'

Endpoint names and SDK calls are illustrative until the docs are public.

Four ways in, one set of permissions.

Gateway API

Aleria's own and open models behind one endpoint, with keys, limits, logs and failover.

Experts API

Run your organization's experts from code, in a project, with its sources and its approvals. Or start an automation from your own system with a webhook.

MCP server

Point any MCP client at your Aleria. It sees only what the signed-in person may see.

CLI

Your experts from the terminal, for scripts, schedules and the work you already automate.