AIM Alpha 1 — open beta

One API layer for African intelligence.

Empire Union gives you one key, one base URL and one consistent response shape — AIM API for chat, vision, speech and documents, and eConnect for your users' Google and GitHub data.

Read the AIM API docs Explore every API

curl https://api.empireunion.xyz/v1/chat \
  -H "Authorization: Bearer $EMPIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "aim-alpha-1",
    "messages": [{ "role": "user", "content": "Sannu, yaya kake?" }]
  }'

The platform

Two APIs. One identity.

Pick an API to see what it does and how to call it. Both authenticate with the same Empire Union key.

AIM API

beta

Chat, reasoning, vision, speech and document generation — tuned for African languages, accents and context. One base URL, one key, every capability.

curl https://api.empireunion.xyz/v1/chat \
  -H "Authorization: Bearer $EMPIRE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "aim-alpha-1",
    "messages": [
      { "role": "user", "content": "Explain compound interest in Pidgin" }
    ]
  }'

Read the AIM API docs

Boring in the ways that matter

The interesting part should be what you build. Everything underneath should be predictable.

One base URL

Every endpoint lives under a single versioned base path. No per-product domains to hunt down.

One key

A single EMPIRE_API_KEY unlocks the whole platform. Add eConnect to the same key and it stays one secret to rotate.

Predictable errors

Every failure returns the same JSON shape — a machine code, a human message, and the request id you can quote in support.

Streaming first

Token-by-token responses over server-sent events, so your UI starts rendering while the model is still thinking.

African languages

Pidgin, Yoruba, Hausa, Igbo and Swahili are part of the core model — not a translation layer bolted on top.

Empire ID

One identity links a developer, their keys, their Telegram account and every integration under eConnect.

Three steps to your first response

Get your key

Create an Empire Union account, then generate an API key from the dashboard. Keep it server-side — never in a browser bundle.

Make one request

Point a single POST at /chat with your key in the Authorization header. If you get JSON back, you are done integrating.

Ship it

Read the request id from the response, log your token usage, and let the docs handle the rest.

Start with the AIM API reference.

Base URL, authentication, rate limits and every endpoint — laid out the way you will actually use it.

Open AIM API docs Go to eConnect