Buy credit, choose your privacy level, and start sending jobs.

This is a thin v1 web flow. It creates a user, ensures a buyer profile exists, applies a starter credit amount, and returns a buyer API key for the OpenAI-compatible API.

Starter packagePrototype credit package in USD until Stripe is wired in.

OutputUser record, buyer profile, buyer key.

Next stepUse the returned key against /v1/models and /v1/chat/completions.

Create buyer

Buyer flow

Result will appear here.

This is still a bootstrap flow. Real payment capture can replace the starter credit step later without changing the buyer profile model. After signup, use the same email on the buyer dashboard.

Privacy levels

Choose how strict routing should be

Resonara Nodes only

Use only nodes operated directly by Resonara.

Resonara + Privacy Nodes

Allow Resonara-operated nodes and external nodes that have accepted Resonara's privacy commitments.

Any compatible node

Allow any compatible node for maximum availability and potentially lower cost.

What the labels mean

Node types

Resonara Nodes

Nodes operated directly by Resonara under our own infrastructure and privacy practices.

Privacy Nodes

External provider nodes that have explicitly agreed not to inspect, retain, or reuse customer traffic beyond what is strictly required to process the request.

Compatible Nodes

Other nodes that meet the technical requirements but are not classified as Privacy Nodes.

Important

Privacy warning

No distributed AI platform can guarantee that data will never leak. Even with isolation, rotating jobs, and strict policies, a node may still be compromised, misconfigured, or abused.

If you handle highly sensitive data, always choose the highest privacy level available.

Privacy-first reduces risk. It does not eliminate it.