SDK
One REST endpoint,
any language.
The API is plain HTTPS + JSON — if your language can make a request, you can ship against Empress today. Typed clients save you the boilerplate.
Node / TypeScript
Built — npm release pending @empress-eco/client — a zero-dependency typed client for the
whole surface: emit, statements, exportAll, analytics, belief. Its test suite
is a tenant's actual first hour, run against production. Not on npm yet.
Full typed reference — generated from the SDK source at build, so it cannot drift from the code.
Python
PlannedOn the roadmap — not yet released. Until then, the REST API is complete from Python via any HTTP library.
# works today
import requests
requests.post("https://empress-api.jdnyzio.workers.dev/statements",
headers={"Authorization": "Bearer KEY"},
json=statement) Go
PlannedOn the roadmap — not yet released. The OpenAPI spec below generates a serviceable client in the meantime.
Works today, from anywhere
The REST API is the product.
curl -X POST https://empress-api.jdnyzio.workers.dev/statements \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"actor": { "account": { "name": "support-agent", "homePage": "https://empress.eco" } },
"verb": { "id": "https://empress.eco/verbs/resolved" },
"object": { "id": "https://example.com/tickets/892" },
"result": { "success": true }
}' Machine-readable reference: https://empress-api.jdnyzio.workers.dev/openapi.json — rendered human-readable at /docs/api.