Developers
Developers
Where a developer starts, with the published API and a key that you create after you sign in and a list of the programmes that we have not published.
What you do here
Read the contract before anything else. Create an account and a key if you need to call an operation that you have been granted. Read deployment and ownership if you run the software yourself.
What this does not grant
No language SDK, webhook catalogue, Kubernetes profile, public roadmap or live internal status board is published. This entrance does not pretend otherwise.
Before you continue
A commercial partnership is a different door. Use Partners when the relationship is a company agreement rather than a technical integration.
What a developer can rely on today
- Identity before capability. Staff and administrative surfaces require a session and a passkey. An account's own surfaces require the capability that each one names. A session alone opens nothing and root on a development machine gives no authority here.
- Credentials are issued, not shared. You create an API key from an account where you are signed in and you can revoke it at any time. We never email it and we never show it again after you create it. Every OAuth client is registered with validated redirect addresses.
- The published contract is the reference. The generated reference and the OpenAPI document sit at fixed addresses and both come from the router that the deployment runs. Nobody writes them by hand.
- Refusals are explicit. A caller over the budget for its address is refused with 429 and never quietly slowed. An unauthorised request answers 401 or 403 and says which one. An address that does not exist answers 404 with a page instead of an empty body.
- Work is recorded, verified, then deployed. We record a build and its tests against a release, a review acceptance says that it does not deploy, and an independent verification goes to a log that the application cannot write. A release is authorised and deployed only under the deployment authority and only where a deploy target exists.
Where a capability is not built, these pages say so and the catalogue does not list it. That is why an SDK, a container profile or a hosting option appears as absent rather than as a placeholder with a download that does not exist.
Developers
Every published page in this section, in the order the platform declares them.
- Getting started
- Platform architecture
- Developer documentation
- Using the API
- Software development kits
- Command line
- Developer authentication
- Developer authorisation
- Webhooks
- Platform events
- Integrations
- Extensions
- Data models
- Workflow development
- AGI development
- Agent development
- Developer tools
- Local development
- Self hosting
- Developer deployment
- Containers
- Kubernetes
- Hardware support
- Performance
- Observability
- Developer security
- Testing
- Compatibility
- API versioning
- Changelog
- Examples
- Tutorials
- Task guides
- Reference implementations
- Open source
- Contributing
- Developer programmes
- Developer resources
- Developer community
- Developer support
- Vulnerability disclosure
- Developer terms
Last reviewed 8 November 2026.