Requests
98.79% success rate
Track LLM costs, latency, errors and sessions across OpenAI, Claude, Gemini and more. Keep your existing backend, or add our AI gateway for API key protection, routing and fallbacks.
1,000 requests/month free · No credit card required · Provider usage billed separately
98.79% success rate
Start with visibility. Add the gateway wherever you need protection and routing. Both can live in the same project.
Requests, estimated AI spend, errors and latency — with shared periods and filters. Follow a model or client from the overview into the details.
98.79% success rate
Estimated provider cost
Average provider response time
Start with 1,000 requests per month. No card required; provider charges are separate.
Compare models and clients. Unknown pricing stays visible instead of looking free.
Inspect error codes and latency trends with the same date range across every chart.
Connect requests to clients and sessions. Separate gateway traffic from server-reported events.
Two key halves unlock the provider credential in gateway memory for an authorized request. Neither half can recover it alone. Watch the path.
Attacker finds only client_half.
Attacker gets ciphertext and server_half.
The credential is recovered in memory while forwarding.
Verify requests come from your real app on a real device. App Attest with Secure Enclave signatures, a replay guard (sign_count must strictly increase), and modes off / device_token / assertion — plus a rotatable simulator bypass token for dev. Play Integrity is on the roadmap.
Point any request at HyperProxy and swap the auth header. That's it — the body stays your service's own.
$ curl -N https://api.hyperproxyai.com/ab12cd34ef56aa77/c4bc1015a291/v1/chat/completions \ -H "X-HyperProxy-Key: hp_live_ab12cd34ef56aa77.<key_id>.<client_half>" \ -H "Content-Type: application/json" \ -d '{"model":"gpt-4o-mini","stream":true,"messages":[{"role":"user","content":"hi"}]}'
Copy your gateway URL from the dashboard and append the upstream's own path: api.hyperproxyai.com/<project>/<service>/<your upstream path>. The URL says where to route; the app key in the header is the credential — it carries the client half we fuse the real key from. Use the provider's request format. Configured model, prompt or compatibility policies may update fields before forwarding. Any public HTTPS API, AI or not.
Start from a built-in preset, or register any public HTTPS API by its base URL — an AI model or any other service. Provider-native transit means no SDK lock-in: send each service's own request format and use native forwarding by default, with per-service endpoint allowlists and attestation.
Provider-native transit runs from iOS, Android, web, React Native, or Flutter — no SDK to adopt, no lock-in.
Split-key envelope encryption plus App Attest device attestation — keep provider credentials off-device and add device verification to supported requests.
Track tokens, model costs and spend limits. See when usage is unpriced so unknown costs do not look free.
Test saved versions in staging, publish to production, and roll back from the dashboard. See the release workflow →
Each guide explains the integration boundary, the data involved, and the controls available in production.
Measure requests, tokens, latency, errors and estimated provider spend—with or without the gateway.
Call provider-native AI APIs from iOS without embedding the provider credential in your app.
Protect keys with split-key storage, device proof, allowlists, rate limits and model policy.
Turn completed GenAI spans into focused usage and cost analytics over OTLP/HTTP.
client_half ⊕ server_half = data_key, reconstructed in memory only.
off / device_token / assertion; Secure Enclave; replay guard; simulator bypass.
Many per service — segment and revoke per app version. Supply the provider key again when minting or rotating an app key.
Restrict which upstream paths a key can reach, per service.
Enforce limits per key, IP, or device, with clear retry guidance for every rejected request.
Fire after N consecutive upstream failures — know before your users do.
Token-by-token streaming forwarded straight through, no buffering.
Run HyperProxy in your own environment, or let us operate it for you.
Start with 1,000 requests per month, no card required. Choose by monthly request volume. Every plan includes the same observability and gateway controls, with usage-based pricing that scales with you.
For prototypes moving into production.
For production apps with steady traffic.
For growing products and multiple workloads.
For high-volume production workloads.
Full product access. Your plan sets included usage and usage-based pricing.
Compare all plans, free allowance and billing examples →
Monthly prices are in USD and exclude VAT / sales tax, which is added based on the customer’s location. Provider API charges are separate. Every account includes 1,000 base requests per month; paid subscriptions add to that shared allowance. Usage-based rates apply after included usage, billed in blocks of 1,000 on the next invoice. Usage-based billing is on by default for paid plans and can be turned off in your account to stop at the included limit. When enabled, an account safety limit caps usage at 2× the total allowance.
Run HyperProxy in your own environment. Keep traffic, credentials, and operational control entirely on your side. Source access is available at no charge on request.
Ask about self-hostingWe run the platform. Connect server metrics or configure a secure gateway service. Free tier included, scale when you need it.
$ start freeShip AI features without shipping your API keys.
Free tier: 1,000 requests / month. No card required.