INTENT-AWARE EMBEDDINGS · resonant-embed-01

Embeddings that keep intent apart from everything else.

Standard embeddings compress meaning, intent, and tone into a single vector. Resonant preserves intent as a separable axis, so search, routing, memory, and recommendations can act on what users actually meant, not just what they wrote.

Get API keyWhy Resonant →
1536-d
EMBEDDING
32K
CONTEXT
100+
LANGUAGES
resonant.embed()
“Cancel my plan. Now.”
semantic↑ intent signalsemantic
Result: This user wants to leave, and they want it now. Route accordingly.

Intent is the action a user is trying to accomplish, independent of wording, tone, or topic.

SEE THE VECTOR SPACE

Watch intent lift out of the noise.

TOPIC →

Standard embeddings cluster by topic. A furious complaint and a calm question about the same thing land on top of each other.

INTENT
Question
calm · info-seeking
Complaint
urgent · negative
Praise
positive · low-urgency
TOPIC CLUSTERS
Billing · Shipping · Account

Same 18 messages, same model. Toggle to re-project the space.

WHY RESONANT

Embeddings were never trained to preserve intent.

Traditional embedding models optimize for semantic similarity. Complaints, questions, and praise about the same topic often end up in nearly identical neighborhoods.

Intent, urgency, sentiment, and sarcasm get averaged away long before retrieval ever sees them.

Resonant preserves those signals as independently recoverable information inside a single embedding, so downstream systems can retrieve, filter, and reason over both meaning and intent without a separate model.

THE COLLAPSE · THREE FAILURE MODEShigh cosine similarity ≠ same intent
COMPLAINT · SARCASM

"Wow. Fantastic. Another delay. Love that."

PRAISE · GENUINE

"Wow, fantastic. It arrived early. Love it."

QUESTION · INFO-SEEKING

"Can you reset my password?"

COMMAND · DIRECTIVE

"Reset my password."

RESEARCH · BROWSING

"Best cameras under $1000"

PURCHASE · TRANSACTIONAL

"Buy Sony A7 IV"

Standard embeddings score all three pairs above 0.89 cosine similarity. Resonant separates them by intent.

WHEN INTENT CHANGES THE OUTCOME

When intent changes the outcome.

Semantic similarity is enough until systems need to make decisions. Routing, recommendations, memory, and agent workflows all depend on understanding what users are trying to accomplish.

USER INPUT

Why is my bill so high this month?

STANDARD

FAQ: Understanding your monthly bill

GENERIC FAQ · COSINE 0.89
RESONANT

Escalation: Billing dispute — frustrated user

INTENT: FRUSTRATION · URGENCY: 0.87

Standard retrieval matches the topic. Resonant detects frustration and routes to dispute resolution.

BENCHMARKS

Competitive on semantics. Unmatched on intent.

Resonant matches existing models on semantic similarity while preserving intent as an independently recoverable signal. These are measured results from our evaluation suite.

85.5%
PARAPHRASE RETRIEVAL
Meaning retrieval R@5 across 200 queries
73.5%
REGISTER PREFERENCE
Intent signal prefers same-register content
39pp
STYLE SEPARATION
Gap between intent and meaning signals on style-varied content
INTENT SEPARATION IN PRACTICE
Same intent, different wording
high
Same wording, different intent
low

Formal and casual versions of identical content are recognized as having different intent. Same intent expressed differently is recognized as equivalent.

IntentBench

Existing leaderboards answer one question: Did retrieval find the right topic?

IntentBench answers a different one: Did retrieval preserve what the user wanted?

Open benchmark. Details at general availability.

MIGRATION

Replace your embedding endpoint, not your stack.

Resonant uses the same API shape as existing embedding providers.

Keep your retrieval pipeline.
Add one field to the response.
No reranker.
No intent classifier.
No second inference call.

QUICKSTART

One API call. One embedding. Two independent signals.

Compatible with the OpenAI embeddings API. Set return_intent=True to receive separable intent axes alongside every embedding.

01Drop-in API.
02Intent appended to every embedding.
03Filter, route, or rerank without another model.
from resonant import Resonant

client = Resonant(api_key="rsn-...")

r = client.embed(
    input="Cancel my plan. Now.",
    model="resonant-embed-01",
    return_intent=True,
)

r.embedding   # 1536-d semantic + intent vector
r.intent      # {"urgency":0.94,"sentiment":-0.71}

WHY NOW

LLMs made intent more valuable. Embeddings never caught up.

AI systems no longer stop at retrieval. They route requests, trigger workflows, decide when to ask follow-up questions, and maintain long-term memory.

Those decisions depend on intent, not just semantic similarity.

Embeddings became the foundation of AI infrastructure. They were never optimized for the signal that now matters most.

PRICING

Drop-in pricing for intent-aware embeddings.

DEVELOPER TRIAL
$25 credit

No credit card required

Full API accessIntent vectors included14-day access
Start building
INDIVIDUAL
$0.018 / 1M tok

Pay only for what you use.

Full APIIntent vectorsOpenAI-compatible APICommunity support
Get API key
SCALE
Custom

Higher volume pricing

Higher RPMBatch APIPriority supportSLA
Contact us
ENTERPRISE
Custom

Dedicated infrastructure

Dedicated capacityFine-tuned intent axesVPC deploymentSSO + audit logsDedicated support
Talk to us

No charge for the intent vector. It ships with every embedding.

Embed what they meant.

Replace your existing embedding endpoint in minutes and start retrieving, routing, and reasoning over what users actually meant.

Get API keyRead the Technical Discovery