Getting started

Five minutes from sign-in to a memory your assistant can recall.

1. Sign in

Open eam.thundera.eu/login and sign in with Thundera (single sign-on at auth.thundera.eu). The first sign-in creates your EAM account automatically from your Thundera identity (matched by email, then linked by issuer and subject). The web app then goes to /app.

One account, three ways in

The web app uses your Thundera session cookie, the macOS app uses OIDC sign-in, and MCP clients use either OAuth or an API token. All of them land in the same memory store.

2. Write a memory

From the API (replace the token, see API reference):

curl -sS https://eam.thundera.eu/api/v1/write \
  -H "Authorization: Bearer $EAM_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"content":"We chose Postgres for the billing service.","source_type":"TEXT","tags":["project:billing"]}'

The response contains memory_id, persisted and salience_score. A memory is stored only if its salience score reaches the threshold (0.38); a low-value text is discarded and persisted is false.

3. Search it

curl -sS https://eam.thundera.eu/api/v1/search \
  -H "Authorization: Bearer $EAM_TOKEN" -H "Content-Type: application/json" \
  -d '{"query":"which database for billing?","top_k":5}'

4. Create an API token

Open Settings → API tokens and create one. The token is shown once. Each account has exactly one active token: creating a new one revokes the previous one immediately.

5. Connect an assistant

Follow MCP integration for Claude Code, Kiro, Grok and Perplexity. For capture on a Mac, install the macOS app.