Trust boundaries

Know what you can audit before workloads grow.

Use scoped keys, prompt and response privacy, usage metadata, payment records, and support tickets to trace access and spend. Formal SLA and compliance certifications are not currently offered.

Read API docs

AccessScoped keys created in the console

PrivacyPrompts and responses are not stored by our platform

UsageMetadata for model, token, status, latency, and charge history

BillingTop-ups, receipts, and payment confirmation records

Audit checks

Check privacy, access, usage, and billing from customer-visible records.

The useful trust signal is whether an account owner can understand what is not stored and trace usage, access, and billing without opening a support thread first.

You can audit

Records account owners can use to understand access, usage, and spend.

Which key sent each workload
Which model and tier served the request
Usage metadata without prompt or response content
Monthly archive batches after day 90, downloadable during the 2-year retention window.
Top-ups, payment status, receipts, and support tickets

Before launch

Checks to run before sustained automation.

Use separate keys per environment or workload
Check usage history before sustained automation
Confirm credits after checkout before increasing traffic
Open a dashboard ticket for billing or access questions

Records

Concrete account records.

Prompt and response privacy

Routed API prompts and responses are processed transiently and are not stored by our platform.

Scoped API keys

Create keys from the console and use separate keys for agents, workflows, scripts, or environments.

Usage metadata

Review model, tokens, request status, latency, charges, and archive exports without prompt or response content.

Payment records

Credits are added after confirmed payment events, and records keep top-ups, receipts, and usage traceable.

Claim limits

Current formal assurance limits are explicit.

This site does not claim uptime percentages, SLA terms, SOC 2 compliance, enterprise support, or production-grade reliability. It does describe the platform data handling boundary for routed API prompts, responses, and usage metadata. See Privacy, Terms, and Refunds for policy pages.

Record sourceUsage metadata, archive exports, credit balance, payment records, and receipts

Support pathDashboard tickets with request or payment context

Current limitsNo formal SLA, SOC 2 report, or support plan