Fillout vs Jotform
Jotform scores higher on the AgentReady, 60/100 against 56/100. They differ on 11 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.
Jotform. Jotform is an online form builder that allows users to create professional-looking forms with no coding, featuring conditional logic, payment acceptance, report generation, and workflow automation.
Where Fillout is ahead
Fillout passes search discoverable and llms.txt published, and Jotform does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: structured api reference. Jotform misses it.
And on adopt, no mandatory sales call. Jotform misses it.
Finally, on operate, structured, predictable output. Jotform misses it.
Where Jotform is ahead
Jotform passes mcp discoverable, and Fillout does not. That is discover, whether an agent can find the product at all without being told it exists.
It also holds understand: authentication documented. Fillout misses it.
And on adopt, official python sdk, cli available and mcp integration available. Fillout misses those.
Finally, on operate, agent compatibility verified. Fillout misses it.
What neither does
Both fail llms-full.txt / full agent docs, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented, programmatic credential creation, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable. 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. Fillout leads 80 to 73. Fillout misses llms-full.txt / full agent docs, mcp discoverable; Jotform misses search discoverable, llms.txt published, llms-full.txt / full agent docs.
Understand. Fillout leads 38 to 31. Fillout misses openapi / spec quality, authentication documented, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented; Jotform misses structured api reference, openapi / spec quality, request examples provided, response examples provided, errors and status codes documented, limits / constraints documented.
Adopt is whether an agent can get a key and make its first successful call without a human in the loop. Jotform leads 80 to 60. Fillout misses programmatic credential creation, official python sdk, cli available, mcp integration available; Jotform misses no mandatory sales call, programmatic credential creation.
Operate. Jotform leads 56 to 47. Fillout misses machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable, agent compatibility verified; Jotform misses structured, predictable output, machine-readable errors, retry behavior documented, idempotency support, rate-limit behavior predictable.
Pricing
Fillout starts at $15/mo and has a free tier. Jotform does not publish one and has a free tier.
| Fillout plans | Jotform plans |
|---|---|
| Free $0/month | - |
| Starter $15/month | - |
| Pro $40/month | - |
Signal by signal
| Signal | Fillout | Jotform |
|---|---|---|
| AgentReady | 56 | 60 |
| Discovery | 80 | 73 |
| Understanding | 38 | 31 |
| Adoption | 60 | 80 |
| Operability | 47 | 56 |
| Public API | Yes | Yes |
| MCP server | No | Yes |
| OpenAPI spec | Yes | No |
| CLI | Unknown | Yes |
| llms.txt | Yes | No |
| Self-serve signup | Yes | Yes |
| Free tier | Yes | Yes |
Which to pick
Jotform clears more of the signals an agent needs, so it is the safer default for unattended use. Full profiles: Fillout and Jotform. Alternatives to each: Fillout, Jotform.
An agent can fetch this as data: POST /v1/compare {"slugs": ["fillout", "jotform"]}