Your live presence,
one well-specified request away
The rawest layer of Chimeling — a fully specified HTTP contract for your presence. No framework assumptions, no client library required.
Raw,
by design
The SDK is the comfortable path. The API is the floor it stands on — plain HTTP that any language can speak.
Skipping the SDK costs you nothing but comfort.
Speaks fluent HTTP with
Specified,
not implied
Every endpoint, every field, every failure mode is written down — and enforced by the schemas that generated the document.
OpenAPI 3.1
The complete surface in one machine-readable document. The reference and the server come from the same source of truth.
Typed end to end
Requests and responses are validated by the very schemas that publish the spec. What you read is what runs.
Deterministic errors
Failures are part of the contract — 400, 401, 403, 404, 409 — each with a documented shape you can branch on.
Versioned from day one
Everything lives under /v1. Breaking changes arrive as a new version, never as a surprise.
- POST/v1/devices201
- GET/v1/devices200
- PATCH/v1/devices/{deviceId}200
- POST/v1/devices/{deviceId}/apps201
- POST/v1/icons201
- POST/v1/presenceSoon
Legible to your AI
You don’t have to be a backend engineer — an unambiguous contract is one your AI assistant can read whole and integrate on the first pass.
- No guessed field names — Every schema is published, down to the error shapes.
- No hallucinated endpoints — The whole surface fits in one machine-readable document.
- No trial-and-error loop — Deterministic status codes tell your agent exactly what happened.
Raw access,
same rules
The API writes into the same pipeline as everything else — whatever you send still runs through your rulesets and filters before your audience sees it.
Start with the raw layer
The API ships with every Chimeling account — join the waitlist and your first request is one key away.