Every site you own.
One pipeline in.

Implement Rook Dots lead capture in this project.

Endpoint: POST https://dotsapi.rookhq.com/api/v1/public/leads
Auth header: X-Rook-Key: <my capture key, stored server-side only, e.g. process.env.ROOK_DOTS_KEY>

Do this:
1. Find my existing contact/signup form (or create one if none exists) and identify its fields.
2. Add a server-side route/endpoint in this codebase (do NOT call the Rook Dots API directly from client-side JS, the key must never reach the browser).
3. Optionally, GET https://dotsapi.rookhq.com/api/v1/public/leads/config (same X-Rook-Key header) first to fetch the workspace's configured budget ranges, currencies, sources, and services, then map my form's own fields onto that vocabulary where they overlap (e.g. if my form has a "services" checklist, match each of my labels to the closest one in config.services and send their "value", not my own label).
4. From that server route, POST JSON to the endpoint above with a body built from the form fields, mapped to this shape:
   {
     "name": string (required),
     "email": string (optional, valid email, strictly validated server-side),
     "phone": string (optional, pre-formatted), OR "phoneCountryCode" + "phoneNumber" (optional, sent separately, e.g. "+1" and "5550100"),
     "businessName": string (optional),
     "budgetRange": string (optional, ideally one of config.budgetRanges[].value if you fetched config, otherwise free text),
     "currency": string (optional, ideally one of config.currencies[].value),
     "servicesInterested": string[] (optional, ideally values from config.services[].value),
     "notes": string (optional, fold in any extra form fields that don't map to the above as readable text here)
   }
5. Add a hidden form field named "hp" (a honeypot) that must stay empty, include it in the POST body as "hp". Real users never fill it; if a bot does, the API silently accepts the request without creating a lead, so don't treat a 201 as proof a human submitted it.
6. Handle the response: 201 means the payload was accepted (data.id is the new lead's id, store it if you need to reference the lead later, e.g. to add a note). Handle 400 (validation, show field errors), 401/403 (misconfigured key, log it, don't show the user a raw error), and 429 (rate limited, retry with backoff or ask the user to try again shortly).
7. Read the key from an environment variable (e.g. ROOK_DOTS_KEY). Never hardcode it, never commit it, never send it in a client-side bundle.
8. Keep this best-effort: if the Rook Dots call fails, log it but don't block the user's form submission on it, unless Rook Dots is the only place this data is stored.