One project. One explicit boundary.

Approved members register sandbox projects with a distinct identity, exact HTTPS redirects and minimal scopes. Production, other people's account data and external code execution remain closed.

Create app Read the API

Project contract

What the sandbox really stores.

A project is the shared boundary for keys, scopes, redirects and daily usage metrics. Every operational request is authorised again on the server.

Identity: Name, stable slug and responsible Developer member.
Environment: Sandbox only today; a project is never silently promoted to production.
Redirects: Explicit HTTPS destinations only, with no general wildcards.
Scopes: Each key can carry only a subset of the scopes already approved for the project.
Activity: Requests and errors are aggregated daily by project and operation — never by using the plaintext secret.
Revocation: Project archiving and key revocation take effect server-side on every request.