Now in public beta

The documentation layer
for AI agents

Turn your API into an executable interface and make it discoverable by every AI agent.

Agents don't just read Elba docs. They find them, understand them, and use them.

Launch Your Agent DocsBrowse agent registry
Two-sided platform
Agents can use your product
  • 01Structured AgentSpec with typed actions
  • 02MCP server config, agent.json, llms.txt
  • 03Reasoning docs for every action
  • 04Prompt to action playground
Agents can discover your product
  • 01.agent.json + MCP protocol endpoints
  • 02Agent registry + capability search
  • 03JSON-LD, sitemap, llms.txt crawling
  • 04Embeddable widget for any site

How it works

From raw API to a fully executable and discoverable agent interface.

01

Paste or import your API

Drop in any API description, OpenAPI/Swagger spec, or plain English. Drag-and-drop file import included.

02

Generate Agent Docs

Elba generates a structured AgentSpec with typed actions, reasoning docs, and example prompts.

03

Publish and Index

Your docs go live at yourco.useelba.com with .agent.json, MCP config, llms.txt, and JSON-LD — all auto-generated.

Generates .agent.json, MCP config, llms.txt, JSON-LD, sitemap, and robots.txt automatically.

04

Agents discover and execute

Any LLM can find your API via search, MCP, or direct crawl — understand it and call actions with zero hallucination.

Two primitives. One platform.

Elba gives agents two things they need: the ability to use your API, and the ability to find it.

Execute

Prompt to action, instantly

Use the Playground to map natural language prompts directly to actions and see structured mock outputs. Agents understand exactly what to call and what they'll get back.

playground
> "Send a welcome email to jane@acme.com"
action: sendEmail
inputs: { to: "jane@acme.com", type: "welcome" }
output: { status: "sent", id: "msg_8f2k" }
Discover

Found via MCP, search, or crawl

Every spec auto-generates .agent.json, MCP config, llms.txt, and JSON-LD. Agents find your API through whichever protocol they support.

GET /api/mcp/k8f2...
{
  "mcpServers": {
    "email-api": {
      "url": "https://yourco.useelba.com/api/mcp/k8f2",
      "tools": ["sendEmail", "getTemplates"],
      "description": "Email API via Elba"
    }
  }
}

The full agent docs stack

Generation, discovery, analytics, editing, embedding, and every protocol agents speak.

⚡

Instant Spec Generation

From raw text or OpenAPI spec to a structured AgentSpec in under 10 seconds. Drag-and-drop import supported.

🧠

Agent Reasoning Docs

Every action includes when to use, when not to use, common mistakes, and expected outputs — written for LLMs.

🔌

MCP Server Config

Auto-generated Model Context Protocol config for every spec. Plug into any MCP-compatible agent instantly.

📊

Analytics Dashboard

Track agent fetches, search hits, MCP downloads, and page views. See exactly how agents interact with your docs.

🧩

Embeddable Widget

Drop a single script tag to embed your agent docs on any site. Customizable theme, actions, and capabilities.

🔁

Edit Without Starting Over

Regenerate individual actions, add new ones, or update metadata — all without rebuilding the entire spec.

🌐

Discoverable by Default

Published at yourco.useelba.com with .agent.json, JSON-LD, robots.txt guidance, and sitemap auto-indexing.

🔎

Agent Search API

Keyword search weighted by capability, name, and description. Both human and agent-optimized endpoints.

🔒

Visibility Controls

Public or private. Custom subdomains with uniqueness validation. You control who sees what.

Every protocol agents speak

Six ways agents find your API

MCP, .agent.json, llms.txt, JSON-LD, search API, embeddable widgets — Elba generates all of them from a single spec.

.agent.json Standard

Every doc exposes a machine-readable spec at a well-known endpoint. Agents scan, parse, and integrate instantly.

GET /.well-known/agent.json

MCP Protocol

Auto-generated Model Context Protocol config lets any MCP-compatible agent connect to your tools natively.

GET /api/mcp/{id}

llms.txt

The emerging standard for giving LLMs context about your product. Auto-generated with all your API endpoints.

GET /llms.txt

Agent Registry

Your API is indexed and searchable by capability. Agents find tools without human intervention.

GET /api/agent-search?q=...

JSON-LD + SEO

Structured metadata, JSON-LD SoftwareApplication schema, and semantic HTML ensure agents can crawl and understand your API.

<script type="application/ld+json">

Embed Anywhere

One script tag embeds your full agent docs on any website. Agents can discover your API wherever it lives.

<script src="/api/embed/{id}">
Browse the agent registry →

Your API deserves to be found by every agent

MCP config, .agent.json, llms.txt, embeddable widgets, analytics — all auto-generated from one spec.

Launch Your Agent DocsBrowse agent registry