# Overview

The BeeL. developer ecosystem — REST API, SDKs, CLI, n8n node, MCP server, Claude Code plugin and machine-readable docs, all deriving from one OpenAPI contract.

Every way to work with BeeL. speaks to the **same REST API** and derives from the
**same OpenAPI contract**, so the surfaces use the same names, fields and rules.
Each tool is built from the contract as it stood at its release: update it to pick
up what the API added since. Pick the one that fits how you build.

<Cards>
  <Card title="REST API" href="/api/openapi">
    The contract everything derives from. HTTPS + JSON.
    Generate a typed client from the OpenAPI spec for any language.
  </Card>

  <Card title="Node / TypeScript SDK" href="/sdks/node">
    Fully-typed client with retries, idempotency and webhook verification built in.
    The fastest path in a JS/TS backend.

    `npm install @beel_es/sdk`
  </Card>

  <Card title="CLI" href="/cli">
    Drive the API from the terminal and scripts — invoices, NIFs, docs search,
    sandbox verification. Commands derived from the OpenAPI spec.

    `npx @beel_es/cli`
  </Card>

  <Card title="n8n node" href="/n8n">
    Issue invoices from automation workflows without writing requests: 75 operations
    in dropdowns, plus a trigger for BeeL. events. Verified by n8n.

    `n8n-nodes-beel`
  </Card>

  <Card title="MCP server" href="/mcp">
    Hosted Model Context Protocol server: gives an AI agent live invoicing tools plus
    docs search over OAuth — no API key to paste.

    `claude mcp add --transport http beel https://mcp.beel.es/mcp`
  </Card>

  <Card title="Claude Code plugin" href="/claude-code">
    The `beel-api` plugin bundles integration skills — implement, webhooks, multi-NIF,
    audit, upgrade — and connects the hosted MCP.

    `/plugin install beel-api@beel`
  </Card>

  <Card title="AI-readable docs" href="/llms.txt">
    Published as `llms.txt` and `llms-full.txt`, the standard machine-readable index.
    Point any agent at them to ground answers in the current contract.
  </Card>
</Cards>

## Which one should I use?

- **Building a backend integration** → the [Node / TypeScript SDK](/sdks/node), or
  generate a typed client from the [OpenAPI spec](/api/openapi) for any other language.
- **Scripts, CI or quick checks** → the [CLI](/cli).
- **An AI agent that acts on BeeL** → the [MCP server](/mcp) — OAuth in the browser,
  no API key to paste.
- **Coding with Claude Code** → the [`beel-api` plugin](/claude-code): integration
  skills plus the MCP, in one install.
- **Automating without code** → the [n8n node](/n8n), when the invoice starts from a form,
  a CRM or a schedule rather than a Stripe charge.

<Callout type="info">
  These docs are also published as [`llms.txt`](/llms.txt) and
  [`llms-full.txt`](/llms-full.txt) — the machine-readable index. Point any agent
  at them to ground its answers in the current contract; the hosted MCP already does.
</Callout>

---

Full OpenAPI spec: https://docs.beel.es/api/openapi