← Leaderboard
7.9 L3

Xero

Ready Assessed · Docs reviewed · Mar 22, 2026 Confidence 0.56 Last evaluated Mar 22, 2026

Verify before you commit

Trust read first, source links second, build decision third.

Use this page to sanity-check Xero quickly. We surface the evidence tier, freshness, and failure posture here, then put the official links where you can actually act on them, especially on mobile.

Evidence

Assessed

Docs reviewed · Mar 22, 2026

Freshness

Updated 2026-03-22T18:18:47.929953+00:00

Mar 22, 2026

Failures

Unresearched

Coverage gap — not a clean bill of health

Score breakdown

Dimension Score Bar
Execution Score

Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability.

8.0
Access Readiness Score

Measures how easily an agent can onboard, authenticate, and start using this service autonomously.

7.6
Aggregate AN Score

Composite score: 70% execution + 30% access readiness.

7.9

Autonomy breakdown

P1 Payment Autonomy
—
G1 Governance Readiness
—
W1 Web Agent Accessibility
—
Overall Autonomy
Pending

Active failure modes

No failure modes have been captured for this service yet. An empty list is a coverage gap, not a clean bill of health.

Reviews

Published review summaries with trust provenance attached to each card.

How are reviews sourced?

Docs-backed Built from public docs and product materials.

Test-backed Backed by guided testing or evaluator-run checks.

Runtime-verified Verified from authenticated runtime evidence.

Xero: API Design & Integration Surface

Docs-backed

REST API at api.xero.com with JSON (default). Resources follow consistent URL patterns: /api.xro/2.0/{Resource}. Read supports filtering via where clause (Xero-specific query syntax), orderBy, and pagination via offset. Batch creates/updates via array POST bodies. CDC (change data capture) API for incremental sync — valuable for keeping agent state current. Webhook support for invoice and bank transaction events.

Rhumb editorial team Mar 22, 2026

Xero: Error Handling & Operational Reliability

Docs-backed

Validation errors returned with HTTP 400 and structured JSON listing each field error. Concurrency errors (HTTP 409) occur when records are modified simultaneously — agents should implement retry with exponential backoff. Rate limits: 5,000 calls/day per connection, 60 calls/minute burst. OAuth token refresh must be handled proactively (30-minute access token lifetime). Xero API reliability is high in practice; 99.9% SLA on enterprise plans.

Rhumb editorial team Mar 22, 2026

Xero: Comprehensive Agent-Usability Assessment

Docs-backed

Xero's API exposes the full accounting lifecycle: invoices (create, send, mark paid), bills, purchase orders, bank reconciliation, contacts, payroll (in supported regions), and financial reports. For agents, high-value use cases include: automated invoice creation from sales data, expense categorization from bank transactions, financial reporting summaries, and accounts receivable follow-up. OAuth2 auth with per-tenant tokens means one set of credentials covers one Xero organization; multi-org support requires managing separate token sets. Broad resource coverage makes Xero one of the most complete accounting APIs available. Confidence is docs-derived.

Rhumb editorial team Mar 22, 2026

Xero: Auth & Access Control

Docs-backed

OAuth2 authorization code flow with PKCE; access tokens expire in 30 minutes, refresh tokens in 60 days. Per-tenant token model: each Xero organization the user connects is a separate tenant with its own token, requiring xero-tenant-id header on every call. Scopes cover accounting, payroll, files, assets, and project APIs. PKCE requirement adds security for public clients. Token management complexity is well-documented with step-by-step guides.

Rhumb editorial team Mar 22, 2026

Xero: Documentation & Developer Experience

Docs-backed

developer.xero.com has thorough documentation: OAuth2 guide, API reference organized by resource type, SDKs for Node.js, Python, .NET, and PHP, and a developer sandbox with pre-loaded data. The OAuth flow is well-explained with step-by-step guides. Error handling docs cover validation errors and concurrency conflicts. Rate limits are clearly documented. Xero developer community (forum, Slack) is active.

Rhumb editorial team Mar 22, 2026

Use in your agent

mcp
→ get_score ("xero")
● Xero 7.9 L3 Ready
exec: 8.0 · access: 7.6

Trust shortcuts

This score is documentation-derived. Treat it as a docs-based evaluation of API design, auth, error handling, and documentation quality.

Read how the score works, how disputes are handled, and how Rhumb scored itself before launch.

Overall tier

L3 Ready

7.9 / 10.0

Alternatives

No alternatives captured yet.