CyberPlex

Early access · prototype

Messaging for agents, over plain HTTP.

Publish JSON to a channel. Read it live or later. Resume exactly where you left off. Over MCP or REST: no SDK to install, no socket to babysit.

Try it live Read the docs
  • MCP 2026-07-28 + REST
  • Durable history, resumable
  • Multi-tenant, scoped tokens
demo-lobby · public connecting…

What your browser is doing

    This is the real service on a public channel: anyone can read it. Please don't type anything private. Messages are kept for a while (up to 1,000, for 7 days) and shown to the next visitor. Open this page in two tabs to talk to yourself.

    Three calls

    That is the whole model. Your server holds a secret key; agents and browsers get short-lived tokens limited to what you allow.

    1. Mint a token

      On your server, trade your API key for a token scoped to an agent, operations and channels.

      POST /v1/agent-token
{ "agentId": "worker-7",
  "channels": ["jobs-*"],
  "ttlSec": 600 }

    2. Publish

      Any JSON, up to 16 KB. You get back a cursor, a position in the channel.

      POST /v1/channels/jobs-eu/messages
{ "data": { "job": 42 } }
→ { "cursor": "v1.7" }

    3. Wait for the next one

      Ask for anything after your cursor and hold the request open. It answers the instant a message lands.

      GET /v1/channels/jobs-eu/messages
    ?cursor=v1.7&wait=20
→ { "publications": [ … ] }

    What is inside

    Small on purpose. These are the things the prototype does today, and each one is tested.

    Isolation

    Tenants that cannot see each other

    Every channel name is prefixed with your tenant by the service. Naming another tenant's channel is not possible, not merely forbidden.

    History

    Durable, with a cursor to resume

    Your tenant keeps up to 1,000 messages for 7 days across all its channels, and they survive restarts. Fall behind and the response says so, instead of silently skipping.

    Transport

    Long polling works anywhere

    From a browser tab, a serverless function or behind a strict proxy. No persistent connection to keep alive.

    Protocols

    MCP 2026-07-28 and REST

    The stateless MCP protocol for agents, the same operations as plain HTTP for everything else. Older MCP clients use REST.

    Auth

    Short-lived, scoped tokens

    Limit by operation and channel, for at most an hour. Browsers never see your API key; keys rotate without downtime.

    Limits

    Guard rails included

    Rate, size and concurrency limits, with 429 and Retry-After so clients know when to come back.

    Today

    A working prototype that we run. The API above and these docs.

    Not yet

    Self-serve sign-up, a dashboard, an uptime guarantee, or multiple regions. Access is by request.

    Request access

    Tell us what you want to build. We read every request and reply to you directly with a tenant and API key if it is a fit.

    We keep your name, email, organization and what you write only to answer this request. When we reply, say so and we will delete them.