Comparison
actionlake vs Merge Agent Handler
Merge Agent Handler alternative for AI agents
Merge Agent Handler connects AI agents to 190+ MCP-ready connectors through scoped Tool Packs, scans every tool call with data-loss rules, and bills in credits spent per tool call, with Pro at $1,000 a month for 25,000 credits. actionlake is an MCP gateway with 995 vendor connectors, billed per upstream call, with spending caps per agent key, human approval before writes and one-call answers across two systems.
Checked 22 October 2026 · every fact links its source
Which to choose
It depends on the job.
Agent Handler is Merge's platform for connecting agents to enterprise tools over MCP. You create Registered Users and Tool Packs, end users authenticate through Merge Link, and a Security Gateway scans each tool call's arguments and responses with entity, regex and natural-language rules.
Choose Merge Agent Handler if
- You need data-loss rules that redact or block personal data in tool-call arguments and responses.
- You build an agent product whose end users connect their own accounts, and you already use Merge's Unified API.
- You need SOC 2 Type II, ISO 27001 and HIPAA from the vendor today, or on-premises deployment.
- You want to import public MCP servers into one governed catalog.
Choose actionlake if
- You want a spending cap per agent key and a person's approval before a write runs.
- You want a published price at 100,000 and 1,000,000 calls: Merge's Pro price above 25,000 credits is not shown.
- You ask one question across two systems and want the joined answer in one call.
- You want a free plan that runs in production: 100,000 calls a month, no card.
Credit where due
Where Merge Agent Handler is stronger
- Data-loss prevention: Merge scans each tool call and can allow, redact or block sensitive data. actionlake does not scan call data.
- Certifications: Merge states SOC 2 Type II, ISO 27001, HIPAA, GDPR and CCPA. actionlake holds none yet.
- Deployment: on-premises and private cloud on Enterprise. actionlake runs in one hosted region.
- Identity: SCIM provisioning with Okta, Azure AD and other identity providers.
The difference
Where actionlake differs
- Pricing: actionlake publishes the price for each volume; Merge publishes $1,000 for 25,000 credits and not the credits per tool call.
- Limits: actionlake caps spend per key and can hold a write for approval. The Merge pages we read describe scoping, rules and logs, not per-agent caps or approvals.
- Joins: actionlake's ask tool joins two systems on a shared entity and returns the answer, not the rows.
Feature by feature
15 things we compared.
Each Merge Agent Handler cell links the page we read it on. Checked 22 October 2026.
| Feature | actionlake | Merge Agent Handler |
|---|---|---|
| Hosted MCP server | YesOne endpoint, https://connect.actionlake.com/mcp, over Streamable HTTP; a REST API with the same behavior. | YesInstalls as an MCP server in Claude, Cursor, ChatGPT and other clients that support remote MCP.Source: merge.dev/agent-handler |
| How a client signs in | YesOAuth 2.1 with dynamic client registration and PKCE, or an actionlake key. The agent holds an actionlake key, never a vendor token. | YesEach Registered User authenticates through Merge Link; OAuth, API keys and custom auth to vendors; bring your own OAuth app.Source: docs.merge.dev/merge-agent-handler/overview |
| Apps and actions | Yes995 vendor connectors and 289,000+ actions behind eight tools. An agent can draft, test and sign a connector for an API that is missing. | Yes190+ MCP-ready connectors as of September 2026.Source: docs.merge.dev/merge-agent-handler/overview |
| What is billed | YesOne upstream call: a request actionlake sent to a vendor that returned a definitive response. Searching, checking, planning, cached answers and failures you did not cause (a vendor's 401, 403, 429, 5xx or a timeout) are free. | YesCredits, spent with each tool call. Credits per call are not stated.Source: merge.dev/pricing/agent-handler |
| Free allowance | Yes100,000 upstream calls a month, no card. | Yes2,000 credits a month, for prototyping and testing.Source: merge.dev/pricing/agent-handler |
| Limit which actions an agent can use | YesPer key: by action, by service, by verb, or read-only. A key can mint narrower keys, never wider ones. | YesTool Packs scope connectors by agent type, customer tier or environment; agents see the tools they can call.Source: merge.dev/agent-handler |
| Spending cap per agent key | YesA cap in upstream calls per key. A child key's calls count against each parent. Refused before the request is sent. | Not statedNot described on the pages read. Pro overages are billed at month end.Source: merge.dev/pricing/agent-handler |
| A person approves a write before it runs | YesDestructive actions need an explicit confirmation, and under the key's `human` policy the agent cannot give it, so a person approves. Approval rules make chosen actions, or every write, wait for a named person, who decides in the console or from an emailed signed link. | Not statedNot described on the pages read.Source: docs.merge.dev/merge-agent-handler/overview |
| Record of each call | YesOne ledger row per run, hash-chained and sealed daily, with the agent's stated reason (kept 90 days). Request and response traces are kept for the plan's window. | YesAudit logs on all plans with identity, arguments, downstream calls and outcome; SIEM streaming on Enterprise.Source: merge.dev/agent-handler |
| Scan call data for sensitive content | NoSecrets are removed from traces. Call data is not scanned or redacted for personal data. | YesEach tool call scanned with entity, regex and plain-English rules; allow, redact or block.Source: docs.merge.dev/merge-agent-handler/overview |
| One question across two systems | YesThe ask tool fetches from two or more systems, joins on a shared entity such as the customer, and returns the answer, not the rows. | Not statedNot described on the pages read.Source: merge.dev/agent-handler |
| Event triggers and webhooks | NoBy design. Agents and schedules start the work; a scheduled plan can ask what changed since the last run. | Not statedNot described on the pages read.Source: merge.dev/agent-handler |
| Self-host | NoHosted service only: actionlake runs in one region in Sydney, Australia, and no self-hosted edition is offered. | YesEnterprise: custom deployments including on-premises and private cloud.Source: merge.dev/pricing/agent-handler |
| Security certifications | NoNone held yet. SOC 2 Type II, ISO 27001 and a third-party penetration test are in progress. | YesSOC 2 Type II, ISO 27001, HIPAA, GDPR and CCPA, as stated by Merge.Source: docs.merge.dev/merge-agent-handler/overview |
| Where data is processed | YesOne region: Sydney, Australia (DigitalOcean syd1). Stored in Australia at rest; TLS terminates at Cloudflare's edge. | Not statedGuardrail regional scoping is configurable; processing region not stated.Source: docs.merge.dev/merge-agent-handler/overview |
"Not stated" means the vendor pages we read did not describe the feature. It is not a claim that the feature is missing. Checked 22 October 2026.
Pricing
What 100,000 and 1,000,000 calls a month cost.
Merge Agent Handler's unit: Credit, spent per tool call (credits per call not published). Plan used: Pro, $1,000 a month for 25,000 credits. actionlake's figure is the cheapest plan that fits the volume, from the published price book; one upstream call counts as one action.
| Calls a month | actionlake | Merge Agent Handler |
|---|---|---|
| 100,000 | US$0 a monthUS$0.00 per 1,000 callsFree: US$0 a month, 100,000 calls included. | Not publishedPro offers up to 100,000 credits a month, but prices above 25,000 credits are not shown.Source: merge.dev/pricing/agent-handler, read 22 October 2026 |
| 1,000,000 | US$219 a monthUS$0.22 per 1,000 callsPro: US$149 a month for 750,000 calls, plus 250,000 calls at US$0.28 per 1,000. | Not publishedEnterprise, custom pricing.Source: merge.dev/pricing/agent-handler, read 22 October 2026 |
Caveats
- At the one published point, Pro is $1,000 for 25,000 credits: $40 per 1,000 credits.
- If one tool call used one credit, 25,000 tool calls would cost $1,000. Merge does not state the credits per call.
How we priced it
- List prices on the vendor's own pricing page on the date shown, annual billing where the vendor offers it.
- The smallest plan or ladder step that covers the volume, plus published overage where that is cheaper.
- Each vendor bills a different unit. The unit is named on every row, and the conversion to one action or one tool call is stated.
- Where no public price covers the volume, the cell says so. Nothing is estimated from a sales quote.
actionlake's figures are the USD list. Searching the catalogue, checking a call, planning, cached answers and failed calls are not billed. See every plan on the pricing page.
Moving over
Migration notes
- If you depend on DLP rules for personal data in tool calls, keep that control in place; actionlake does not scan call data.
- Connect the same systems to actionlake once per tenant. OAuth systems need your own app registered with the vendor and one admin sign-in; key-based systems the agent connects itself.
- Turn each Tool Pack into an actionlake key: the allowed actions, a monthly cap, and approval for writes.
- Run both servers in the same MCP client while you compare results.
Questions
Asked about Merge Agent Handler and actionlake
How much does Merge Agent Handler cost?
Free includes 2,000 credits a month. Pro is $1,000 a month for 25,000 credits, with larger credit options whose prices are not shown, and Enterprise is custom (merge.dev/pricing/agent-handler, checked 22 October 2026). Merge does not state how many credits a tool call uses.
Does actionlake have DLP rules like Merge?
No. actionlake removes secrets from its traces but does not scan or redact personal data in call arguments or responses. It limits what an agent can do with scoped keys, spending caps and approvals instead.
Can actionlake be deployed on-premises?
No. actionlake runs in one hosted region in Sydney, Australia, and no self-hosted edition is offered. Merge offers on-premises on Enterprise.
What does actionlake add that Merge does not describe?
A spending cap per agent key, refused before dispatch; a person's approval before a write; and the ask tool, which joins two systems on a shared entity and returns one answer.
Sources
- Merge Agent Handlermerge.dev/agent-handler · read 22 October 2026
- Merge Agent Handler pricingmerge.dev/pricing/agent-handler · read 22 October 2026
- Merge Agent Handler documentationdocs.merge.dev/merge-agent-handler/overview · read 22 October 2026
We wrote these pages, so read them with that in mind. Each competitor is stronger somewhere, and each page says where. If a fact here is out of date, tell us at [email protected] and we will correct it.
Give your agent every system, with limits.
Start free - 100,000 calls/month, no card. No signup. Hard caps on every key. Cached answers are free.