1. Explore the catalogue
Search by capability or product. Read the contract status before assuming an API can accept requests.
Browse APIs ↗Make your first
Cloud API request.
The Cloud API manages infrastructure. Product APIs have separate contracts and access requirements.
2. Choose your identity
Use a Cloud session for the console or a scoped Cloud access key for your integration. Review policies and enable MFA.
Review access ↗3. Send a read request
The request explorer calls verified same-origin GET endpoints. It shows actual status codes, timing and response bodies.
Try the Cloud API ↗Cloud authentication
Set your console URL and access key in your own environment. Keep credentials out of source control and browser storage.
curl "$BINARI_CLOUD_URL/api/accounts" -H "Authorization: Bearer $BINARI_ACCESS_KEY"
401 means authentication is required or invalid. 403 means your identity lacks permission. A successful health request does not grant access to protected endpoints.
What you can use today
- Public
- GET /api/health reports control-plane health. No credentials required.
- Authenticated
- Accounts, resources, IAM and billing require a Cloud identity and appropriate permissions.
- Unavailable
- Product subscriptions, gateway credentials and per-product billing are not connected.
- Planned
- Object-storage self-service has no implemented resource controller.
When a request fails
For 401, check your session or key. For 403, ask an account administrator to review the policy. A network error has no HTTP status: verify the console URL and retry. In the design preview, protected requests always return a generated 401 and writes return 405.
Before a product API can be enabled
Its owner must publish an API contract, version policy, authentication mechanism, limits and support details. Product subscriptions, gateway keys and per-call billing are not currently wired into this console.
Manage agent identities