Qualia is the emotional intelligence API for AI — an EQ layer for AI agents that adds relationship intelligence and communication style awareness to any agent, assistant, or workflow. Understand people, not just prompts.
Connect Qualia to Claude, ChatGPT, Cursor, Slack, or any MCP-compatible agent in minutes. The same relationship intelligence — wherever communication happens.
Every surface consumes the same two core calls: context.person to profile the recipient, and adapt.message to rewrite your draft.
Today's agents are syntactically fluent and emotionally blind. They treat a frustrated parent, a skeptical VP, and an anxious student as the same input.
The missing layer isn't a better model. It's relationship intelligence — knowing who you're talking to, how they communicate, and what the relationship needs right now.
Connect via our remote MCP server — Claude gains get_relationship_context and adapt_message as native tools. Zero prompt engineering required.
Or use the REST API directly. Python and JavaScript SDKs ship with typed responses, auto-retry, and the full OpenAPI 3.1 spec.
Or install the CLI: npx qualia profile sarah@acme.com and get a full archetype profile in your terminal in seconds.
An AI agent that writes emails without Qualia is syntactically correct and emotionally blind. With Qualia, the agent calls /v1/context/person before drafting — getting the recipient's archetype and communication strategy. It then calls /v1/adapt/message to rewrite the draft to fit.
Embed Qualia into a CRM side panel. When a rep opens a contact, the copilot surfaces relationship health, tone trend, and communication archetype — then suggests an adapted outreach draft.
Before a support agent replies to any ticket, Qualia runs /v1/analyze/tone — detecting frustration level, urgency, and churn risk. The agent then uses /v1/adapt/message to reframe the response so it lands with empathy, not just accuracy.
Wire Qualia to any Claude workflow via the remote MCP server. Claude gains get_relationship_context and adapt_message as native tools — no prompt engineering required. Zero EQ logic for the developer.
A teacher writing to a frustrated parent, a counselor following up with an anxious student — all high-stakes communications that happen dozens of times a day. The SDK enables LMS and SIS platforms to embed this district-wide.
Bottom line first. Action items second. Details optional.
Decision. Reasoning. Implementation.
Trust first. Execution second.
Future-state focused. Big opportunities.
Use "we." Build consensus.
Context first. Reasoning second. Conclusion third.
Provide plan. Provide ownership.
Focus on people. Show support.
Provide framework. Provide process. Provide next steps.
Data. Analysis. Recommendation.
Teach. Explain. Explore.
Provide details. Provide documentation. Avoid ambiguity.
Free sandbox. No credit card. Python + JS SDKs. Claude MCP recipe on day one.