Early access

SDK

One REST endpoint,
any language.

The API is plain HTTPS + JSON — if your language can make a request, it can use Empress today. Clients exist to save you boilerplate, and we only list the ones that are real.

Node / TypeScript

Built — npm release pending

@empress-eco/client — a zero-dependency typed client covering the whole sold surface: emit, statements, exportAll, analytics, belief. It exists and its smoke test is a tenant's actual first hour against production. It is not on npm yet; publishing is a deliberate release step, not a formality.

Python

Planned

On 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

Planned

On 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.