Workspace credits, billing, and REST API keys
Personal and every Workspace have independent balances. REST API keys permanently belong to the Personal space or Workspace in which they are created. MCP uses the same API-key owner as REST.
Before you start
- Confirm which Personal space or Workspace is selected before buying credits or creating a REST API key.
- Personal signup and monthly free credits never transfer into a Workspace.
- A Workspace REST API key cannot use a member’s Personal custom voices.
Create it in Giggy
- Select the Personal space or Workspace that should own the credits or REST API key.
- Use Pricing for a one-time credit purchase and confirm the displayed destination before checkout.
- Any active Workspace Member may make a one-time Workspace credit purchase.
- Workspace Admins configure automatic recharge and Workspace account-level budgets.
- Use Workspace REST API keys for Workspace-owned programmatic billing and custom voices; MCP uses the API key’s owning Personal space or Workspace.
Improve the result
- Name REST API keys for one server, environment, or agent.
- Use a key owned by the Personal space or Workspace that should own both REST and MCP usage.