No packaged SDK yet. The contract is the SDK.

Eventium does not currently distribute a client library for any language. Everything below is what you can actually use today, and it is deliberately short rather than aspirational.

Why this page says "none" rather than listing one. A page here previously documented a Python client and told readers to install it from a directory inside the API repository. That package exists in no Eventium repository, in no branch history, and on no package index, so the instruction could not succeed for anyone who followed it. The page was withdrawn on 2026-11-10 rather than restyled. If a client library ships later, it will be listed here with its real package name and a version you can install.

What exists today

Language	Status	What to use instead
Any	No published package	The REST contract and the hosted MCP endpoint, both documented and stable.
Any, generated	Supported path	Generate a typed client from the published OpenAPI document. It describes exactly the operations a developer may call.
MCP clients	Supported path	Use your existing MCP client. Eventium is a hosted MCP server; no Eventium-specific library is involved.

Generate a client from the published contract

The schema at https://api.eventium.ai/api/openapi.json is the developer contract: the operations a developer may call, each annotated with its exposure tier. It is generated from the running service, so a generated client cannot drift from what the API actually serves.

curl -s https://api.eventium.ai/api/openapi.json -o eventium-openapi.json

# then use the generator you already trust, for example:
#   openapi-generator-cli generate -i eventium-openapi.json -g python -o ./eventium-client
#   npx openapi-typescript eventium-openapi.json -o ./eventium.d.ts

Those generators are third-party tools. They are named as examples of the approach, not as supported Eventium software.

Writing a client by hand

Two credentials, two different purposes. This is the whole of it:

Credential	Header	Use for
Browser session	Cookie, plus the CSRF token for state-changing calls	Signed-in product surfaces. A browser cannot read the HttpOnly session cookie; call `GET /api/auth/session` instead.
Scoped API key	`X-Api-Key`	Server-to-server integrations. Create and revoke keys in the API keys console.

curl -s https://api.eventium.ai/api/health

curl -s https://api.eventium.ai/api/commercial/atlas-api/usage \
  -H "X-Api-Key: $EVENTIUM_API_KEY"

Base URL is https://api.eventium.ai. Branch on the machine-readable code in an error envelope rather than on its prose, and retry only when the response says retryable. See schemas and errors.

If you are integrating an agent

Agent integrations do not need a client library at all: Eventium is a hosted MCP server, so an MCP-capable client connects to it directly. The configuration for each supported client lives on the MCP destination, and REST or MCP explains which method fits which job.

REST API reference
Endpoints, schemas and the published contract. MCP
Connect a client and discover tools. Webhooks
Receive events instead of polling.