v0.3 — context + verify

Agent coordination without the token tax

NEKTE is an open protocol for token-efficient agent-to-agent communication. Progressive discovery, zero-schema invocation, budget-aware responses.

Get Started Read the Spec
TypeScript
import { NekteClient } from '@nekte/client';

const client = new NekteClient('http://localhost:4001');
const catalog = await client.catalog();          // ~24 tok for 3 caps
const result  = await client.invoke('sentiment', { input: { text: 'Great!' } });
console.log(result.out);                         // "positive 0.9"
-99%
Token savings vs MCP
(100 tools)
8
Tokens per capability
(L0 discovery)
$10,744
Monthly savings
(enterprise, 50 tools)
0
Extra tokens for
cached invocations

8 Primitives. Minimal Overhead.

Every primitive is designed to minimize token cost in the common case.

nekte.discover
Progressive discovery at L0/L1/L2
~8 tok/cap
nekte.invoke
Zero-schema invocation via version hash
0 extra
nekte.delegate
Task delegation with streaming
Budget-aware
nekte.context
Context envelopes with permissions + TTL
Compressed
nekte.verify
Result verification with proofs
On-demand
nekte.task.cancel
Cancel a running or suspended task
~20 tok
nekte.task.resume
Resume from checkpoint
~20 tok
nekte.task.status
Query task lifecycle state
~30 tok

How NEKTE Compares

NEKTE complements existing protocols — it does not replace them.

Feature MCP A2A NEKTE
Progressive discovery No No L0/L1/L2
Zero-schema invocation No No Version hash
Native token budget No No First-class
Result compression No No 3 levels
Task lifecycle (push) No Polling Push (SSE/gRPC)
gRPC transport No Yes Native
MCP bridge N/A No @nekte/bridge

The Bridge: Zero Migration

Don't rewrite your 10,000+ MCP servers. Drop the bridge in front.

Agent <-- NEKTE --> nekte-bridge <-- MCP --> MCP Server(s)
                             |
                     cache + hash
                     + compression

90%+ token savings. Zero backend changes. Day 1.
Bridge Setup Guide