Landing page HTML

Start with the assumption you want to test and the behavior that would count as evidence. The HTML should give visitors a small but credible experience of the value—not only describe a future product.

A useful page usually contains a clear promise, one focused interaction, an outcome or preview, and a meaningful next step such as applying for a pilot.

• Provide one complete UTF-8 HTML document.
• Keep the file at or below 1 MiB.
• Include CSS and JavaScript in the document or load them from public HTTPS URLs.
• Make the page responsive and usable without a build step.
• Use the project UUID returned by create_project in the endpoints below.

Submit an email address to the public lead endpoint. The field must be named email. A regular HTML form is the simplest option:

<form method="post" action="/api/v1/leads/{project_uuid}">
  <label for="email">Email</label>
  <input id="email" name="email" type="email" required>
  <button type="submit">Join the pilot</button>
</form>

After a successful form submission, idelot redirects the visitor to /lp/{slug}/thanks. Duplicate submissions for the same project and normalized email address do not create duplicate leads.

Use a relative endpoint as shown above. When idelot serves the page, it also normalizes old absolute URLs and stale project UUIDs to the current environment and project.

For an interactive flow, send JSON and request a JSON response instead of navigating to the Thanks page:

const response = await fetch("/api/v1/leads/{project_uuid}", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    "Accept": "application/json"
  },
  body: JSON.stringify({ email })
});

if (!response.ok) {
  const { error } = await response.json();
  throw new Error(error);
}

Ask your MCP-connected AI client to create the complete HTML and publish it with the project UUID. The client calls upload_lp with the HTML content and returns the public URL.

Create a self-contained HTML experiment for this project.
Connect its lead form with the idelot endpoint and project UUID.
Review the mobile layout and form behavior, then publish it.

• Confirm that the experience tests one clear value assumption.
• Use a real project_uuid, not the placeholder text.
• Keep the email field name exactly email.
• Explain what participants are signing up for.
• Do not collect sensitive data unless you have a lawful basis and suitable safeguards.
• Test the page, lead submission, Thanks page, and mobile layout before sharing the URL.