---
name: formerize-forms
description: Build and integrate website contact, signup, waitlist, and lead forms with Formerize.
---

# Formerize forms

Build a form that matches the user's site with Formerize's shared form definition.

1. Inspect the site and choose the fields it needs.
2. Ask the owner to sign in at https://formerize.lansford.dev/auth/login and create an API key in the dashboard.
3. Read https://api.formerize.lansford.dev/openapi.json for current operations and the form schema.
4. Create or update an authenticated draft. Return its dashboard URL for review and publication.
5. After owner publication, install the returned submission URL or share the hosted link.

Keep API keys in server-side configuration or the agent's secret store. Never put them in public markup, logs, or commits.

MCP: `POST https://api.formerize.lansford.dev/mcp`, with `Authorization: Bearer <key>`. OAuth is not yet available.

API keys can prepare drafts and read delivery metadata. Publication, response content, and key management require the signed-in owner.

Use one versioned form definition across the builder, API, MCP, and renderer. Do not create an independent schema.

| Need | Read |
| --- | --- |
| Fields and templates | [Form definition](references/form-definition.md) |
| Authentication and installation | [Form API](references/form-api.md) |
| Side-effect boundaries | [Safety](references/safety.md) |
| Final response | [Handoff result](references/handoff-result.md) |