Emote

Chat agents that only ever reply with paragraphs can feel stiff. Emote is a small HTTP API for developers who want their agent to react to a message with a single emoji, the way a person would in Telegram, WhatsApp, iMessage, Discord or Slack. It bills itself as a reaction API for agents: one message in, one emoji or none out.

One call, one reaction

A developer's server sends the incoming message to a single endpoint, together with optional personality text describing the agent, up to 12 earlier messages for context, and the reactions the platform supports. That means a default set of 12 emojis or as many as 254 custom ones. Emote returns one of those options, or "none", since staying silent is treated as a valid choice. The caller can ask for reserved, balanced or expressive behavior. The intended pattern is to call it in parallel with the main model, so the reaction lands while the reply is still being written.

Documentation and limits

Docs cover TypeScript, Python and cURL and include a guide per messaging platform. Each account is limited to 300 requests a minute, input is capped at 12,000 bytes, and inference has a deadline of 1.5 seconds. Reactions can be wrong or inappropriate, and the terms say so.

Data handling

According to the privacy notice, message text is sent to an unnamed external AI inference provider, and Emote does not keep it in its own database or logs; metadata like token counts and model identifiers is retained. Sign-in and billing run through Clerk and Stripe, on Neon Postgres and Vercel.

Plans and who runs it

There is a free tier that gives a one-time allowance of requests, a paid developer plan with a monthly allowance that pauses at the limit rather than billing overage, and an enterprise option by arrangement. Payments are generally non-refundable. Emote comes from Experimental Software, a name its own site gives to an independent software lab with one person running it. The terms took effect on 18 September 2026 and specify no governing law.