Data and security

Security

API keys, how provider credentials are held, and where request data flows.

Every call authenticates with an organization API key (xpl_...). A key acts only for its own organization. Your own provider credentials are stored encrypted and are never returned by any API.

Keys

KeyCan do
Inference keyCall models, read usage, the catalog and its own limits, manage your org's data controls and provider connections
Provisioning keyEverything above, plus create, update and revoke keys through the keys API (a normal key gets 403)

The plaintext key is shown once, at creation. We store only a hash. Each key hangs off an identity, so usage and guardrails can be grouped per team or product. A key can carry its own spend cap and per-minute ceilings.

POST/api/v1/keys
curl -X POST https://api.experientiallabs.ai/api/v1/keys \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name": "ci", "limit": 50, "limit_reset": "monthly"}'
{
  "data": { "hash": "5c1e...", "name": "ci", "limit": 50, "limit_reset": "monthly" },
  "key": "xpl_..."
}

Spend and rate bounds

BoundScopeWhere
Spend capOne key, daily, weekly, monthly or yearly (UTC)Budget & limits
Requests and tokens per minuteOne keyBudget & limits
BudgetsTeam, key, model or identitySpend page
Rate-limit tierWhole organizationSee Rate limits

Your provider credentials

When you connect your own provider key, the secret goes to an encrypted vault. The connection keeps the provider name, non-secret settings (base URL, region) and the last four characters. The secret is released to the serving process only when a rung on that connection is dialled.

CredentialStoredShown
Your xpl_ keyHash onlyOnce, at creation
Your provider keyEncrypted vaultLast four characters
Guardrail classifier tokenEncrypted vaultLast four characters

Where request data goes

StepData
Your app to the gatewayTLS to api.experientiallabs.ai
Gateway to providerThe request, to the rung that serves it, and only rungs your provider policy allows
LedgerMetadata only, never content
CaptureContent only while your capture switch is on, never under ZDR

Request headers such as Authorization are never forwarded to a provider; safety_identifier stays with us. See the privacy policy for every store and who can read it.

Report a vulnerability through the contact in /.well-known/security.txt on platform.experientiallabs.ai.