SDKs
AeThex does not currently publish a guaranteed stable first-party SDK release contract for the KAEL API. Use the OpenAPI contract or direct HTTP integration while interfaces are evolving.
| Field | Value |
|---|---|
| Product maturity | In development |
| Documentation status | Active |
| Contract source | OpenAPI Reference |
| Last source review | 2026-06-26 |
Recommended approach
For ordinary JSON endpoints:
- Download
/static/custom/openapi.yaml. - Generate a client for your language.
- Wrap generated code behind your own application boundary.
- Pin the generated client to the contract version you reviewed.
For /kael/stream, use an SSE-capable fetch client. Many generated SDKs treat streaming responses as a plain string and need a small custom adapter.
SDK responsibilities
An AeThex client library should provide:
- Base URL configuration.
- Typed request and response models.
- Cookie or server-side tenant authentication.
- SSE parsing.
- Error normalization.
- Timeouts and cancellation.
- Safe retry behavior.
- No logging of credentials.
Stability
- Client model keys are more stable than provider model IDs.
- Public routes are more stable than privileged operator routes.
- Experimental fields can change before a formal SDK release.
- Review KAEL Changelog before regenerating.