API

The API is the platform's only door: the dashboard, the CLI, the SDKs, and your integrations all speak the same REST surface at api.myndlabs.ai, so there is no capability that exists in the UI but not in your code. The design goals are deliberately unexciting. Resources are nouns (runs, agents, files, webhooks, models), verbs are HTTP methods, identifiers are prefixed strings (run_, ag_, file_) that are unambiguous in logs, and every list endpoint paginates the same way with the same cursor shape. Mutations accept an Idempotency-Key header and honor it for 24 hours, which makes retry-on-timeout a safe default instead of a gamble. Errors are a single envelope — HTTP status, machine-readable code, human-readable message, and a field-level errors object on validation failures — documented exhaustively in the errors reference. Versioning is by date pin: your key locks to the version current when it was created, upgrades are explicit, breaking changes arrive only in new versions with a published migration guide, and old versions get a minimum twelve months of support. Authentication is bearer keys with granular scopes checked by the trust kernel on every call. Rate limits are per key with honest headers, so your client can pace itself instead of discovering the limit by hitting it.