Skip to content

Agentic managed forms

Forms your people fill in.
Forms your agents build and manage.

Send a link. Anyone opens it on a phone, fills it in, adds photos, and signs. A PDF lands in the inbox. The same form is open to an AI agent through the API.

Free to start. No card. Nothing to install.

Made for a phone, anywhere

One screen at a time. Photos are resized in the browser before they upload, so a weak signal still works. A signature is drawn with a finger. The person filling it in never signs in.

A PDF and an email, every time

Each submission prints to a PDF and goes to the people that form routes to. A failed send is retried and shown in the app, not hidden. Screen and paper come from one renderer, so they cannot drift.

Open to agents from day one

An API key reads your forms, builds new ones, and files submissions. An MCP server puts the same tools in front of an assistant. Every record says whether a person or an agent sent it.

How it works

  1. 1

    Build the form

    Drag blocks onto the page, or describe the form in a sentence and let the builder draft it.

  2. 2

    Share the link

    Send a URL or a QR code. It opens on any phone with no app and no login.

  3. 3

    Get the PDF

    Each submission is filed, printed to PDF, and emailed to the right people.

Runs on Cloudflare's network, close to your users everywhere.

Use cases

One product, many jobs. Start from a shape that is close and change it.

For agents

Two doors. One form.

Every form publishes its own contract: the fields, the rules, and an example request. An agent reads it, submits with an idempotency key, and gets the PDF link back. Keys are scoped. A submit key can file. An admin key can build.

  • REST with OpenAPI 3.1 and llms.txt on every workspace
  • MCP server with the same tools an admin has
  • Signed webhooks on every submission
  • Field errors that name the field, not a wall of text
POST /v1/forms/field-inspection/submissions
// Any agent with a key can read the contract and file a submission.
const r = await fetch("https://acme.lazerforms.com/v1/forms/field-inspection/submissions", {
  method: "POST",
  headers: { Authorization: "Bearer ifk_submit_…", "Content-Type": "application/json" },
  body: JSON.stringify({
    values: { area: "Level 3 east wing", faults: "Handrail loose at the stair head." },
    idempotency_key: "run-4821",
    agent: { name: "Claude" }
  })
});
// 201 { id, pdf_url, email_status: "sent" }
Or connect an assistant over MCP at https://acme.lazerforms.com/mcp. Same tools, same keys.

Plans

Prices in USD a month. Local taxes may apply. Change or cancel yourself, any time.

Free

Free

One team, a few forms, and real email on every submission.

  • 3 forms
  • 100 submissions a month
  • 1 GB of photos and PDFs
  • 1 API key
  • PDF and email on every submission
Start on Free

Business

$99a month

For a business with many crews, many sites, and an IT team.

  • Unlimited forms
  • 50,000 submissions a month
  • 200 GB of photos and PDFs
  • Unlimited API keys
  • Outbound webhooks
  • AI form drafting
  • Single sign-on
Start on Business

Questions

What is Lazer Forms?

Lazer Forms is a hosted form builder for teams and for AI agents. You build a form, share a link, and anyone can fill it in on a phone with no app and no login. Every submission is stored, rendered to a PDF, and emailed to the people that form routes to. The same form is also a JSON API that an agent can read and submit to.

Do the people filling in the form need an account?

No. A form is a public link, so anyone you send it to can open it and fill it in. Only the people who build forms and read submissions need to sign in. That is what makes the link work for a contractor, a customer, or a visitor you have never met.

Does it work on a phone with a weak signal?

Yes. The form is one screen at a time and the pages are small. Photos are resized in the browser before they upload, so a large camera image does not have to travel at full size. A signature is drawn with a finger on the same screen.

Do I get a PDF of each submission?

Yes. Every submission is printed to a PDF and emailed to the recipients set on that form. The screen and the PDF come from one renderer, so what a person filled in is what the paper shows. A failed send is retried and shown in the app rather than hidden.

Can an AI agent fill in one of my forms?

Yes. Each form publishes its own contract with every field, its type, whether it is required, and an example request. An agent sends an API key as a bearer token, posts the values, and gets the submission id and the PDF link back. Every record says whether a person or an agent sent it.

Can I connect it to Claude or another assistant?

Yes. Every workspace runs an MCP server with the same tools an admin has, so an assistant can list forms, read a contract, build a form, and file a submission. It uses the same API keys as the REST API. There is also an OpenAPI 3.1 spec and an llms.txt on every workspace.

How do API keys and permissions work?

Keys are scoped. A submit key can file submissions and nothing else. An admin key can build and change forms. You create, name, and revoke keys yourself on the API keys screen, and each one is listed against what it did.

Where is my data stored?

Everything runs on Cloudflare's network, so the form loads close to the person filling it in wherever they are. Submissions are stored in Cloudflare D1 and photos and PDFs in Cloudflare R2, in the region this deployment is configured for. You can delete a workspace yourself from the settings screen, which removes its forms, submissions, and files.

Set up a workspace in a minute.

Build your first form, send the link, and watch the PDF arrive.

Create your workspace