Form backend glossary

A public token (= the form ID) that authorizes submissions — safe to commit client-side.

An automatic email FormLoom sends to the submitter after they fill out a form.

A secret token for the FormLoom management API — reading submissions, managing forms. Not the same as the public access key.

A development environment with an integrated LLM agent — Cursor, Claude Code, Windsurf, v0, Copilot.

A challenge-response test (reCAPTCHA, Turnstile, hCaptcha) that proves the submitter is human.

Downloading all form submissions as a comma-separated values file for analysis.

A form setting that rejects submissions unless the request comes from your allowed domains.

A hosted URL that accepts form POST requests and handles delivery, storage, and spam.

The practice of optimizing content to be cited by AI answer engines (ChatGPT, Perplexity, Claude, etc.).

A FormLoom MCP tool that returns framework-correct, copy-paste form code with a real provisioned key embedded.

A hidden form field that bots fill in and humans skip — the simplest, CAPTCHA-free bot filter.

A Next.js feature that serves a cached static page and regenerates it in the background when stale.

An architecture combining pre-rendered static sites with JavaScript enhancements and API services for dynamic features.

A root-level file that tells LLMs how to integrate with a service — the GEO-native version of documentation.

Form spam written by a large language model — grammatically correct, contextually plausible, hard for keyword filters to catch.

An extended version of llms.txt that inlines the complete code snippets for every framework.

A Model Context Protocol server that exposes tools AI coding agents can call to wire forms into a codebase.

The HTML form encoding type that allows file attachments alongside text fields.

A design pattern where the form ID is intentionally public and safe to commit — no secret involved.

The email API FormLoom uses to send notification and autoresponder emails.

A mechanism that caps how many requests a single IP or key can make in a time window — prevents abuse.

A 0–100 heuristic + AI score applied to every submission, where higher = more likely spam.

Structured data markup that tells search engines and AI crawlers what a page is about.

A Next.js App Router function marked `'use server'` that runs on the server and can be called from a form.

A website where all pages are pre-built as HTML files — no server code runs at request time.

A tool that builds a static website from templates and data at build time.

An email triggered by a user action (form submit) rather than a campaign — high deliverability is critical.

A POST request FormLoom sends to a URL you control when a submission arrives — for Slack, Discord, or custom automation.