Merge.dev alternatives for agent integrations in 2026

Your agent needs the Greenhouse offer status for one candidate. The synced candidate object has a name, a job, and a stage. The offer status lives on a Greenhouse field the common model does not use. The user asked a question the normalized record cannot answer.

This post shows what Merge's linked-account price buys, and what to do when the agent needs the provider's own field.

What a linked account costs

Merge Unified is one API over many customer systems. Categories include ATS, HRIS, CRM, accounting, and others. The ATS integration list includes Greenhouse, Lever, Ashby, iCIMS, and Workday.

On the October 2026 unified pricing page:

• The first 3 production Linked Accounts are free.
• $650 a month covers up to 10 production Linked Accounts.
• Each production Linked Account after that is $65.
• Professional and Enterprise are contract priced. Professional lists custom fields, field-level scopes, and custom sync frequency. Enterprise lists an audit trail and support SLAs.
• Launch rate limit is 100 requests a minute per Linked Account. Professional is 400. Enterprise is 600.

A Linked Account is one customer connection to one third-party platform. Ten customers on Greenhouse are ten accounts, even though you wrote one integration. Sync frequency on Launch can be quarterly, monthly, daily, or Merge's highest setting. The data the agent sees can be hours old if you chose daily.

That price is for a product integration: your app shows each customer's ATS inside your UI. It is an awkward price for one internal agent that calls your own Greenhouse a few hundred times a day. You would pay the account fee, then still wait on the sync.

Where one schema is the right cut

Use Merge when you are a B2B product and each customer brings a different ATS or HRIS.

You build against Candidate, Application, and Job once. Merge handles auth, pagination, and a large share of the connector maintenance. Field-level scopes on Professional let you limit which common fields a connection may use. That is the right control when the risk is "sync too many columns," not "the model invented a write."

How unified APIs fit B2B SaaS compares this shape with other unified vendors. Managed OAuth for agents is the piece to read if the hard part is the customer login, not the schema.

Leave Merge in place for those product syncs. Do not force an internal agent through a daily sync so it can read one live field.

When the agent needs the provider field

The common model drops names the ATS invented. Merge's pricing page lists Remote Data and Authenticated Passthrough so you can reach data the common model skipped. Use those when you are already a Merge customer and one field is missing. You still go through Merge, and you still hold a Linked Account.

Use a direct method when the agent must call the provider now, with the provider's own parameters, and you want a rule on those parameters.

Swytchcode does not replace Merge's sync. It runs the call you enabled. After swy get, swy list methods prints canonical IDs from that bundle. You add the one read you need. A policy can block a write even if the model asks for it. On the October 2026 pricing page, allow and deny are on every plan, including Free at 100 live commands a month. Approval starts on Business at $149 a month. Multi-tenant OAuth is the matching problem if each of your customers connects their own ATS. Connected end users are 10 on Free, 1,000 on Pro, and 10,000 on Business.

If swy search does not list that ATS, say so in the design. Do not invent a method ID to fill the gap. Business can bring your own provider. The ID still has to come from the bundle you installed.

Allow one method instead of the whole ATS

Follow this step to install the CLI. Use one of these.

npm install -g swytchcode

irm https://cli.swytchcode.com/install.ps1 | iex

curl -fsSL https://cli.swytchcode.com/install.sh | sh

Confirm the install, then start the project.

swy --version
swy init

Search with the provider name. Download the bundle only if the search returns it. Add the single read. Skip offer, stage, and reject methods. Read the inputs before you let an agent send them.

swy search <provider>
swy get <name from search>
swy list methods
swy info <canonical_id from swy list methods>
swy add <canonical_id from swy list methods>

Connect the provider. There is no .env file in this project. Swytchcode keeps credentials in its own local store and reads them when a call runs.

swy auth connect <provider>
swy policy validate

Keep Merge for the product sync your customers expect. For the one provider field the common model skipped, enable that method and refuse the writes beside it.

Related reading

• Policy as code. Block the write even if the read is allowed.
• Credential brokering. The provider key stays out of the model that asked for the field.
• Human approval on a tool call. Use this when the missing field is a write, not a read.
• Log every API call an agent makes. A daily sync and a live call leave different records.

FAQ

Is Merge $65 per API call?

No. The October 2026 Launch price is per production Linked Account: 3 free, $650 a month up to 10, then $65 for each additional account. Calls are rate limited per account. They are not the line item.

Can Remote Data replace a direct provider call?

It can return fields the common model dropped, through Merge, for an account you already link. It does not turn Merge into a live allowlist for an agent that chooses new methods. If you need the call now, and a policy on its body, call the provider method you enabled.

What if the ATS is missing from both Merge and the registry?

Do not fake the method name in a prompt. Check Merge's ATS list and swy search. If both miss it, you are writing that integration yourself, or bringing the provider on a Business or Enterprise plan. The policy file cannot guard a call you have not defined.

Does a daily sync meet an agent that is talking to a recruiter right now?

Often no. Launch lets you pick quarterly, monthly, daily, or the highest frequency Merge offers. A recruiter who just moved a stage will not see that change until the next sync. Read the live method when the conversation depends on the current stage.