FAQ

Is there a free tier?

New accounts get 520 free credits on signup with email verification (no card required). That’s enough for one solid build plus a few revisions — you can build a real site end-to-end before deciding whether to top up.

Hosting on *.warpweb.app is also free (auto-pauses after 7 days inactivity; one free POST /v1/sites/:id/refresh brings it back). There’s no monthly minimum and no platform fee — you only pay when you build.

When you need more, the starter credit pack is $5 for 100 credits.

What’s not supported?

Warpweb generates static sites optimized for local-business and service-based use cases. Anything requiring server-side logic at request time isn’t supported — but the form-webhook escape hatch covers most real use cases. Your server gets every lead, and you wire Twilio, SendGrid, your CRM, payment processor, or whatever else you need on your side.

What works out of the box:

Form-submission webhooks — every form on the site posts to your server with an HMAC-signed payload. Wire any backend behavior.
Stripe Payment Link buttons — static “Buy now” links embedded in the page. Stripe handles checkout end-to-end.
Customer-provided keys for client-side libraries — Google Maps embeds, Calendly, Mailchimp, GA4, and similar drop-in widgets work fine.

What’s out of scope (needs a backend you control):

Live chatbots that text or email you when a visitor types
Custom Stripe Checkout flows with server-side session creation (use Payment Links instead)
User accounts, gated content, or member-only areas
Real-time inventory, dynamic pricing, or per-visitor personalization
Server-side A/B testing logic

If you need one of the out-of-scope items, host that backend yourself and call out from your generated site via the form webhook or a client-side embed.

Is the API stable?

V1 endpoints are stable. Breaking changes get a new major version (/v2/) with a 6-month sunset window for V1.

Non-breaking additions (new optional fields, new error codes, additional webhook event types) can ship at any time. Watch the Changelog for what’s new.

Can I white-label the deployed sites?

Yes — that’s the default. Generated sites carry no Warpweb branding, on either the free *.warpweb.app subdomain or a custom domain. Your business is the only brand on the page.

The one exception: when a free-subdomain site auto-pauses after 7 days of inactivity, visitors temporarily see a Warpweb-branded placeholder instead of the real content. One free POST /v1/sites/:id/refresh call restores it. Paid-tier sites (custom-domain attached) never pause.

Can I use my own domain?

Yes. Two paths:

You already own it. Point DNS at Warpweb, call POST /v1/sites/:id/domains (5 credits), $10/mo per site for always-on hosting.
You don’t own it yet. Call POST /v1/domains/register. Warpweb registers it (passthrough registrar fee), configures DNS, and attaches in one call (50 credits + the registrar fee).

Can I get a refund if I don’t end up using Warpweb?

Yes:

Failed builds — never charged in the first place. No refund needed.
Unspent credits — refundable within 30 days of purchase, prorated. Email support@warpweb.ai with your account email.
Active site subscriptions — cancel any time from the dashboard. Pro-rated for the unused portion of the current month. Site data preserved for 90 days after deactivation, then archived.

See Pricing → Refunds for the full policy.

Do you support team / org accounts?

One account per email today. If you need multi-user access, share credentials through a password manager and rotate keys when teammates leave (Dashboard → API Keys → Rotate). Team accounts with role-based access are on the longer-term roadmap — if it’s blocking you, email support@warpweb.ai so we can prioritize.

How do I make sure I’m building the right business?

Common names (“Acme Plumbing”, “Mike’s BBQ”) match multiple Google Places results. Letting POST /v1/sites auto-resolve picks the first match — which may not be the one you mean. Use the two-step flow:

Call POST /v1/businesses/search with businessName (and optionally businessLocation). You get back up to 5 candidates with placeId, formatted address, phone, rating, and a Google Maps URL (googleMapsUri).
Show the candidates to your user (or pick programmatically), then pass the chosen placeId to POST /v1/sites instead of businessName.

If you’re confident the name is unique, you can skip the search step and pass businessName directly — Warpweb will still try to disambiguate via Google Places but will fail closed if more than one strong candidate exists.

What’s in a generated site?

Every site Warpweb deploys is a multi-page, mobile-responsive, SEO-instrumented static bundle. Out of the box you get:

Pages: home, about, services, contact (plus an FAQ section where the vertical earns it — e.g. trades, clinics)
Sections: hero, services grid, testimonials/reviews (pulled from Google), service-area maps, contact form, footer
SEO: per-page meta tags, canonical URLs, OpenGraph + Twitter cards, sitemap.xml, robots.txt, and Schema.org JSON-LD (LocalBusiness, OpeningHours, AggregateRating when reviews exist, service-area markers when relevant)
Performance: target Lighthouse score 90+ on mobile; image optimization; preload + lazy-load hints; minimal JavaScript
Accessibility: WCAG AA target — labelled form inputs, semantic landmarks, color-contrast checks during build
Contact form: built-in, submissions delivered to your form-webhook URL with HMAC signing
Custom client-side embeds: GA4, Plausible, Calendly, Stripe Payment Links, Google Maps, Mailchimp, and similar drop-in widgets work out of the box

What’s not included: server-side anything (databases, auth, dynamic routing, server-rendered personalization). See “What’s not supported?” above for the full out-of-scope list and escape hatches.

I already have a website — can Warpweb use it as a starting point?

