Compare

Fillout vs Formcarry

Formcarry scores higher on the AgentReady, 60/100 against 56/100. They differ on 4 of the 41 signals. Which ones decides whether an agent can adopt them without a person watching.

What each one is

Fillout. Fillout is an all-in-one form solution for creating forms, quizzes, and surveys.

Formcarry. Formcarry is a form backend (or form endpoint) that allows you to collect form submissions from your HTML or Javascript form with as minimum configuration as possible.

Where Fillout is ahead

Fillout passes no mandatory sales call, and Formcarry does not. That is adopt, whether an agent can get a key and make its first successful call without a human in the loop.

Where Formcarry is ahead

Formcarry passes authentication documented, and Fillout 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 adopt: programmatic credential creation and cli available. Fillout misses those.

What neither does

Both fail llms-full.txt / full agent docs, mcp discoverable, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, official python sdk, mcp integration available, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified. 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. Both sit at 80/100 here. Fillout misses llms-full.txt / full agent docs, mcp discoverable; Formcarry misses llms-full.txt / full agent docs, mcp discoverable.

Understand is whether an agent can read the docs and work out how the API behaves before calling it. Formcarry leads 46 to 38. Fillout misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Formcarry misses openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.

Adopt. Formcarry leads 65 to 60. Fillout misses programmatic credential creation, official python sdk, cli available, mcp integration available; Formcarry misses no mandatory sales call, official python sdk, mcp integration available.

Operate. Both sit at 47/100 here. Fillout misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Formcarry misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified.

Pricing

Fillout starts at $15/mo and has a free tier. Formcarry starts at $5/mo and has a free tier.

Signal by signal

Which to pick

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

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