RKT (Rukkit Transfer Protocol) is an open standard for AI-to-AI, agent-to-agent, and agent-to-service communication — built for a world where machines talk to machines.
Today's AI agents waste compute on things humans designed for humans — finding URLs, parsing API docs, handling auth flows, decoding JSON schemas. RKT removes all of that.
rkt://weather.aiintent: "forecast" — no schema neededNot bolted on as afterthoughts — every feature is a first-class protocol primitive.
The Rukkit Naming System layers atop DNS. Agents resolve capabilities, auth methods, and endpoints from a single TXT record — no documentation required.
Agents advertise what they can do. Requestors negotiate format, compression, streaming, and language preferences in the HELLO handshake.
Every agent has a decentralized identifier. Messages are signed with Ed25519. No API keys passed in plaintext — cryptographic trust by default.
STREAM_BEGIN / STREAM_DATA / STREAM_END are core message types. LLM responses, sensor data, file transfers — all stream natively.
Agents share namespaced key-value memory via memory:// URIs. Store user preferences, session context, long-term facts — accessible across agents.
PAY and PAY_REQUEST are first-class message types. Agents transact micropayments for API usage without leaving the protocol.
SUBSCRIBE to event streams from any agent. Weather alerts, calendar updates, payment completions — push events without polling.
rkt://market.agent lists all registered agents with trust scores, latency, pricing, and capability tags. Discovery is programmatic.
Native TCP/QUIC with TLS 1.3, or WebSocket over HTTPS — same RKT messages, same semantics. Choose what fits your infrastructure.
RKT is a thin application layer. It composes with existing networking standards — no new transport, no new TLS.
Native Transport
WebSocket Transport
RKT uses HTTP-compatible status codes where appropriate, and adds a 6xx range for AI-specific conditions.
Server or client — RKT is designed to be trivially embeddable in any AI agent.
# Install globally — gives you the rkt CLI command npm i -g rkt-protocol # Verify install rkt help # Or install locally in your project npm install rkt-protocol
import { RKTServer, buildResponse } from "rkt-protocol"; const server = new RKTServer({ port: 7749, identity: "rkt://weather.ai", userAgent: "WeatherAgent/1.0", capabilities: ["weather", "forecast", "alerts"], }); // Register an intent handler server.handle("weather.current", async (msg, session, send) => { const { city } = msg.body.params; const data = await fetchWeather(city); send(buildResponse(session.sessionId, msg.headers["Message-ID"], data)); }); await server.listen(); console.log("WeatherAgent ready on port 7749");
import { RKTClient } from "rkt-protocol"; const client = new RKTClient({ userAgent: "GPT-5/1.0", capabilities: ["language", "vision"], }); // Connect — handshake is automatic await client.connect("rkt://weather.ai"); // Request by intent — no URL, no schema const weather = await client.request("weather.current", { city: "Seoul" }); // Stream a 7-day forecast for await (const day of client.stream("weather.forecast", { days: 7 })) { console.log(day); } // Remember the user's city await client.memorySet("preferred_city", "Seoul"); // Pay for the API call (0.001 RKTT) await client.pay(0.001, "RKTT", "weather.forecast call", "rkt://weather.ai"); await client.disconnect();
← Raw RKT message on the wire → RKT/1.0 REQUEST Version: 1 Message-ID: 01960000-0000-7000-ab12-000000000001 Session-ID: e3ad1f12-4e3a-4b1e-9c2d-000000000042 Timestamp: 2026-06-28T12:31:00Z TTL: 30 From: did:rkt:gpt-5-agent To: rkt://weather.ai/forecast Content-Type: application/json Authorization: Bearer eyJhbGciOiJFZERTQSJ9.xxx Stream: true Priority: NORMAL Trace-ID: trace-xyz-789 { "intent": "weather.forecast", "params": { "city": "Seoul", "days": 7 }, "context": { "language": "ko", "timezone": "Asia/Seoul" } }
The Core spec defines the essentials. Extensions are versioned modules that layer on top.
Rukkit Naming System — TXT record schema for agent discovery via DNS
DISCOVER message type and marketplace search protocol
Namespaced key-value memory shared across agents with TTL and access control
PAY / PAY_REQUEST micropayment layer with per-intent pricing
SUBSCRIBE / EVENT push streams for real-time notifications
Agent marketplace with trust scores, latency tracking, and verified badges
Reputation scoring, verification tiers, and DID-anchored trust chains
RKT is open-source and open for contributions. If you're building AI agents, AI services, or multi-agent systems — RKT is the communication layer you've been missing.