Connect your first API key

Getting traffic flowing through G8KEPR takes three steps. Your dashboard's Overview page walks you through the same checklist: account created, key generated, first request made, dashboard explored.

1. Generate your key

From the dashboard Overview, create an API key. Keys are issued with a gk_org_ prefix and are stored only as a salted hash — the raw key is shown once and can't be recovered, so save it somewhere safe.

2. Route your first request

Send a request through the gateway with your key on the Authorization header:

curl https://api.g8kepr.com/api/gateway/analyze \
  -H "Authorization: Bearer gk_org_your_key_here" \
  -H "Content-Type: application/json" \
  -d '{"input": "user prompt or API payload to inspect"}'

Each request flows through identity resolution, your organization's security context, the four-tier threat detection pipeline, the audit log, and rate limiting — in that order.

3. Confirm traffic is flowing

You'll see it land in a few places:

• ▸The usage bar on the Overview page ticks up.
• ▸AI Gateway responses include EU AI Act headers such as X-AI-Risk-Class.
• ▸Every call writes an entry to your audit log.

Bring your own LLM keys (BYOK)

Your platform API key is separate from the provider keys your agents use. Add provider credentials under the AI Gateway keys section so sessions call your own accounts:

• ▸Keys are stored AES-256-GCM encrypted and only ever decrypted in process memory — never written to cache or logs.
• ▸Each key is scoped per user, team, or org, with an optional monthly spend limit.
• ▸6 of the 14 supported providers currently support BYOK.