Research

Overview Interpretability Alignment science Economic research

Safety

Commitments Responsible scaling Trust centre

Learn

Academy Developer docs Models News

Company

About Careers Contact
Try Resonance Log in

Resonance is the product. Everything below it is meant to be boring.

Three model sizes, one API surface, and tooling that behaves the same way across all of them. The interesting part is supposed to be what you build, not which endpoint you called.

The lineup

Pick by shape of the task, not by leaderboard position. All three share a context window, a tool protocol, and a refusal policy.

Cortex 5.1

The one for hard, long work

Multi-day agentic runs, ambiguous briefs, and problems where a wrong confident answer costs more than a slow careful one. Slower and more expensive, and worth it when it is.

Context
1M tokens
Best at
Planning, long-horizon agents, analysis
Relative cost
$$$$
Pulse 5.1

The default

Most production traffic should land here. Fast enough for interactive use, careful enough for customer-facing work, and the model we tune first when a new capability ships.

Context
1M tokens
Best at
Coding, support, extraction, drafts
Relative cost
$$
Echo 5

The one you stop thinking about

Classification, routing, and the million small calls that make an agent feel responsive. Cheap enough that you design around latency instead of budget.

Context
400K tokens
Best at
Routing, tagging, high-volume calls
Relative cost
$
Developer platform

One call, three model sizes, same tool protocol.

Swap the model name and the rest of your code keeps working. Tool definitions, streaming, and structured output behave identically across the lineup, so a prototype can graduate without a rewrite.

  • Streaming, tool use, and JSON schema output on every model.
  • Prompt caching and batch inference to cut the cost of repeated context.
  • SDKs for Python, TypeScript, Go, Java, and a plain HTTP surface underneath.
  • Evals and tracing built in, so a regression shows up before your users find it.
agent.py
from anthropic import Neurok

client = Neurok()

# Same call shape at every size — swap the model, keep the code.
response = client.messages.create(
    model="neurok-pulse-5-1",
    max_tokens=2048,
    tools=[search_docs, run_query],
    messages=[
        {"role": "user",
         "content": "Reconcile last quarter and flag anything odd."}
    ],
)

for block in response.content:
    if block.type == "tool_use":
        print("calling", block.name, block.input)

Pricing

Published rates, no sales call required for standard usage. Enterprise adds controls, not a different model.

Model pricing per million tokens
Plan Price Includes Best for
Free $0 Pulse 5.1 with daily limits, web search, file uploads. Trying it on real work
Pro $20 / month Cortex 5.1 access, higher limits, projects, shared context, desktop app. Individuals and small teams
Team $30 / seat / month Everything in Pro, plus SSO, admin controls, and usage reporting. Teams standardising on one assistant
API Usage-based All three models, prompt caching, batch inference, and spend caps. Products built on the platform
Enterprise Contact sales Region pinning, zero-retention mode, audit log, named security contact. Regulated and large organisations

Prices shown are illustrative placeholder values for this design study.

Surfaces

The same model, in the place where the work already is.

Web & desktop Resonance apps Projects, artifacts, file uploads
Terminal Resonance Code Agentic work in your repository
Editor IDE integration Inline edits with your project context
Workplace Slack & Microsoft 365 Answers where the thread already is
Browser Browser extension Summarise, compare, extract
API Console Keys, usage, evals, tracing
Get started

The fastest way to judge this is to hand it something you actually have to finish.

Free tier, no card, and a usage policy that tells you plainly what the model will decline. If it fails your task, that is useful information and we would like to hear it.