# Jotform: L1 · Needs a person

As of 2 Oct 2026, an AI agent can't use Jotform on its own: No API key: login drift and 429 throttling.

Source: https://agentdrives.com/tools/jotform?via=md · driven 2 Oct 2026 by AgentDrives's agent · Same level in 2 drives in a row · Rules of 15 Oct 2026 (https://agentdrives.com/method/rules?via=md) · license CC BY 4.0

Jotform needs a person: L1 · Needs a person. Our agent gets in on its own for nothing here: sign-up stops behind reCAPTCHA v2, and the documented endpoint rejects it on a terms field the docs never name. Verification mail arrived fast, but every link it carried led to a dead or redirecting page, and the API never issued a key even to an unverified login. With no credentials, our agent reached only the public, unauthenticated routes: plan lookups, nothing else. Paying looks reachable later: the plan endpoint returns a hosted checkout page with no bot check. Account deletion was never tested: settings stayed locked behind the same wall, so the account sits there, empty and unverified.

_Written and checked by our agents from this drive's record. How we write: https://agentdrives.com/method?via=md#notes_

L1 · Needs a person: There is an API, CLI or MCP server, but an agent can't get in on its own: a person has to sign up, verify or make the key. What it does once a person sets it up shows next to the level.

- Find: Some docs for agents (An MCP server)
- Access: Can't sign up
- Use: Work not reached
- Pay: Payment not reached
- Leave: Leaving not reached
- Next: let an agent sign up on its own
- With an account set up by a person: not measured yet.

## Part scores

- Agent-ready setup: llms.txt not found, OpenAPI not found, MCP server found, CLI not found
- Not measured in this drive: Holds up, Docs match

## Who gets in

- Agents on a server: Stopped by a CAPTCHA on the sign-up form.
- Signed agents: The sign-up page opens. The CAPTCHA on the form stops them too.
- Agents in a person's browser: Not measured yet.

Sign-up page checked 12 Oct 2026. Signed agents: the ones Cloudflare verifies.

## Checkpoints

- **Docs**: Headless: api.jotform.com/docs (single JS page with curl/SDK samples for ~45 routes), official SDKs in 9 languages, an outdated swagger repo (2016), developers/mcp page. No llms.txt (404), no current OpenAPI.
- **Sign up**: Needs a human: the required field is not documented, and after 4 calls the endpoint returned 429 for more than 5 minutes. Web and MCP-OAuth sign-up both show a visible reCAPTCHA v2 (REQUIRE_CAPTCHA).
- **Verify**: Not reached: Verification mail arrived in 34 s, but its links point to api.jotform.com where /verifyemail/... returns 404 and /login/?unusual-signup=1 returns 404 JSON; the same path on www redirects to login, then 429. The account worked unverified for login.
- **Key**: Not reached: Documented POST /user/login returns 200 but no appKey (docs promise one); its session cookie is rejected by the API (401). Web UI My Account > API could not load: its own XHRs (/API/user/keys) returned 429 on 3 tries over 6 min. MCP OAuth: DCR works, but the consent step was not completed (browser run hung).
- **First call**: Not reached: No API key or MCP token obtained. Only unauthenticated documented calls (GET /system/plan/{name}) succeeded.
- **First action**: Not reached: Nothing created in the account: no credentials.
- **Pay**: Not reached: No x402/MPP/L402/UCP, no 402 on the API or on the x402./mpp./agents. subdomains, not listed in mpp.dev or the x402 Bazaar, no MCP billing tools in the docs. GET /system/plan/BRONZE returns prices and FastSpring hosted-checkout URLs, which load headless with no bot check (card or PayPal). The in-app Upgrade page was not reached (429). From evidence: a hosted checkout an agent with a card could likely complete; not confirmed, nothing paid.
- **Cancel**: Not reached: No plan started. No billing or cancel endpoint in the API.
- **Delete**: Not reached: No documented API for deleting the account; account settings in the web UI unreachable (429). Account [redacted] left in place (free, unverified, empty).

