Verify before you commit
Use this page to sanity-check Merge Api 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 21, 2026
Freshness
Updated 2026-03-21T03:48:00.093306+00:00
Mar 21, 2026
Failures
Clear
No active failures listed
| Dimension | Score | Bar |
|---|---|---|
| Execution Score Measures reliability, idempotency, error ergonomics, latency distribution, and schema stability. | 8.4 | |
| Access Readiness Score Measures how easily an agent can onboard, authenticate, and start using this service autonomously. | 8.1 | |
| Aggregate AN Score Composite score: 70% execution + 30% access readiness. | 8.3 | |
No active failure modes reported.
Published review summaries with trust provenance attached to each card.
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.
The unified API returns normalized data models per category — employee records look the same regardless of whether the underlying HRIS is Workday or BambooHR. The passthrough API allows agents to access provider-specific data that falls outside the normalized model. Merge's link flow handles the OAuth and credential collection for customer-facing integration setup without building per-provider OAuth flows.
Reliability is appropriate for a unified API layer. Merge sits between agents and the underlying SaaS providers — data freshness depends on Merge's sync frequency from each connected provider. Teams with real-time data requirements should verify the sync frequency commitments for their subscription tier, as unified APIs typically sync on schedules rather than in real-time.
Merge is a unified API platform that normalizes access to entire categories of B2B SaaS — HRIS (Workday, BambooHR, Rippling), ATS (Greenhouse, Lever, Ashby), CRM (Salesforce, HubSpot), accounting (QuickBooks, NetSuite), ticketing (Jira, Linear, GitHub Issues), and file storage (Google Drive, Dropbox, Box). A single Merge integration per category replaces per-provider integration maintenance across an entire vertical. For agents that need to read or write customer data across diverse B2B SaaS stacks, Merge eliminates the need to build and maintain per-provider connectors.
Authentication uses API keys for the server-side Merge API and access tokens scoped per linked account. The access token model ensures per-customer data isolation — agents use the customer-specific access token to scope requests to that customer's connected data. API keys should be stored as server-side secrets.
Documentation is thorough and covers the normalized data models, linked account management, and passthrough API clearly. The category-specific model documentation (HRIS, ATS, CRM) explains the normalized fields and their provider equivalents, which is essential for building reliable downstream logic. Teams adopting Merge for B2B integrations will find the documentation covers the common integration patterns well.
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
8.3 / 10.0
No alternatives captured yet.