Push a ZIP, get a public URL with a secure proxy, runtime config, and webhook capture. Your prospects make real API calls — your keys never leave the server.
Real API calls, zero secrets in the browser. Click to load the interactive demo in an iframe.
We'd rather you bounce now than churn after a contract. Here's where we win, and where we don't.
Same demo. Different operational reality.
Real primitives we've already shipped: SSRF-hardened proxy, runtime config, webhook receiver, atomic monthly quotas.
POST /api/proxy
{
"projectId": "stripe-checkout-7b3a1c",
"method": "POST",
"targetUrl": "/v1/charges",
"body": { "amount": 1999, "currency": "usd" }
}[
{ "key": "STRIPE_KEY", "visibility": "secret", "required": true },
{ "key": "ACCOUNT_ID", "visibility": "public", "required": true },
{ "key": "BASE_URL", "visibility": "public",
"defaultValue": "https://api.stripe.com" }
]POST /hooks/<projectId>/<token>
{ "event": "checkout.session.completed", "id": "cs_test_..." }
→ stored in project_events
→ visible in /hooks/<projectId>
→ counted in your monthly usage// HTTP 402 from /api/proxy
{
"code": "quota_exceeded",
"error": "Free plan limit reached for proxy_requests: 1000 / month.",
"usage": { "current": 1000, "limit": 1000, "metric": "proxy_requests" }
}No vanity metrics. These are real guarantees the platform gives you on day one.
npx apiqube push extracts, prebuilds, and serves your demo under a public slug.
Project keys live server-side. The proxy injects them per request and strips them on the way back.
Response size and timeout enforced for you. A runaway upstream can’t take your demo down.
DNS resolve, IPv6 loopback, cloud metadata, redirect revalidation — all covered by unit tests.
npx apiqube push