formcarry.com valid

formcarry

formcarry is one inbox for every form you run. A form posts its fields to its endpoint, `https://formcarry.com/s/{form_id}`, and formcarry stores the submission, emails it to the owner, filters spam and passes it on to webhooks, Zapier and the API. Any HTML page, React, Next.js, Vue or Svelte app, a Webflow, Framer, WordPress, Wix or Squarespace site, or a site an AI tool built can send to it. Accounts: https://app.formcarry.com/register. The endpoint is on the form's Setup page in the dashboard

For agents: Form backend service: point any HTML, React, Next.js or Webflow form to its endpoint to store submissions, email alerts, spam filtering, webhooks and API.

form-backendform-submissionsspam-filteringwebhookshtml-forms

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-21T03:48:00.136Z. Cached copy · Source on formcarry.com

# formcarry

> formcarry is one inbox for every form you run. A form posts its fields to its endpoint, `https://formcarry.com/s/{form_id}`, and formcarry stores the submission, emails it to the owner, filters spam and passes it on to webhooks, Zapier and the API. Any HTML page, React, Next.js, Vue or Svelte app, a Webflow, Framer, WordPress, Wix or Squarespace site, or a site an AI tool built can send to it. Accounts: https://app.formcarry.com/register. The endpoint is on the form's Setup page in the dashboard, https://app.formcarry.com.

## How to connect a form

Read this section before writing any code. It is the whole contract.

- Send a `POST` to the endpoint. A `GET` is answered with a page that says GET is not allowed.
- Accepted bodies: `application/x-www-form-urlencoded` (a plain HTML form), `multipart/form-data` (files), `application/json` (JavaScript). Up to 50 MB per request.
- Every field needs a `name`. formcarry stores the value under that name, as sent.
- Name the visitor's address field `email`. It becomes the reply to address of the owner's notification email and the recipient of the auto response.
- Reserved names, read and not stored: `_gotcha` (honeypot, leave it empty), `_next` (a redirect URL for one submission, paid plans, used only when the form's thank you URL in the dashboard is empty), `submit`, and the challenge tokens `g-recaptcha-response`, `h-captcha-response`, `cf-turnstile-response`.
- From JavaScript, send `Accept: application/json`. The answer is JSON with `code`, `status`, `title` and `message`, and the HTTP status equals `code`. Stored: `{"code":200,"status":"success","title":"Thank You!","message":"We received your submission"}`. `422`: a validation rule failed, `errors` holds one entry per failing field with a `message`. `403`: no fields, or the reCAPTCHA token was rejected. `400`: the hCaptcha or Turnstile token was rejected. `429`: a second submission within 15 seconds from the same IP address for the same form. `401`: wrong form id or a paused form.
- Without the `Accept` header the browser lands on formcarry's thank you page, or on the form's thank you URL when one is set in the dashboard.
- Files: send `multipart/form-data` (a `FormData` in JavaScript); a field can carry several files, each appended under its own name. From JSON, a data URL string is stored as a file, one key per file, never an array. Leave `Content-Type` to the browser when sending `FormData`. Files are stored on paid plans; the free plan stores the rest of the submission without them.
- Spam blocker: render reCAPTCHA, hCaptcha or Turnstile in the page and send its token under the field name above. The secret key goes into the form's settings under Form Security. Never post with an empty token.
- Post from the browser, not from a server. From a server every visitor shares one IP address against the 15 second limit, and no challenge token exists.

A plain HTML form:

```html
<form action="https://formcarry.com/s/{form_id}" method="POST
…

Related sites

Other listed sites in AI and machine learning. See the whole category →

Machine-readable: GET /v1/resolve?q=formcarry.com · GET /v1/domain/formcarry.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for formcarry.com:
1. POST https://agentwebmap.com/v1/sites/formcarry.com/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://formcarry.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/formcarry.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/formcarry.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.