e-Boekhouden — can an agent use it?
e-Boekhouden has a functional SOAP API and a new REST API, but no official agent protocol, no status transparency, and no published rate limits. The cheapest upgrade: publish rate limits and a status page so agents can plan around constraints they currently cannot discover.
FIND & RETRIEVE · 6.3
ACT & TRANSACT · 3.9
TRUST & DURABILITY · 5.5
FIND & RETRIEVE6.3/10Can an agent get correct information?
Machine-readable surface6.5/10
Server-side rendered HTML with 1,061 words visible without JS. Valid sitemap with fresh lastmod, schema.org markup (Organization, Offer, FAQPage, BreadcrumbList, ContactPoint). robots.txt explicitly allows GPTBot, ClaudeBot, PerplexityBot, and Google-Extended. No llms.txt, no RSS/JSON feed, no markdown negotiation. source
Information retrieval quality7/10
Pricing clearly published at /prijzen (ZZP €4.98/mo, Standaard €7.25/mo, Standaard+Factureren €12.00/mo). Feature pages list all capabilities including 40+ integrations, bank connections, and VAT filing. Offer schema.org markup present with machine-readable prices. Some detail (API specifics, exact integration capabilities) requires deeper navigation. source
Documentation for machines5.5/10
SOAP API documented via a publicly downloadable PDF (English and Dutch versions) with WSDL at soap.e-boekhouden.nl/soap.asmx?wsdl listing 20 operations. A new REST API v1 is available at api.e-boekhouden.nl/scalar/ with OpenAPI spec. However: no visible changelog, no public error taxonomy, no per-field reference on the web (buried in PDF), and the REST API docs loaded only a Scalar shell without full spec content. source
ACT & TRANSACT3.9/10Can an agent do the job?
Action coverage5.5/10
SOAP API exposes 20 operations covering core bookkeeping: AddMutatie, AddFactuur, AddRelatie, AddGrootboekrekening, plus get/update variants for relations, ledger accounts, invoices, balances, and cost centres. Covers approximately 60-70% of UI actions. Missing: VAT filing, quote creation, bank connection management, document scanning, and deletion operations are UI-only. source
Agent protocol support3/10
No official MCP server or agent protocol from e-Boekhouden. Not in the official MCP registry. No .well-known/mcp.json or .well-known/skills. Zapier provides a third-party MCP surface with comprehensive coverage (create/update/find for invoices, mutations, relations, members, ledgers) but this is Zapier's wrapper, not an official e-Boekhouden product. Make.com has a community integration. source
Access & auth friction5/10
API credentials (username, security codes) are self-serve via the in-app settings panel (Beheer > Instellingen > API/SOAP). No enterprise gate or manual review. However: SOAP uses session-based auth (OpenSession) rather than API keys or OAuth, which is harder for agents to manage. No scoped or restricted credentials — it is all-or-nothing access. Requires a paid subscription first. source
Agent payment capability1.5/10
e-Boekhouden is a paid subscription SaaS (€4.98-€12.00/month). No support for any agent payment protocol (ACP, AP2, MPP, x402). Subscription payment is via standard web checkout only. An agent cannot programmatically subscribe, upgrade, or pay on a user's behalf. source
Cost & rate fairness4.5/10
API access is included in all plan tiers starting at €4.98/month — affordable and no separate API pricing. No evidence of agent traffic being priced differently from human traffic. However: no published rate limits whatsoever, no usage quotas, no documentation of throttling behaviour. An agent cannot plan around constraints it cannot discover. source
TRUST & DURABILITY5.5/10Will it still work next quarter?
Permission & ToS stance7/10
robots.txt explicitly allows major AI crawlers (GPTBot, ClaudeBot, PerplexityBot, Google-Extended) with partial access — only /nb (the app) and /admin are blocked. Terms of service contain no explicit anti-automation or anti-bot clauses. The existence of a publicly documented SOAP API implies programmatic access is expected and permitted. No hostile enforcement history found. source
Reliability & continuity4/10
No public status page — status.e-boekhouden.nl does not resolve. No programmatic status feed. SOAP API has been stable for years (third-party PHP and Node wrappers exist since at least 2022), and a new REST API v1 signals ongoing investment. But: no versioned API beyond 'v1', no public deprecation policy, no status transparency for programmatic consumers. An agent has no way to check if the API is currently operational before making calls. source
Sources
Point-in-time assessment — services change terms, prices and APIs often. That volatility is itself scored under Reliability & continuity. Re-verified at least quarterly.
- e-boekhouden.nl — home — features, positioning, customer count (500k+) (accessed 2026-08-18)
- e-boekhouden.nl/prijzen — pricing — three tiers, starter offer (accessed 2026-08-18)
- e-boekhouden.nl/robots.txt — robots — per-bot AI crawler policies (accessed 2026-08-18)
- e-boekhouden.nl/sitemap — sitemap — 60+ URLs, fresh lastmod (accessed 2026-08-18)
- e-boekhouden.nl/koppelingen — integrations — 12 categories including API (accessed 2026-08-18)
- e-boekhouden.nl/koppelingen/api — API page — REST v1 docs link, developer contact (accessed 2026-08-18)
- e-boekhouden.nl/functies/overzicht — features — full capability list (accessed 2026-08-18)
- e-boekhouden.nl/algemene-voorwaarden — terms — no anti-automation clauses (accessed 2026-08-18)
- soap.e-boekhouden.nl/soap.asmx — SOAP endpoint — 20 operations listed (accessed 2026-08-18)
- cdn.e-boekhouden.nl/handleiding/Documentation_soap_… — SOAP docs PDF (English) (accessed 2026-08-18)
- api.e-boekhouden.nl/scalar — REST API v1 docs (Scalar/OpenAPI) (accessed 2026-08-18)
- zapier.com/mcp/e-boekhoudennl — Zapier MCP — third-party agent protocol surface (accessed 2026-08-18)