COMPARISON

Arc0 vs Merge.

Considering Arc0 as an alternative to Merge Agent Handler? A like-for-like read on pricing, whose name your users see, catalog and deployment, including where Merge is still the better choice.

Per connected user vs per tool call · Your brand on every plan · Agents only
01 · SIDE BY SIDE

Arc0 and Merge, line by line.

ItemARC0MERGE
Pricing unitActive connected users, with 5,000 calls per user includedCredits: 1 credit per tool call
Entry pricingFree for 100 users; $99 a month for 1,000, then $0.10 → $0.03 per userFree 2,000 credits a month, then Pro from $1,000 a month
Failed and test callsNot billedUse credits
Your users’ consent screenYour logo on every plan; your domain and OAuth apps on paid plansMerge by default, unless you register your own OAuth apps
Catalog1,500+ apps, plus official MCP servers behind Arc0 auth~190 Merge-built connectors plus ~114 vendor MCP servers
DeploymentHosted; EU and dedicated hosting on ScaleAWS US-East; EU, VPC and on-prem on Enterprise
Audit log exportOpenTelemetry on paid plansSIEM streaming on Enterprise
MERGE DETAILS FROM THEIR PUBLIC PRICING AND DOCS · VERIFIED SEPTEMBER 2026
02 · FAIR IS FAIR

Where Merge is the better choice.

01THEIRS
Normalized data, not just actions

Merge’s Unified API syncs and normalizes HR, recruiting, CRM and accounting data into common models. Arc0 doesn’t do that, on purpose.

UNIFIED API
02+
HIPAA and ISO 27001

ISO 27001 and HIPAA on top of SOC 2 Type II, plus data-loss-prevention rules that scan tool inputs and outputs. If you need HIPAA or ISO 27001 today, Merge is ahead.

ENTERPRISE READY
03+
Track record

Merge has sold integrations to large companies since 2020, with implementation support to match.

MATURITY
03 · WHAT'S DIFFERENT

What Arc0 does differently.

01+
Pricing that grows with you

Build is free up to 100 active users in production. Launch is $99 a month for 1,000, then $0.10 or less per user, so cost grows with the users your agent serves.

PRICING
02+
Retries don’t cost you

Failed calls and development mode are free. Your bill tracks the users your agent serves, not how many steps it took.

PREDICTABLE
03+
Your name on the consent screen

White-label connect on your own domain on every paid plan, with your OAuth apps set up with you.

WHITE-LABEL
04+
Exportable tokens

Take your users’ tokens with you whenever you want, by API.

NO LOCK-IN
05+
Agents only

No unified API, no LLM router, no employee-AI suite. One product for one job, built around MCP from day one.

FOCUS
06+
One connection, two callers

The same connection serves your agent over MCP and your backend over REST, under one price.

MCP + REST
04 · IN THE PRODUCT

Every call your agent makes, on the record.

The audit log shows which agent acted, for which user, in which app and with which scope, and why each call was allowed, held for approval or blocked. It is on every plan, including free.

app.arc0.ai
The Arc0 audit log filtered to blocked calls and calls waiting for approval
05 · SWITCHING OFFER

Free migration from Merge.

An engineer moves you over at no charge, on any plan. You keep shipping while we do the work, and nothing changes for your users until you say so.

  1. 01We map itEvery app, action and auth config your agent uses in Merge, matched to Arc0.
  2. 02We set it upYour OAuth apps registered, Arc0 Connect in your brand, and your first policies written with you.
  3. 03We move your usersTokens imported wherever Merge lets you export them, and reconnects staged in-product where it doesn’t.
06 · SWITCHING

What moving from Merge looks like.

Agent Handler and Merge’s Unified API are separate products. If you rely on Unified for normalized HR or accounting data, keep it: Arc0 sits alongside it for agent actions.

Connections

If your connections use your own OAuth apps and you can export their tokens from Merge, they can move without a reconnect. Otherwise your users reconnect once, to your own branded connect flow, and we help you stage it in-product.

Your agent

Swap the MCP URL or the SDK calls. Actions are named by app and verb, like salesforce.update_record, each with a read, write or destructive scope. See the concepts.

07 · FAQ

Questions, answered.

Q01

Is Arc0 a good Merge Agent Handler alternative?

If you ship agents inside your product and want your brand on the connect flow, exportable tokens and per-user pricing, yes. If you need HIPAA or ISO 27001 today, or normalized data from Merge’s Unified API, Merge is the safer choice right now.

Q02

Does Arc0 have a unified API like Merge?

No. Arc0 gives agents and your backend authenticated access to each app’s real actions, rather than a normalized data model kept in sync. That keeps your users’ data out of our storage and avoids lowest-common-denominator schemas.

Q03

Can I use Arc0 and Merge together?

Yes. Teams that use Merge’s Unified API for data sync can use Arc0 for agent actions without changing the sync.

Q04

Is Arc0 SOC 2 Type II compliant?

Yes. Arc0 holds a SOC 2 Type II report, is GDPR compliant and signs a DPA. The report is shared on request under NDA.

Get started

Moving from Merge? We’ll move you.

Tell us where your connections live today and what your agent does. An engineer plans and runs the move with you, free, including how to keep reconnects to a minimum.