FAQ
What’s the difference between Warpweb and Prickl?
Two products, one engine. Prickl is a consumer iOS app for solo operators — chat with an AI office manager who, among other things, can build you a website. Warpweb is the developer API for the same site-building engine. If you’re an end user who wants a website, look at Prickl. If you’re a developer integrating site-building into your own product, you’re in the right place.
Is there a free tier?
Sort of. The hosting is free — sites on *.warpweb.app cost nothing per month. But each build consumes ~150 credits ($1.50). There’s no monthly minimum and no platform fee — you only pay when you create something.
The starter credit pack is $5. That covers your first three builds.
Can I use my own domain?
Yes. Two paths:
- You already own it. Point DNS at Warpweb, call
POST /v1/sites/:id/domains, $20/mo per site. - You don’t own it yet. Call
POST /v1/domains/register. Warpweb registers it (passthrough cost + small markup), configures DNS, and attaches in one call.
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. Open an issue at github.com/warpweb/warpweb-docs.
Can I white-label the deployed sites?
Not in V1. All free-tier sites carry a small “Powered by Warpweb” footer; paid-tier sites get a less prominent attribution. White-label (full removal) is a V1.5 feature for higher-tier customers.
Do you support team / org accounts?
Not in V1. One account per email. If you need multi-user access today, share credentials through a password manager. Team accounts with role-based access are V1.5.
How do I delete a site?
Send a DELETE /v1/sites/:id request — well, that endpoint is V1.5. For V1, deactivate via the dashboard:
- 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.
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.
What happens if a webhook delivery fails?
We retry on the schedule immediate → +30s → +5min. 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.
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?
Three usual causes:
- Typo in the header. The format is
Authorization: Bearer wpwb_sk_…. No extra spaces, no quotes, capital B in Bearer. - Key revoked. Check the dashboard — keys can be auto-revoked if Warpweb detects them in a public GitHub commit.
- Wrong environment. Production keys don’t work against staging endpoints (and vice versa). Match key environment to endpoint.
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.
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.