Authentication

Every request to the Meida API requires a valid API key passed as a Bearer token in the Authorization header. Keys are scoped by environment.

API Key Format

Meida uses prefixed API keys to distinguish between environments. This prevents accidental production usage during development.

Production
me_live_xxxxxxxxxxxxxxxx

Full access to live routing clusters. All providers active.

Devnet / Sandbox
me_test_xxxxxxxxxxxxxxxx

Isolated sandbox for local testing. Rate limits relaxed.

Passing the API Key

Authorization Header
curl https://api.meida.cloud/v1/chat/completions \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer me_live_xxxxxxxxxxxxxxxx" \
  -d '{ "model": "auto-route", "messages": [...] }'

Security Best Practices

  • Never expose your me_live_ key in client-side code or public repositories.
  • Use environment variables (MEIDA_API_KEY) on your backend server.
  • Rotate keys immediately if you suspect they have been compromised.
  • Use me_test_ keys during development and CI/CD pipelines.
ArchitectureChat Completions