Multiple API Tokens & Usage Tracking#463

Feature Description

We would like the ability to create and manage multiple API tokens from the platform settings.

Each API token should:

Have a custom name to identify its purpose, client, project, or environment.
Be individually manageable (create, revoke, regenerate).
Have its API consumption tracked separately.

We would also like an API endpoint to retrieve usage/consumption data per token.

Why Is This Needed?

We use the API across different clients and use cases and need to accurately attribute consumption.

Having separate named tokens and token-level usage data would allow us to:

• Identify which client or use case generated the consumption.
• Automate usage tracking through our systems.
• Simplify usage-based billing and cost allocation.
• Avoid having to implement our own usage attribution layer.

Expected Capabilities

-Multiple API tokens
-Create multiple tokens from the settings.
-Assign a custom name to each token.
-Revoke or regenerate individual tokens.
-Usage tracking per token
-Make usage metrics available over a specified period.

Usage API
-Provide an endpoint to programmatically retrieve consumption.
-Allow filtering/grouping usage by token and date range.
-Ideally expose metrics such as request count, consumed units, and associated cost when available.

Primary Use Case

One API token per client → track consumption per token → retrieve usage programmatically → calculate and automate client billing.