Compare

Mercury vs Paddle

Paddle scores higher on the AgentReady, 83/100 against 81/100. They differ on 3 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Mercury. Mercury is a fintech company providing radically different banking for entrepreneurs, offering business banking, cards, expense management, payments, invoicing, and accounting in one platform.

Paddle. Paddle is a Merchant of Record platform for digital product businesses that manages payments, tax, compliance, and billing across 300+ markets.

Where Mercury is ahead

Mercury passes authentication documented, and Paddle does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.

It also holds operate: agent compatibility verified. Paddle misses it.

Where Paddle is ahead

Paddle passes structured api reference, and Mercury does not. That is understand, whether an agent can read the docs and work out how the API behaves before calling it.

What neither does

Both fail search discoverable, public docs discoverable, llms-full.txt / full agent docs, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk, canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution. If your agent needs any of those, you will be building it yourself either way.

Score, pillar by pillar

The AgentReady splits into four pillars, scored separately, because a product can be easy to find and still impossible to adopt.

Discover is whether an agent can find the product at all without being told it exists. Paddle leads 83 to 67. Mercury misses search discoverable, public docs discoverable, llms-full.txt / full agent docs; Paddle misses search discoverable, public docs discoverable, llms-full.txt / full agent docs.

Understand. Mercury leads 92 to 83. Mercury misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Paddle misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Paddle leads 100 to 88. Mercury misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk; Paddle misses no mandatory sales call, programmatic credential creation, fast time to first request, copyable quickstart, official typescript sdk, official python sdk.

Operate. Mercury leads 78 to 67. Mercury misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution; Paddle misses canonical workflow succeeds, structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, observable execution, agent compatibility verified.

Pricing

Mercury does not publish a machine-readable starting price and has a free tier. Paddle does not publish one and has a free tier.

Signal by signal

Which to pick

Mercury clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Mercury and Paddle. Alternatives to each: Mercury, Paddle.

An agent can fetch this as data: POST /v1/compare {"slugs": ["mercury", "paddle"]}