Status & Support
When something breaks, check whether it is the platform or your integration before you write to anyone.
Start with the Kakr Labs status page. If the platform is healthy there, the next stop depends on what you are stuck on — the table below points you at the primary source for each kind of question.
Where to go
| I need to... | Go here |
|---|---|
| Check whether the platform is up | Kakr Labs status page |
| Confirm an exact path, header, or request body | OpenAPI spec |
| Browse every operation in one place | Endpoint Index |
| Try a request without writing code (Standard) | Postman — Standard |
| Try a request without writing code (Enterprise) | Postman — Enterprise |
| Read or file an issue against a client library | liaas-sdk on GitHub |
| Create an account or generate an API key | pteri.org |
The resources in full
Status page — incident history and current platform state. Check here first so you do not debug your own code against an outage.
OpenAPI spec — the machine-readable source of truth for the API surface. The Endpoint Index mirrors it, but the spec wins if they disagree.
Postman collections — runnable requests you can fire from the browser. There are two: Standard and Enterprise. Use the one that matches your plan.
liaas-sdk — the client library monorepo. Each language lives in its own subdirectory. Read the source there when a client behaves differently from the spec, and open issues against that repo rather than the docs.
pteri.org — account sign-up and the dashboard where API keys are generated. Its own Help / Support and "Report a Bug" sections are the route for product questions that are not about the API surface.
Reaching a human
| Route | What it is |
|---|---|
| pteri.org → Help (Support) | The product's own support entry point, including a Report a Bug page. |
kakr.ai → Contact, or contact@kakr.ai | The corporate site for Kakr Labs Inc. kakr.org redirects here. |
| GitHub issues | Client library bugs. Say which language directory you are using. |