Merge indexes at apis.io/providers/merge/ with 118 APIs and 117 API specifications, a Kin Score of 75.3 (exemplar), and an Agent Readiness score of 63.5 in the agent-native band.
Merge describes itself as the connective infrastructure for production AI: one API surface across HRIS, ATS, CRM, accounting, ticketing, file storage, chat, and knowledge base.
What’s in the surface
Ten named collections, and they are unusually legible because each is a category rather than an endpoint group:
- Accounting — ledgers, invoices, payments
- ATS — applicant tracking
- CRM — contacts, opportunities, accounts
- HRIS — employees, payroll, time off
- Ticketing — issues and support workflows
- File Storage — documents across providers
- Chat — messaging platforms
- Knowledge Base — help content
- Agent Handler — the AI-facing surface
- API Overview / Gateway — the umbrella
The unified-API bet
Merge’s product is a normalization layer. Instead of integrating Workday and BambooHR and Personio separately, you integrate Merge’s HRIS API once and it maps each underlying system into a common model.
That bet has a specific consequence for the catalog: Merge’s API surface is a published data model for eight software categories. The HRIS API is effectively an assertion about what an employee record universally contains. Getting that abstraction wrong is the whole business risk, which is why the specifications are complete — the model is the product, and an under-described model is an unusable one.
The 75.3 exemplar score reflects that. So does the near-1:1 API-to-specification ratio.
Agent Handler is the notable surface
The Agent Handler collection is the newest and the most strategically interesting. Merge’s original pitch was to human developers building integrations. Agent Handler is a surface aimed at AI systems that need to reach into a customer’s business software.
That is a coherent extension of the thesis. An agent trying to read employee records across a customer base faces exactly the fragmentation problem Merge already solved — except an agent cannot read integration docs and write a per-vendor adapter. Unified APIs are arguably more valuable to agents than to the developers they were built for.
The 63.5 agent-readiness score against a 75.3 composite suggests that transition is underway rather than finished.
The category comparison
This week’s workflow-automation piece found that companies who consume APIs for a living describe their own well. Merge is the strongest form of that argument: its entire business is consuming other people’s APIs, and it lands in the exemplar band.
Takeaway
118 APIs, 117 specifications, eight normalized software categories, and an emerging agent surface. Merge’s score is what happens when your published data model is your product — you cannot under-describe it without breaking the thing customers pay for.
Browse it at apis.io/providers/merge/.