Yes. Pass the URL as existingSiteUrl on POST /v1/sites and Warpweb will extract services, FAQs, testimonials, and photos from your current site to seed the build. The output blends extracted content (your real services, your real testimonials) with the AI-generated structure and design — better defaults than a from-scratch build for businesses with existing web copy.

You don’t need to “migrate” — there’s no import step. Warpweb generates a fresh site from research; existingSiteUrl is just an additional signal. Your old site stays online until you cut over DNS.

How do I add analytics?

Two paths:

At create time — add the embed as part of the initial design, then point your analytics property at the deployed *.warpweb.app (or custom) domain.
Via a revision — POST /v1/sites/:id/revisions with a prompt like "Add Google Analytics 4 with measurement ID G-XXXXXXX in the site head." The agent edits the templates accordingly.

Anything that drops in as a client-side script tag works — GA4, Plausible, Fathom, PostHog, Microsoft Clarity, Hotjar. Server-side analytics (Segment server-side, custom event collection) needs a backend you run yourself; you can still embed the client-side SDK on the generated site.

Can I edit the generated HTML directly?

Not in V1. Iteration happens via natural-language revisions (POST /v1/sites/:id/revisions) — the agent edits the source and redeploys. The deployed bundle isn’t a hand-editable surface today.

If the agent struggles with a specific change after a couple of retries, contact support — we can apply targeted patches on your behalf during the V1 window. Source export for self-hosting is on the roadmap; the current path is to keep iterating via the revision API.

Can I export the source / self-host the site?

Not in V1. Generated sites are hosted on Warpweb-managed infrastructure. If you need an HTML export for migration purposes, email support@warpweb.ai and we’ll provide one. Programmatic source export is on the roadmap.

Is there a staging or sandbox environment?

Not in V1 as a separate environment. The 520 free signup credits are effectively your sandbox budget — one full build plus a handful of revisions, no card required. Use a throwaway business name (or a real one of your own) on a free *.warpweb.app subdomain to exercise the full integration before pointing real customer traffic at it.

If you need a long-running mock environment for CI, contact support — we can scope an arrangement for serious integration work.

Is there an SDK?

V1 is REST + curl. Use any HTTP client. Official SDKs for JavaScript/TypeScript, Python, and Ruby are V1.5 — coming after we see which languages customers actually use.

If you want to publish a community SDK, we’d love to link to it from the docs. Email support@warpweb.ai with the link and we’ll add it.

What’s the data retention policy?

Form submissions — stored 90 days, then purged. Deliver them to your webhook for long-term retention.
Build artifacts and revisions — kept as long as the site is active. 90 days post-deactivation, then archived.
API request logs — 30 days, surfaced in the dashboard usage view.
Webhook delivery logs — 30 days (including dead-letter contents).

GDPR / CCPA deletion requests are honored; email support@warpweb.ai (we action within 30 days). For DPA/SCC requests, subprocessor lists, encryption details, and the rest of the procurement-grade story, see Security & Compliance.

What happens if a webhook delivery fails?

We retry on the schedule immediate → +30s → +5min → +30min. After that, the delivery lands in the dashboard’s dead-letter queue with a manual replay button.

4xx responses (including 400, 404, 422) are not retried — they’re treated as permanent rejections. Don’t return 4xx to “ignore” events. Return 200 and ignore on your end.

See Webhooks → Form Submissions → Retry behavior.

Are there rate limits?

30 requests per minute per API key, sliding window. See Authentication → Rate limits for the full picture. If 30/min is too tight for your workload (e.g. a CRM that builds a site per new customer signup), email support@warpweb.ai — we’ll raise the cap for legitimate use cases.

How do I delete a site?

Site deletion is dashboard-only in V1; the DELETE /v1/sites/:id API endpoint ships in V1.5. To deactivate today:

Open the site in app.warpweb.ai → Sites.
Click Deactivate.
The site goes offline immediately. Custom-domain billing stops.

Site data (build artifacts, revisions, form submissions) is preserved for 90 days, then archived. Contact support if you need it earlier.

How do I list my API keys via the API?

Key management is dashboard-only in V1 (Dashboard → API Keys). You can create, rotate, and revoke keys there. Programmatic key listing / management is on the roadmap. For zero-downtime rotation, create a second key in the dashboard, deploy it, then revoke the original.

How do I rotate an API key?

Dashboard → API Keys → Rotate. The new key is shown once; the old key is invalidated immediately. Deploy the new key before clicking Rotate to avoid a brief 401 window in production.

For zero-downtime rotation, create a second key, deploy it, then revoke the original.

Why am I getting 401 on a key I just created?

Two usual causes:

Typo in the header. The format is Authorization: Bearer wwk_…. No extra spaces, no quotes, capital B in Bearer.
Key revoked. Check the dashboard — if you rotated keys recently, the old plaintext stops working immediately.

All keys hit the same production api.warpweb.ai — there’s no separate staging endpoint in V1, so a key tagged staging in the dashboard authorizes the same surface as one tagged prod. Tags are organizational only.

How do I contact support?

Email: support@warpweb.ai
Response: best-effort, business hours US/Pacific
Priority support is included for accounts spending $200+/month

Include your account email and any relevant site_id / event_id / revision_id in your message. We can find anything if you give us an ID.

Authentication Security & Compliance