Join the waitlist

Manifest

Your form publishes a front door for software.

Real agents shake hands. Bots pick the lock. Every Endpoint Form publishes a manifest — a tool definition an agent can call directly — so software acting for a real buyer has a way in that isn’t pretending to be a browser.

What it is

Manifest is the machine-callable surface a form publishes alongside its human page — one tool definition, generated from the same form, that an agent can call directly.

Where this stands

Endpoint Forms is pre-launch, and this is the capability furthest from having a real user. It is a specification and a demo, not a shipped surface.

One definition · two surfaces

Demo request formIllustration

What a person sees

Work email · required

you@company.com

Company · required

Northgate

Monthly ad spend

$5k – $25k

What are you trying to fix?

Request a demo

What software sees

{
  "name": "demo_request",
  "description": "Request a demo of Endpoint Forms.",
  "input_schema": {
    "type": "object",
    "required": ["work_email", "company"],
    "properties": {
      "work_email": { "type": "string", "format": "email" },
      "company":    { "type": "string", "maxLength": 120 },
      "ad_spend":   { "enum": ["<5k", "5k-25k", "25k+"] },
      "problem":    { "type": "string" }
    }
  }
}

And what it gets back

{
  "status": "accepted",
  "submission_id": "sub_8f21",
  "origin": "agent"
}

Same fields, same required rules, same validation — because both sides are generated from the one definition, there is no second place for them to drift apart. The agent gets a structured answer instead of a re-rendered page with a red border.

Illustration of the two surfaces a single form definition publishes. Endpoint Forms is pre-launch — the tool definition here is drawn to show the shape of the contract, not copied from a running form.

How it works

  1. 01

    You build one form

    You do not author a separate API contract, and there is no second place for the two to drift apart. The manifest is generated from the same definition that renders the page — the same fields, the same validation, the same required rules.

  2. 02

    The form declares itself to software

    The manifest is a tool definition in the shape agents already read (MCP, and WebMCP in the browser). An agent can discover what the form wants without scraping the DOM and inferring it from label text.

  3. 03

    The agent submits and gets a real answer

    A structured submission gets a structured response — accepted, or rejected with the specific field and reason. Not a re-rendered page with a red border the agent has to interpret.

  4. 04

    The call is stamped Agent

    Because it came through the declared surface, the submission carries an Agent origin and goes to your CRM tagged as such. There is a real buyer behind a lot of agent traffic, and the point is to let those through cleanly, not to block them.

The problem it solves

Software already fills out your forms. Today it does so by driving a browser — which is exactly what a scraper does, which is why the only available defense is an obstacle course that punishes both. Legitimate automation and malicious automation are currently indistinguishable to your form, because neither one has a way to say which it is.

The obstacle course, meanwhile, does not work on the party you were worried about:

“Captcha can easily be bypassed… using a service such as 2captcha you could bypass captcha in like max 30 seconds.”
u/AndyAndrei63 · r/webdev, Jan 2025

Publishing a manifest inverts it. The honest party has an easier path than the dishonest one for the first time, and anything still stuffing the human page while acting like software has made a choice you can now see.

The full case, including the strongest arguments against it, is in the argument.

The catch

The honest limitation

Agent traffic is not a large share of your form fills today, and we are not going to pretend otherwise. Google announced WebMCP at I/O 2026 and shipped an early preview in Chrome Canary in February 2026. That is a preview, in one browser channel, in 2026.

The reason to build it now is that the provenance half pays for itself immediately regardless of agent volume — knowing which of last month’s submissions came from something that could not identify itself is useful today. The agent surface is the option you will want to already have, and we would rather say that than invent adoption numbers.

What Manifest doesn’t do

It is not the form-building MCP the other tools ship.
Tally, Jotform and Typeform have MCP servers, and all three are build-a-form surfaces for the person authoring the form. This is a fill-a-form surface for a buyer’s agent. Different job, opposite direction.
It does not authenticate the human behind the agent.
The manifest tells you software submitted and identified itself. It cannot tell you whose software. That is what makes Verdict necessary rather than optional.
It is not a way to submit your forms for you.
We publish the surface. We do not run agents, sell agent traffic, or fill anybody’s forms.

Waitlist

Nothing on this page is running yet.

Endpoint Forms is pre-launch. Leave your email and we’ll write once, when there’s something to look at — not a drip sequence about Manifest.