Product shape
Each product should own its domain workflow and call EthanKit only for shared concerns: identity, quota, keys, and usage reporting. Products authenticate to the API with an EthanKit API key rather than a registered client.
API keys
Use one EthanKit key per environment and keep product-level permissions explicit. Keys should be revocable without deleting the account or historical usage.
Launch checklist
- Create an EthanKit API key for the environment
- If product attribution is desired, set the
x-ethankit-clientheader to your product slug on gateway requests - Usage is attributed to the API key and its project; if you set the
x-ethankit-clientheader, it is recorded as an optional attribution label on usage rows (otherwise null) - Test balance exhaustion and retry behavior
- Add dashboard copy that names the product clearly