Projects
Projects group resources, keys and members. The unit of authorisation.
What it is
Every resource belongs to exactly one project. API keys are issued per project with a list of scopes. Members are users in your tenant with a role in the project (viewer / developer / admin).
When to use it
- Separate prod from dev.
- Give a contractor scoped access to only one project.
- Bill by project, with per-project budgets.
Quickstart
asc projects create my-proj
asc projects members add my-proj --email alice@example.com --role developerclient.projects.create('my-proj')
client.projects.members.add('my-proj', email='alice@example.com', role='developer')await client.projects.members.add('my-proj', { email: 'alice@example.com', role: 'developer' });Limits & quotas
| Limit | Default | Burst | Notes |
|---|---|---|---|
| Members per project | 200 | 1,000 | |
| Roles | viewer, developer, admin, owner | — |
Pricing
See pricing. Pay-as-you-go, billed monthly via Stripe.
API surface
POST /v1/projectsPOST /v1/projects/{p}/members
Required scope(s): projects:write. See Scopes.
Security
All access is authenticated and scoped. See Auth & scopes and Network controls.