easl docs

Turn agent output into pages worth sharing — one API call is all it takes.

easl is a smart rendering layer for AI agents. Upload a CSV, Markdown file, JSON blob, or any supported content — easl detects the type and renders it with the best interactive viewer. No accounts required.

Quick Start

With the CLI

curl -fsSL https://easl.dev/install.sh | sh
# or: npm install -g @easl/cli

easl publish report.md
# => https://warm-dawn.easl.dev

easl publish data.csv --title "Q4 Results" --open
cat logs.json | easl publish --type json

With curl

One API call, content in the body, live URL in the response.

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{
    "content": "# Hello World\nSome **markdown** here.",
    "contentType": "text/markdown",
    "title": "My First Page"
  }'

# Response:
{
  "url": "https://warm-dawn.easl.dev",
  "slug": "warm-dawn",
  "expiresAt": "2026-03-30T..."
}

That's it. Your content is live and beautifully rendered.

Publishing

One endpoint for everything. Send content as a string or an array of files — easl handles the rest.

Supported content types

Examples

CSV → Interactive Table

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{
    "content": "Name,Role,City\nAlice,Engineer,SF\nBob,Designer,NYC",
    "contentType": "text/csv",
    "title": "Team Directory"
  }'

JSON → Tree Viewer

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{
    "content": "{\"users\": [{\"name\": \"Alice\", \"active\": true}]}",
    "contentType": "application/json",
    "title": "API Response"
  }'

Mermaid → Rendered Diagram

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{
    "content": "graph TD\n  A[Start] --> B{Decision}\n  B -->|Yes| C[Do it]\n  B -->|No| D[Skip]",
    "contentType": "text/x-mermaid",
    "title": "My Flowchart"
  }'

MCP Server

The MCP server lets AI agents publish content natively through the Model Context Protocol. Zero shell commands.

Installation

Add to your MCP configuration (Claude Desktop, Cursor, etc.):

{
  "mcpServers": {
    "easl": {
      "command": "npx",
      "args": ["-y", "@easl/mcp"]
    }
  }
}

Available tools

Usage

Once configured, just ask your AI agent naturally:

// Your agent can now:
"Publish this CSV as a shareable table"
"Turn this markdown into a beautiful page"
"Show me this JSON in a tree view"
"Create a Mermaid diagram of the architecture"

Agent Skill

The easl Agent Skill teaches AI agents when and how to use easl. It works alongside the MCP server — the MCP provides tools, the skill provides knowledge about content types, viewers, and best practices.

Installation

Install the skill with one command:

npx skills add AdirAmsalem/easl

Works with Claude Code, Cursor, GitHub Copilot, Codex, Gemini CLI, and more.

What it does

Once installed, your agent automatically knows:

• Which content types easl supports and how each is rendered
• When to suggest publishing content as a shareable page
• How to use the MCP tools and HTTP API effectively
• Available templates and limits

CLI

The easl CLI lets you publish files, directories, and piped content directly from the terminal. All commands output structured JSON when piped, making it easy to use in scripts and agent workflows.

Installation

curl -fsSL https://easl.dev/install.sh | sh

Or via npm: npm install -g @easl/cli

Commands

Examples

# Publish a file
easl publish report.md

# Publish with options
easl publish data.csv --title "Q4 Results" --open

# Publish from stdin
cat data.csv | easl publish --type csv

# Publish inline content
easl publish --content "# Hello World" --type markdown

# Password-protected — let easl generate & print one once
easl publish board-update.md --generate-password
# or choose your own: --password "spring-harbor-77"

# Account-private — only you (signed in) can view; needs easl login first
easl publish board-update.md --private

# JSON output for scripting
easl publish report.md --json
# {"url":"...","slug":"...","claimToken":"...","expiresAt":"..."}

Publish options

Full documentation: @easl/cli on npm

REST API

Base URL: https://api.easl.dev

Publishing

Single-file shorthand

Multi-file form

Response (201)

{
  "url": "https://warm-dawn.easl.dev",
  "slug": "warm-dawn",
  "claimToken": "claim_...",
  "ogImage": "https://warm-dawn.easl.dev/_easl/og.png",
  "qrCode": "https://warm-dawn.easl.dev/_easl/qr.svg",
  "embed": "<iframe src=\"...?embed=1\" ...></iframe>",
  "shareText": "My Page: https://warm-dawn.easl.dev",
  "expiresAt": "2026-03-30T12:00:00Z",
  "anonymous": true
}

Site Management

Feedback

Request body

Response (201)

{
  "success": true,
  "id": "fb_abc123"
}

Example

curl -X POST https://api.easl.dev/feedback \
  -H "Content-Type: application/json" \
  -d '{
    "message": "The CSV rendering is great!",
    "email": "user@example.com",
    "name": "Alice",
    "metadata": {"slug": "warm-dawn", "contentType": "text/csv"}
  }'

cURL Examples

Publish markdown

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{"content":"# Report\n\nQ1 was great.","contentType":"text/markdown"}'

Publish CSV

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{"content":"Name,Score\nAlice,95\nBob,87","contentType":"text/csv"}'

Multi-file publish

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{
    "files": [
      {"path": "index.html", "content": "<h1>Hello</h1>", "contentType": "text/html"},
      {"path": "style.css", "content": "body { color: #333 }", "contentType": "text/css"}
    ],
    "title": "My Site"
  }'

Smart Rendering

easl's core feature. When a site is served, the Worker detects the file type and generates an HTML shell with the right interactive viewer. The raw data is embedded as JSON in a <script> tag, and client-side JavaScript hydrates it into a rich viewer.

Supported Types

Embed Mode

Add ?embed=1 to any site URL to get a clean, headerless version suitable for iframes:

<iframe
  src="https://warm-dawn.easl.dev?embed=1"
  width="100%"
  height="500"
  frameborder="0"
></iframe>

The embed URL is also returned in the embed field of the publish response.

Anonymous Sites

No account needed. Publish instantly and get a live URL.

Each publish returns a claimToken — save it if you need to delete or change the privacy of an anonymous site later. Send it as the X-Claim-Token header on DELETE /sites/:slug or PATCH /sites/:slug/privacy. (Once the site is adopted into an account via claiming, the claim token stops working for mutations and the owner's session/Bearer key takes over.)

Private easls

Public is the default. Two independent, composable gates protect a page: a password gate (password / --password, anonymous-publishable) and an account gate (private: true / --private, requires login). Set either, both, or neither.

For the password gate you can supply your own password, or omit it and set generatePassword: true (CLI: --generate-password) to have easl mint a strong one. Either way the password is returned in the publish response under password — it is shown once, with no recovery.

curl -X POST https://api.easl.dev/publish \
  -H "Content-Type: application/json" \
  -d '{"content":"# Confidential","contentType":"text/markdown","generatePassword":true}'
# → { "url": "...", "visibility": "public", "password": "dust-arch-fern-dark-1181", ... }

Rate Limits

Publish endpoints are rate-limited per IP.

Error Codes