End users in the Directives table, an alert when one runs out of budget, and attribution on evaluate and suggest
The Directives table has an End users group for per-end-user rate limits, daily quotas, budgets and the end-user requirement, with a new limit on each end user's concurrent requests. A new end_user.budget_exhausted webhook tells you when an end user's budget refuses a request.
end_user.budget_exhausted is sent once per end user per day or month, however often that end user retries, with the end user, the period, the budget and what was spent. It goes to your webhook endpoints only, not by email.
endUser.concurrentRequests limits how many requests one end user can have in flight; one more returns 429 concurrency_limit_exceeded with X-RateLimit-Scope: end_user.
/v1/evaluate and /v1/suggest now read ib-user, user and ib-tags like chat completions: the end user and tags are stored on the request, shown in Logs and usage export, and limited by per-end-user Directives and tag budgets.
More in Directives: Per end user.