A key belongs to one team, many keys can share one plan
Every key sits under one team, and every key under that team draws from the same quota.
Staging and production should not need separate paperwork.
Create a key for a staging app and another for production. Both sit under the same team, and both read the same plan, the same quota, the same rate limit.
curl -H "X-API-Key: parse_staging_key" https://api.parseapi.com/postal/33139?country=US
curl -H "X-API-Key: parse_production_key" https://api.parseapi.com/postal/33139?country=US
Two keys, two names on the dashboard, one number for usage. Rotate the staging key without touching production, revoke an old one when a project ends, the team's plan never moves.
One team, one bill
A team is the billing unit. A key is just a named handle under it, split as many as you want, by environment, by app, by whoever is holding the credential.
Try it
Create a second key from the dashboard and call two different endpoints with two different keys. Usage lands on the same team either way. The team doesn't care which key did the work.