API Documentation

The Emotional Reactor as a middleware layer — plug it into any product you're building, and get emotionally-aware, memory-persistent responses back.

Getting your API key

Create an account at eminle.in and log in. Your API key appears in the bar above the demo chat, starting with em_. Keep it secret — it identifies your account and its usage.

Authentication

Pass your key in the x-api-key header on every request.

x-api-key: em_your_key_here

Send a message

POST https://api.eminle.in/v1/react

This is the core endpoint. Send a message on behalf of one of your own end-users, and get back a reply shaped by real emotional context and that user's memory over time.

curl -X POST https://api.eminle.in/v1/react \
  -H "Content-Type: application/json" \
  -H "x-api-key: em_your_key_here" \
  -d '{
    "user_id": "your-end-users-id-123",
    "message": "I did not get the job I interviewed for"
  }'

Request body

Field	Type	Notes
user_id	string	An identifier for this specific end-user of yours. Their memory and emotional history are tracked per user_id, not per your account.
message	string	Max 4000 characters.

Response

{
  "response": "That's a real loss to sit with...",
  "emotional_state": { ... },
  "expression": { ... },
  "companion_mode": "support",
  "attachment_level": 0.12,
  "tier": "free"
}

Rate limits

Plan	Limit
Free	50 requests / day
Pro	Higher daily limit — see pricing

Going over the limit returns an HTTP 429 status.

Errors

Status	Meaning
400	Missing or invalid message
401	Missing or invalid API key
429	Rate limit reached
500	Something went wrong on our end — safe to retry

Data & privacy

Conversations sent through this API are stored so that a given user_id's emotional context and memory persist across requests — that's the actual feature. Here's exactly where that data goes:

Storage. Conversation data is stored in our own database to power memory and continuity. It is not sold or shared with third parties.

The underlying model provider. Messages are processed by Groq to generate responses. Per Groq's own policy, they do not train on or retain API inputs/outputs by default, and we have enabled Zero Data Retention on our account for additional protection.

Your responsibility. If your product handles sensitive end-user conversations, make sure your own privacy policy discloses that messages are processed through this API, consistent with how we disclose our own use of Groq.

Questions

Email eminle.com@gmail.com — we respond within 24 hours.