v0.1 (Draft) · Open · MIT

RAK Content Language — open spec for AI-native content

RAK is a small, open standard for content that is written once, owned by its creator, and consumed natively by any AI agent — cited, fresh, and (optionally) paid. It does not replace existing standards; it composes them (RSL for licensing, C2PA for provenance, MCP for transport, x402 for payment).

Read the spec (SPEC.md) RepoReference implementation

What RAK is, in one paragraph

AI agents today burn tokens searching and scraping the web. The result is expensive, stale, uncited, and pays the authors nothing. RAK closes the loop: a canonical content object (the "UPC of content for AI"), a per-creator content wallet (provenance + signature), an RSL-compatible license, MCP as the transport, and a settlement layer that pays creators per substantive AI citation. Write once → paid many times. Like Spotify pays artists per stream, RAK pays creators per AI citation. See ECONOMICS.md for the moat thesis.

Spec sections (v0.1)

§1
Why

Agents burn tokens scraping. No universal way to author once, own, cite, get paid. RAK defines that object.

§2
Design principles

Neutral global naming · compose-don't-reinvent · creator-first · free-to-read, owned-to-publish · a language + many agents.

§3
The RAK Content Object

The atomic unit — id, type, lang, title/body, owner, provenance, license, media. The 'UPC of content for AI.'

§4
Provenance — the content wallet

HMAC v0 → Ed25519 v1, portable wallet.json. C2PA-compatible for media.

§5
Licensing (RSL-compatible)

owned_public · owned_licensed · rak_editorial · restricted. Maps onto Really Simple Licensing.

§6
Access & transport — MCP

RAK is spoken over Model Context Protocol. Streamable HTTP at /api/mcp/rak/mcp or stdio via @rak/mcp.

§7
Tool namespace — rak_<module>_<op>

content · rag · meta · research · write · media · qa · crawl · distribution · owned.

§8
Agents on RAK (the platform)

Stanowski is the reference Polish agent; anyone can build their own (regional/vertical/white-label). Network effect = citation market.

§9
Economic loop

Reads free; paid platforms pay per substantive cite. Node takes ~15%, creator gets the rest, settled via x402/Stripe. Write once → paid many times.

§10
Interoperability

RSL (license) · C2PA (provenance) · MCP (transport) · x402/ACP (payment) · llms.txt (discovery). RAK ties them together.

§11
Versioning & governance

Semver of the language. Company-led-open today; standards-body donation (W3C CG / Linux Foundation) on the table.

Canonical source: SPEC.md · Raw: raw

Compose, don't compete

ConcernRAK usesStandard
Licensing termslicense.*RSL
Provenanceprovenance.*C2PA
Transport / toolsrak_<module>_<op>MCP
Payment railper-cite settlementx402 (Linux Foundation), ACP (OpenAI/Stripe)
Discoveryllms.txt, sitemapllms.txt, sitemap.xml

How to propose a change (RFC)

  1. Open a discussion or issue in the RAK-MCP repo titled RFC: <short title>.
  2. Describe the motivation, the proposed change to SPEC.md (sections affected), and the migration path for existing implementations.
  3. If feedback converges, open a PR against SPEC.md tagged spec. Editors merge after at least one independent implementer signs off.
  4. Breaking changes bump the major (rak_version). Tool deprecations come with a support window and a one-step migration note.

Versioning & governance track

    RAK Content Language — open spec for AI-native content (v0.1) | ZERO