Blurface Playground

Try face blur locally, then move the same task flow into a guest-ready cloud product.

This workspace is designed as a retention loop, not just a demo. Visitors start with a private in-browser preview, then continue into guest onboarding, starter credits, API key provisioning, task history, and reusable API docs.

API documentation API log dashboard API keys
Session
No active account yet

The first cloud run creates a guest session automatically, then unlocks starter-credit logic.

Sign in
Credits
0.0 credits

Each cloud blur consumes 0.5 credit. Runs are blocked when balance is too low.

API key
Not ready

Guest and signed-in sessions can both obtain a key automatically through this product flow.

Manage keys
Private preview

Zero-credit browser preview

Use this first touch to reduce friction. Files stay in the tab, the slider updates instantly, and the user experiences value before any guest account or billing step appears.

No account needed
Blur strength12px
Loading preview…
Cloud run

Guest onboarding, credit gating, and async task delivery

The first real run handles account preparation, starter-credit claim logic, API key readiness, upload, async generation, and task tracking in one product surface.

Auto guest signup
StandbyUpload a photo to start.

Visitors do not need to sign up first. The cloud run will prepare a guest workspace, then attempt to unlock starter credits before the job starts.

Uploaded source

The cloud request starts from the selected file, uploads it, then forwards the hosted URL into the public generate endpoint.

Result image

Once processing finishes, the result image appears here and the same task can be revisited through logs or GET /api/status.

Developer handoff

The API mirrors the exact playground flow

Once the product loop works, developers can call the same public endpoints directly. That keeps marketing, dashboard, and API behavior aligned.

Open full docs
Sample requestcURL
curl -X POST "https://blurface.net/api/generate" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "image": "https://images.unsplash.com/photo-1500648767791-00dcc994a43e?w=1200&q=80&auto=format&fit=crop"
  }'
Reference
API docs
Parameters, request examples, response payloads, and error handling notes.
Debug
Task logs
Inspect requests, result URLs, task states, and credits consumed by each key.
Access
API keys
Provision, rotate, and manage the same keys used by the web app and your integrations.
Guest onboarding
The first cloud click should not feel like registration friction.

This flow creates a guest session only when value is already established through the local preview, which is a better activation order than leading with auth.

Credit control
Insufficient balance stops wasted requests before they start.

Starter-credit claim, top-up modal, and required-credit checks all happen before generation to preserve trust and reduce confusing upstream failures.

Retention loop
One task should lead naturally into docs, logs, and paid reuse.

Result visibility, task IDs, API docs, and dashboard history are positioned as the next steps so a successful blur becomes the start of a workflow, not the end.