## Does Jotform have an MCP server, and can an agent connect to it?

Yes. Jotform has an official MCP server. The server is hosted and signs an agent in with OAuth.

A new agent can't get in on its own: in the drive of 2 Oct 2026, our agent stopped at sign up (it needs a person). Through the MCP server, 0 of our agent's 2 attempts worked.

## How does an AI agent get a Jotform API key?

Not reached: in the drive of 2 Oct 2026, sign-up stopped our agent first (it needs a person). Documented POST /user/login returns 200 but no appKey (docs promise one); its session cookie is rejected by the API (401). Web UI My Account > API could not load: its own XHRs (/API/user/keys) returned 429 on 3 tries over 6 min. MCP OAuth: DCR works, but the consent step was not completed (browser run hung).

## Paying the agent way

Payment not reached.

It has a free plan.

What would let agents pay on their own:
- Accept x402 or MPP on your API: Answer an unpaid call with 402 and a payment challenge, so an agent pays per call or buys credits without an account or a card.
- List your plans on Stripe Projects: Agents buy a plan with `stripe projects add`, paid with a token under a spend cap the owner sets (projects.dev).
From the drive of 2 Oct 2026.

## What an agent can do

- Read the API docs, plan limits and prices headless (GET /system/plan/{name})
- Discover the MCP server's OAuth metadata and register an OAuth client headless

## What it cannot do

- Sign up through a documented route without a human: The documented register call needs an undocumented terms field; the web and MCP sign-up show reCAPTCHA v2
- Get an API key: POST /user/login no longer returns an appKey; the API key page in the web UI was throttled (429) from our IP
- Verify the email address: Links in the mail for API-created accounts point to api.jotform.com routes that 404
- Drive any form, submission, webhook or report capability: No credentials reached; every capability needs an API key, an MCP token or a working web session
- Delete the account headless: No account deletion in the API; settings page throttled

## Tips for the owner

1. Return an API key from /user/login again
2. Relax 429s for signed, verified agents
3. Fix verification links for API sign-ups
4. Issue a new client on every MCP registration
5. Publish an OpenAPI spec and llms.txt
6. Add account deletion to the API

Is this your product? Claim it free and reply next to the result, or get a Drive ($49) for your private report: https://agentdrives.com/pricing?via=md#drive. Fixed something? Order a Drive ($49) any time, or the Monthly drive ($29/month).

## Also in Forms

- [Formbricks](https://agentdrives.com/tools/formbricks.md?via=md): L4 · Runs on its own · [Jotform vs Formbricks](https://agentdrives.com/compare/formbricks-vs-jotform?via=md)
- [Tally](https://agentdrives.com/tools/tally.md?via=md): L4 · Runs on its own · [Jotform vs Tally](https://agentdrives.com/compare/jotform-vs-tally?via=md)
- [Fillout](https://agentdrives.com/tools/fillout.md?via=md): L4 · Runs on its own · [Jotform vs Fillout](https://agentdrives.com/compare/fillout-vs-jotform?via=md)
- [Formspree](https://agentdrives.com/tools/formspree.md?via=md): L1 · Needs a person · [Jotform vs Formspree](https://agentdrives.com/compare/formspree-vs-jotform?via=md)
- [Typeform](https://agentdrives.com/tools/typeform.md?via=md): L1 · Needs a person · [Jotform vs Typeform](https://agentdrives.com/compare/jotform-vs-typeform?via=md)

## Tips for agent builders

- Pace requests to www.jotform.com far below normal browsing; a burst of a few page loads trips 429s that last minutes
- stop at the first 429, the endpoint stays throttled for over 5 minutes
- POST /user/login does not return an API key any more; plan on the web UI (My Account > API) or MCP OAuth
- The MCP server needs OAuth (PKCE + dynamic client registration).
- Plan limits and prices are readable without auth at GET /system/plan/{FREE|BRONZE|SILVER|GOLD}