/* generated using openapi-typescript-codegen -- do not edit */
/* istanbul ignore file */
/* tslint:disable */
/* eslint-disable */
/**
 * Signup payload.
 *
 * Two valid flows (per spec §8.1 anti-abuse hybrid design):
 *
 * 1. Browser flow (humans on docs landing): provide ``turnstile_token`` (from
 * Cloudflare widget) AND ``setup_intent_id`` (after Stripe Elements card
 * collection). Turnstile blocks bots, SetupIntent attaches card on file.
 *
 * 2. Programmatic flow (agents/MCP self-signup): provide ``payment_method_id``
 * directly (agent must tokenize card via Stripe API first). NO Turnstile
 * required — Stripe's own fraud detection on the card is the anti-abuse
 * layer. This enables autonomous AI agents to self-register without browser.
 *
 * Rule: must provide EITHER (turnstile_token AND setup_intent_id) OR
 * (payment_method_id). Validation in handler.
 */
export type SignupRequest = {
    email: string;
    /**
     * Cloudflare Turnstile token (browser flow only)
     */
    turnstile_token?: (string | null);
    /**
     * Stripe SetupIntent ID (browser flow: after card collection)
     */
    setup_intent_id?: (string | null);
    /**
     * Stripe PaymentMethod ID (programmatic flow: agent self-signup)
     */
    payment_method_id?: (string | null);
};