Allow Studios to configure their own Hume API Key and Secret Key - Githubissues

casual-simulation / casualos

Casual Open Simulation for the Web

https://ab1.bot

MIT License

48 stars 9 forks source link

Allow Studios to configure their own Hume API Key and Secret Key #512

Closed KallynGowdy closed 1 month ago

KallynGowdy commented 1 month ago

Improved Hume AI features to support Studios.
- The ai.hume features now determine whether a Studio can configure their own Hume apiKey and secretKey.
- ai.hume.getAccessToken(recordName) now accepts a record name.
  - This allows the user to specify which record they want to use for hume.ai access.
  - Once a studio is configured, requests to one of the Studio's records will return an access token derived from the Studio's configured apiKey and secretKey.
  - Requesting users require access to the ai.hume resource kind and create action for the specified record.

Closes #493