Developer quickstart
Use developer access to inspect your App Cloud account and connect supported operations to your workflow. A developer key covers keys, billing, and read-only MCP tools. To build apps from a coding agent, sign it in to your account instead: see Connect your coding agent.
Make a first read
Section titled “Make a first read”Obtain a developer key from the account’s developer settings with billing:read. Developer access is part of the current Pro plan. Store the key in your local environment, then request the active limits:
curl --fail-with-body https://api.exepad.com/v1/billing/limits \ -H "Authorization: Bearer $EXEPAD_KEY"Inspect the response for the limits and usage applied to the account. Keep credentials out of browser code, logs, and source control.
Choose an interface
Section titled “Choose an interface”- REST: key management and billing information.
- MCP: with a key, compatible agents can inspect key metadata, wallet, and plan limits; signed in on Pro, they build apps.
- A2A: discovery is available; the current card advertises no app-building skills.
Migrating an old example
Section titled “Migrating an old example”The earlier /v1/apps lifecycle API and /v1/openapi.json return 404 in the current service. Old create/edit/publish examples are historical, not a current contract. Create in Studio while using the developer interfaces for their documented operations.