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 whichever surface you pick stays consistent and never drifts. Pick the one that fits how you build.
REST API
The contract everything derives from. HTTPS + JSON, VeriFactu-compliant. Generate a typed client from the OpenAPI spec for any language.
Node / TypeScript SDK
Fully-typed client with retries, idempotency and webhook verification built in. The fastest path in a JS/TS backend.
npm install @beel_es/sdkCLI
Drive the API from the terminal and scripts — invoices, NIFs, docs search, sandbox verification. Commands derived from the OpenAPI spec.
npx @beel_es/clin8n node
Issue invoices from automation workflows without writing requests: 75 operations in dropdowns, plus a trigger for BeeL. events. Verified by n8n.
n8n-nodes-beelMCP server
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/mcpClaude Code plugin
The beel-api plugin bundles integration skills — implement, webhooks, multi-NIF,
audit, upgrade — and connects the hosted MCP.
AI-readable docs
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.
Which one should I use?
- Building a backend integration → the Node / TypeScript SDK, or generate a typed client from the OpenAPI spec for any other language.
- Scripts, CI or quick checks → the CLI.
- An AI agent that acts on BeeL → the MCP server — OAuth in the browser, no API key to paste.
- Coding with Claude Code → the
beel-apiplugin: integration skills plus the MCP, in one install. - Automating without code → the n8n node, when the invoice starts from a form, a CRM or a schedule rather than a Stripe charge.
These docs are also published as llms.txt and
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.