GoCardless alternatives
The highest-scoring alternative to GoCardless is Paddle at 83/100 on the AgentReady, against 61/100 for GoCardless.
All scored in Payments & Billing.
What Paddle does that GoCardless does not
Paddle passes structured api reference, and GoCardless fails it. That is the whole of the gap between the two scores, so if none of those matter to your agent the ranking above overstates the difference.
Why people look for an alternative
GoCardless fails structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, no mandatory sales call, agent-compatible signup flow, programmatic credential creation, structured, predictable output, machine-readable errors, idempotency support, rate-limit behavior predictable, agent compatibility verified. Each one is a place an unattended run stops, which is usually what sends someone looking in the first place.
Where GoCardless loses the points
| Pillar | GoCardless | What it measures |
|---|---|---|
| Discover | 100 | Can an agent find it at all: sitemap, robots, structured data. |
| Understand | 31 | Is there a spec, an llms.txt, a machine-readable description. |
| Adopt | 70 | Signup, keys, SDKs, and whether a human has to be involved. |
| Operate | 44 | Rate-limit headers, errors, status, and behaviour under load. |
GoCardless is weakest on understand at 31/100. Without a spec an agent has to guess at endpoints, and it guesses wrong. If that is the part your agent depends on, take the ranking above seriously; if it is not, GoCardless may still be the right pick.
What an agent runs into with GoCardless
These are the findings from the last audit on 2026-09-01. Each one is a place unattended software stops, which is the practical reason to look at the list above.
- Publish an OpenAPI spec so agents can generate a client.
- Flesh out the OpenAPI: paths, schemas, and descriptions.
- Document error responses as an enum in your OpenAPI.
- Let agents create API keys programmatically.
- Return X-RateLimit / Retry-After headers so agents pace themselves.
- Add request examples to your API reference.
- Add response examples to your API reference.
- Support an Idempotency-Key so retries are safe.
What this category actually supports
Across the 18 products scored in Payments & Billing, accept a payment is offered by 39%, create a subscription is offered by 39%, meter usage is offered by 28%, merchant of record is offered by 17%. Anything under half is a gap you should expect to fill yourself whichever one you pick.
An agent can get this list directly: resolve("alternative to GoCardless") over the MCP server, or GET /v1/categories/payments.