Form backend for AI-generated sites

Forms your agent can wire up in seconds.
No database required.

Your agent builds the frontend. AgentsForms gives it a submission endpoint, validates the payload, stores the response, and emails the owner — no database or backend route required.

  • Agent-built frontend
  • Submission API
  • Email delivery
  • No database required
cli coding agent
$ agentsforms init
✓ Created forms/contact.json

$ agentsforms forms create contact \
--email founder@example.com
✓ Endpoint: api.agentsforms.com/v1/forms/contact/submissions

$ agentsforms codegen contact --target react
✓ Added ContactForm component
submission api
POST/v1/forms/contact/submissions sourcesite answers{ name, email, message } deliveryemail → founder@example.com
01 / build

Frontend form

Your coding agent builds the form UI inside the generated site.

02 / create

API endpoint

AgentsForms returns a submission endpoint for that form.

03 / post

Submission

The frontend POSTs answers to AgentsForms instead of your database.

04 / deliver

Email delivery

AgentsForms validates, stores, and emails the submission to the owner.

MVP1: remove form infrastructure

Your agent should build the frontend, not the form backend.

When a CLI agent spins up a site, the UI is easy. The painful part is storage, validation, email, routes, and deployment config. AgentsForms turns that backend into one endpoint.

Native forms in the generated site

Your coding agent keeps the form in your app’s design system instead of linking visitors to a generic hosted page.

components/ContactForm.tsx

Endpoint + email delivery first

MVP1 gives the frontend a safe place to POST and sends submissions to the owner’s inbox.

POST /forms/contact/submissions

Hosted URLs when you need zero UI

If the agent does not need a native frontend, it can still fall back to a hosted preview URL. Webhooks and sessions come later.

hostedPreviewUrl
Live demo

Keep the frontend. Skip the database.

This page is the MVP1 model: a native frontend form posts to AgentsForms, and the submission is delivered by email.

quickstart
$ agentsforms forms create contact --email founder@example.com
✓ Endpoint → api.agentsforms.com/v1/forms/contact/submissions

$ agentsforms codegen contact --target react
✓ Added native ContactForm component

$ git diff app/contact/page.tsx
✓ Frontend posts to AgentsForms
Try it live

Try the API-backed frontend.

This form is built into the page and posts to AgentsForms. Use a real email address to verify delivery.

Build / POST / Receive

A form backend for machines, not another dashboard.

AgentsForms gives coding agents the part they should not reinvent: a submission endpoint, validation, storage, and email delivery. The frontend stays in the generated app.

Build

The form UI lives in your app.

Your agent writes the component using the same design system as the rest of the generated site.

components/ContactForm.tsx
POST

The API receives submissions.

No database migration, server action, queue, or email provider. The browser posts answers to AgentsForms.

POST /v1/forms/contact/submissions
Receive

Submissions hit your inbox.

Email delivery is the default MVP path. Add hosted URLs and signed webhooks later when you need more automation.

Delivery: email → you@example.com

Give your agent a form backend.

Let it build the frontend. AgentsForms handles the endpoint, validation, storage, and email delivery.

$ agentsforms forms create contact --email you@example.com