Authentication

API keys, what they pay from, their retention, and the rate limits.

Send a key in the Authorization header of every request: Bearer eevo_sk_…. Create keys on API keys in the Eevo console. MCP clients can sign in with OAuth instead (MCP server).

• A key is shown once, when it is created. Keep it in a secret manager or an environment variable, never in code. The docs use $EEVO_API_KEY.
• Keys belong to the organization. Its free decisions, then its prepaid balance, pay for their requests.
• Each key has its own retention: none, 30d, 90d, 1y, unlimited (Configure data controls). none ("Not stored") can be chosen once your organization has bought credit.
• Use one key per integration, so the decision log and Usage tell them apart and one can be revoked alone.
• A revoked key's next request is a 401 authentication. Its decisions stay in the log.

Rate limits

Over either, the answer is a 429 rate_limited with a Retry-After header in seconds, and nothing is charged. Ask Upright if you need more.