Merge

Agents reach more than 190 prebuilt connectors through one MCP endpoint, including Salesforce, Slack, Jira, GitHub, HubSpot, NetSuite and Workday, with tool schemas normalized and descriptions written for models. Each end user authenticates once through Merge Link or a magic link, or a Group shares one set of credentials, and tokens stay encrypted until the moment a call goes out. Any MCP server a customer runs at a public address can be registered as a custom connector and served through the same endpoint, and Enterprise adds connectors Merge builds to order.

Sourcedocs.merge.dev/merge-agent-handler/overviewread 2026-11-09

Merge serves one tool call or one model request at a time and runs no workflow of its own. The agent loop, the order of steps and any handoff between agents stay in the customer's runtime, which calls Agent Handler over MCP and Gateway over an OpenAI or Anthropic compatible API. Gateway's routing policies choose which model serves a request and fail over between providers, and Workforce skills hand employees' agents shared written procedures, but neither sequences or branches multistep work.

Sourcedocs.merge.dev/merge-agent-handler/overviewread 2026-11-09

The Unified API keeps a synced, normalized copy of a customer's records, files and knowledge base articles from connected HR, CRM, ticketing, file storage and knowledge base systems, refreshed on a schedule that runs from quarterly up to the highest setting and queryable through one schema per category.

An AI product can ground answers on that store without calling each system, and incremental sync keeps it current. Merge builds no search index or embeddings over it, so retrieval and ranking happen in the customer's own pipeline, and the Universal Context Layer is announced on the marketing site only.

Sourcedocs.merge.dev/llms.txtread 2026-11-09

Controls set what an agent can do rather than holding its calls for a person. Tool Packs fix which connectors and tools each agent surface reaches, input overrides hide, force or constrain fields, and the Security Gateway allows, redacts or blocks personal, health, payment and custom pattern matches. AI Guardrails judge plain English rules, such as no mention of a confidential project, on requests and responses and block or log each match, and per user rate limits cap runaway calls. No step routes a tool call to a reviewer for approval before it runs.

Sourcedocs.merge.dev/merge-agent-handler/secure/ai-guardrailsread 2026-11-09

Dashboard members get Admin, Developer, Security or Read Only roles, or custom roles built from read and write permissions per resource, and sign in through SAML single sign on with SCIM provisioning and multifactor authentication. End users are isolated by user scoped access keys, so one user's agent cannot call tools as another. Merge holds SOC 2 Type II, with reports under NDA, and ISO 27001, supports HIPAA and GDPR, and encrypts stored credentials with AES 256, decrypting them only at the moment of injection.

Sourcedocs.merge.dev/merge-agent-handler/administer/team-and-rolesread 2026-11-09

Every tool call lands in a log with its arguments, result, latency broken into auth, scan, dispatch and third party time, the end user it ran for, any redaction applied and any error, filterable by user or tool. API request logs sit beside it, an audit trail records admin changes such as role and plan switches, and guardrail violations appear in alerts linked to the call. Webhooks fan events to the customer's pipeline, Enterprise streams logs to a SIEM, and Gateway attaches a cost to every response.

Sourcedocs.merge.dev/merge-agent-handler/overviewread 2026-11-09

Tool calls through Agent Handler are stateless, results are never cached, and nothing the agent learns is kept for a later session. What persists is records about the agent rather than memory for it: tool call logs held for 90 days by default, the audit trail, and stored end user credentials. Workforce skills are shared procedures people write for their teams' agents. Conversation state, user preferences and anything an agent should remember stay in the customer's own runtime and storage.

Sourcedocs.merge.dev/merge-agent-handler/resources/faqread 2026-11-09

Standard plans store tool call logs, credentials and configuration in encrypted databases on AWS US East. Enterprise contracts can pin data to the EU or APAC, run a single tenant instance, peer with the customer's VPC, or deploy Agent Handler and Gateway on premises or inside the customer's own cloud. The Unified API offers a self hosted option and a single tenant option for purchase and can land synced data in the customer's own environment, and region pinning is one of the terms an Enterprise contract sets.

Sourcedocs.merge.dev/merge-agent-handler/resources/faqread 2026-11-09

Merge ships the parts of an agent rather than agents. Tool Packs bundle the connectors and tools one agent surface may use, a preconfigured pack lets a new account make its first call, and AI Guardrails start from templates that prefill each rule. Workforce adds a shared skills library that teams write and publish for one another. No prebuilt agent, packaged workflow or ready made assistant comes in the box, so each team assembles its own from these pieces in its own runtime.

Sourcedocs.merge.dev/merge-agent-handler/overviewread 2026-11-09

Agent Handler acts only when an agent calls it, and its webhooks report events such as tool calls and alerts rather than starting work. Event delivery comes from the Unified API, whose Merge webhooks and third party webhooks tell the customer's endpoint when records change in a connected HR, CRM, ticketing or file system, so a team can use a new hire or a closed deal to start its own agent. Merge itself never wakes an agent, and Agent Handler has no schedule or inbound trigger of its own.

Sourcedocs.merge.dev/merge-unified/reading-data/webhooks/overviewread 2026-11-09

Gateway gives a team 270+ models from more than 20 families, including OpenAI, Anthropic, Google, Meta, Mistral, DeepSeek and Qwen, behind one base URL. The customer picks models directly or through routing policies selected by a model alias, ranked or learned, with failover on outages and rate limits, and Pro adds custom policies, its own provider keys and settings that let its customers choose their own models. Workforce limits each group to an approved list. Agent Handler works with any model whose runtime speaks MCP.

Sourcedocs.merge.dev/merge-gateway/routing/overviewread 2026-11-09

OpenAPI specifications cover the Agent Handler API, the Gateway API and its management and embedded routing APIs, and the Unified APIs for HR, recruiting, CRM, accounting, ticketing, file storage, knowledge base and chat, with official SDKs and a command line tool. Teams manage connectors, Tool Packs, registered users, access keys and usage over REST, the MCP endpoint takes OAuth sign in, and both Agent Handler and Gateway accept an unauthenticated signup call that creates an organization and returns a working key.

Sourcedocs.merge.dev/llms.txtread 2026-11-09

Testing centers on the safety rules and tool setup. The Rule Tester runs a sample input through the whole Security Gateway, streaming entity detections, guardrail verdicts and the block decision in order, with a library of payment, health, personal, secret, financial and legal samples plus a benign control, and the Playground makes test tool calls. Test API keys and sandboxes for third party platforms let a team try integrations before launch. Nothing scores an agent's answers or compares one agent version against another.

Sourcedocs.merge.dev/merge-agent-handler/secure/rule-testerread 2026-11-09

Merge never puts an agent in front of a browser, desktop or remote computer. Every action goes through an API: connectors call each third party's own endpoints with the end user's credentials, passthrough requests reach endpoints the common schema does not cover, and custom MCP servers extend the catalog. For a system with no API, a team needs a separate browser automation product, since Merge offers no hosted browser or screen control of its own.

Sourcedocs.merge.dev/merge-agent-handler/overviewread 2026-11-09