RXed AI News

AI to the bone.
SCORE 5/10 10/10 criteria · Capable, with friction Assessed 2026-09-03 · ARI rubric v1.0

Yuki (now Nmbrs) — can an agent use it?

Visit yuki.nl
“Yuki was a Dutch/Belgian SMB bookkeeping platform, now fully merged into Nmbrs (Visma Group). Nmbrs provides invoicing, accounting, payroll, and HR software for 501K+ Dutch businesses and accountants.” — the vendor’s own words

Yuki's absorption into Nmbrs delivers a real REST API with OAuth and sandbox, but the agent surface is immature — no official MCP, no llms.txt, no agent payment path, and pricing is hidden behind 'contact sales' for the payroll/accounting core. The community Pipedream MCP wrapper covers HR/payroll but not accounting.

Category
Accounting
Agent protocol
Community only
Agent payment rails
None published
Site Scan
C (68/100) · crawl-level, 03/09
Tap or hover any criterion to see why it scored that.
FIND & RETRIEVE5.5/10Can an agent get correct information?

Machine-readable surface5.5/10

Sitemap present and fresh. Clean HTML with FAQPage JSON-LD. No llms.txt, no markdown negotiation, no RSS feed. Multiple H1 tags. The redirect from yuki.nl to nmbrs.com is clean (HTTP 200) but the original brand domain no longer hosts content. source

Information retrieval quality4/10

Invoicing pricing is published clearly (€6.50–€26.50/mo with add-ons). But the core accounting and payroll products — which is what Yuki customers use — require 'Brochure aanvragen' (request brochure) or 'Maak een afspraak' (book a meeting). An agent cannot answer 'what does Yuki/Nmbrs accounting cost?' without guessing. source

Documentation for machines7/10

REST API reference at nmbrs.stoplight.io with authentication guide and endpoint specs. Developer portal at developer.payroll.nmbrs.com for OAuth credential management and scope configuration. SOAP API documented separately with production and sandbox endpoints, but deprecated (retiring 2027). Concrete getting-started path exists. source

ACT & TRANSACT4.2/10Can an agent do the job?

Action coverage6/10

REST API covers HR and payroll operations (the Nmbrs Payroll core). 100+ partners are connected via the developer platform. However, the accounting/invoicing modules — the original Yuki product — have no documented API surface. An agent can read/write payroll but not bookkeeping entries. source

Agent protocol support3/10

A community MCP server exists via Pipedream (mcp.pipedream.net/v2), listed on awesome-mcp-servers. It exposes Nmbrs HR/payroll operations. No official MCP from Visma/Nmbrs. The server covers HR/payroll — not accounting, which is what the original Yuki queue entry is about. source

Access & auth friction6.5/10

OAuth credentials via developer portal. Partners can register, configure access scopes, and manage credentials self-serve. Sandbox endpoint available (api-sandbox.nmbrs.nl). However, the developer portal requires a partner registration step — not instant API key issuance. source

Agent payment capability1/10

No agent payment protocol support (no ACP, AP2, MPP, x402). No documented programmatic checkout or spend-capped billing API. Nmbrs is a subscription service paid by the business, not a transaction platform — but even subscription management lacks a programmatic path. source

Cost & rate fairness4.5/10

Invoicing tier pricing is published and reasonable (€6.50–€26.50/mo). No documented API rate limits. No agent-specific pricing or penalties. But the core accounting/payroll pricing is hidden ('request brochure'), and the API pricing model for partners is not public. source

TRUST & DURABILITY7.0/10Will it still work next quarter?

Permission & ToS stance7/10

Robots.txt allows all agents with only HubSpot CMS preview paths blocked. No AI-bot-specific blocks (no GPTBot, ClaudeBot, etc. disallows). Terms page exists but renders as Nmbrs legal — no explicit anti-automation clauses visible. Developer portal implies automation is expected. source

Reliability & continuity7/10

Public status page at status.payroll.nmbrs.com with component-level monitoring (Web App, Sandbox, API, Mobile, plus product modules). Atom/RSS/JSON programmatic status feeds. Recent incidents documented and resolved transparently. Part of Visma Group (large Nordic software conglomerate). SOAP API deprecation announced with clear 2027 retirement date — responsible timeline. 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.