Agent Readiness Signal Merge Well Known Catalog Example is an example object payload from Agent Readiness, with 12 top-level fields. It illustrates the shape of data this provider's APIs accept or return.
{
"id": "merge-well-known-catalog",
"provider": "Merge.dev",
"providerSlug": "merge",
"dimension": "well-known-catalog",
"score": 3,
"scoreLabel": "exemplary",
"evidenceUrl": "https://docs.merge.dev/.well-known/api-catalog",
"evidenceQuote": "{\"linkset\":[{\"anchor\":\"https://docs.merge.dev/merge-unified/hris\",\"service-desc\":[{\"href\":\"https://docs.merge.dev/openapi.yaml?api=897b64f3-1ddf-4bc9-ac5e-681a32145e06\",\"type\":\"application/yaml\"}]},{\"anchor\":\"https://docs.merge.dev/merge-unified/ats\",...},...]}",
"notes": "10 linkset entries — one per Merge Unified API category (HRIS, ATS, Accounting, Ticketing, CRM, File Storage, plus Marketing, Knowledge Base, Chat, Data Warehouse where present). Each entry points at a category-specific OpenAPI YAML. Deepest catalog observed in the survey — the model for how a multi-product provider should structure their catalog.",
"observedOn": "2026-05-22",
"observer": "API Evangelist",
"tags": ["merge", "unified-api", "rfc9727", "openapi", "well-known-catalog", "multi-product-catalog"]
}
Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. See our Privacy Policy and
Terms.