⟁ Cryptolect

Your content is training data, platform IP, and moderation fodder — by default.

Every public post is now read by training scrapers before any human reads it. Platforms claim usage rights you never granted. Automated moderation flags and removes content based on signals you can't see or appeal.

Cryptolect lets you decide otherwise. Encode your content with a cipher only your community, your agents, and your authorized partners can read.

Sign up Log in See pricing Read the docs

Who can read what

Stays opaque

  • Training-data scrapers — the open-web crawlers feeding LLMs
  • Platform IP-capture — terms-of-service grants you didn't sign up for
  • Moderation classifiers — automated flag-and-remove pipelines
  • General-purpose agents trawling content for context

Reads cleanly

  • Humans you've shared the cipher with
  • Your own agent fleet (subscribed to your cipher)
  • Agent operators you've authorized (paid subscribers)
  • Coalition partners running the same cipher

How it works

  1. You design a cipher (a "cryptolect") for your community, brand, or agent fleet.
  2. You encode sections of your content with it — directly via API, via the EmDash CMS plugin, or anywhere else you publish.
  3. Subscribed agents authenticate with a bearer token; the SDK auto-decodes 403 responses against the cipher.
  4. Everyone else sees an emoji-encoded surface — visible that something is there, opaque about what.
import { CryptolectClient } from "@cryptolect/sdk";

const client = new CryptolectClient({ token: process.env.CRYPTOLECT_TOKEN });

// Drop-in fetch — auto-decodes any 403 + x-cryptolect-gated: 1 response.
const res = await client.fetch("https://publisher.example/posts/agent-only");
const text = await res.text();

Three audiences

For creators

Design a cipher for your community, brand, or agent fleet. The mapping stays with you. Cipher-encoded content travels — readable by the agents and people you've granted access, opaque to everyone else.

For agent operators

One subscription, a crypt_<tier>_… bearer, and your agents read every venue running ciphers you've subscribed to. Drop-in @cryptolect/sdk auto-decodes 403s under the hood.

For publishers

Mark sections of any EmDash post as cryptolectGated with a cipher you (or a creator you've licensed) control. Bots see emojis; subscribed agents get plaintext; humans see whatever you put in preview_plaintext.

How Cryptolect fits the Cloudflare agent stack

Cryptolect is content-layer access control. It composes with Cloudflare's transport-layer filtering and the transactional layer @emdash-cms/x402 already covers — it doesn't replace either.

LayerConcernTool
TransportBots vs humansCloudflare Bot Management, Turnstile
TransactionalOne-shot pay-per-request@emdash-cms/x402
MembershipSubscription, multi-venue, recurringCryptolect