Private API key
A unique customer credential is shown once after confirmed payment.
Issued securelyAI access.
Infrastructure stays private.
A controlled gateway for model access, customer keys, usage policy, and live billing.
Checking gateway
Customer keys stay separate
Provider credentials stay server-side
Checking checkout
01 / The gateway
The complex parts stay behind one clear endpoint.
Your product sends one request to blueberry. The gateway checks the customer, protects upstream credentials, applies account rules, records usage, and returns a familiar response. Customers see the part they need. Operators keep control of the rest.
Customer appblueberry gatewayAI response
02 / After checkout
Everything needed
to start is delivered.
Payment does not end at a receipt. It creates a usable account with the access details and visibility needed for the first request.
Familiar endpoint
A compact base URL that fits common chat-completion integrations.
Ready to connectMonthly allowance
The selected plan sets a clear combined input and output token limit.
Visible rulesAccount visibility
Plan, status, current usage, and renewal details stay available.
Self-serveSupport path
Billing, access, and security questions go to dedicated support routes.
Human help03 / First request
From checkout
to first request.
Purchase
Choose a plan, enter the access email, and complete payment in secure checkout.
Receive access
After payment confirmation, a private blueberry API key is issued and shown once.
Send a request
Use the familiar chat endpoint while usage and subscription status stay connected.
04 / Product view
One gateway.
Every moving part in view.
Integration stays compact while account state remains visible and understandable.
POST
/v1/chat/completions200PlanPlus
StatusActive
Next renewal24 Aug
Monthly usage1.2M of 3M
- Endpoint
- https://blueberrry.net/v1
- Customer key
- bbai_live_••••••••••••9Q3
- Access
- Subscription active
05 / Compatibility
Familiar standards.
Fewer integration surprises.
The gateway follows the request patterns developers already expect, so existing application code usually needs only a base URL and customer key change.
RouteChat completions
POST /v1/chat/completionsAuthenticationBearer token
Authorization: Bearer bbai_live_...TransportHTTPS + JSON
application/jsonResponseStandard or streamed
stream: true | falseModel selectionConfigured model IDs
model: provider-default06 / Use cases
Built for the work
behind the product.
Ship AI features
Connect once, keep application code focused, and add AI without rebuilding the infrastructure around it.
Protect provider credentials
Keep sensitive upstream keys on the server instead of shipping them inside customer applications.
Control customer access
Tie every request to a customer key, active plan, monthly allowance, and clear account state.
Understand usage
See token consumption and account status without exposing the systems that route each response.
07 / Security
Private by structure,
not by slogan.
Payment details, customer access, request content, and provider credentials follow separate paths. Each service receives only what it needs.
01HTTPS in transit
Public traffic is encrypted between the customer and gateway.
02Hashed customer keys
Issued keys are stored as one-way hashes after initial delivery.
03Server-side credentials
Provider credentials stay out of browser code and customer responses.
04Payment separation
Card details are entered only inside secure Paddle checkout.
08 / Token rules
Tokens, without
the guessing.
Usage is measured against one understandable monthly allowance. Customers can inspect the same account state the gateway enforces.
InputPrompt + context
+
OutputGenerated response
=
CombinedPlan usage
One billing cycle
Allowance resets when the monthly subscription renews.
Visible usage
The account view shows current-cycle token usage at any time.
Predictable limits
Requests pause at the plan limit instead of creating surprise overages.
No hidden cash value
Unused allowance does not roll over and cannot be withdrawn.
09 / Billing
Access that fits
how you build.
Choose a predictable monthly allowance or add prepaid usage credit. Checkout explains the total before payment.
Payment received
Your subscription was completed.
Paddle is confirming access with blueberry.
Your blueberry API key
Credits / PrepaidPay for the usage
Pay for the usage
you need.
Credits are non-recurring, stay on the access account, and are used only after a monthly allowance is unavailable or absent.
Launch credit bonus
Prepaid access credit
Prepaid access credit
Prepaid access credit
Prepaid access credit
Prepaid access credit
Prepaid access credit
Prepaid access credit
Prepaid access credit
Talk to the team about a custom allowance and support path.
→
Checking
Loading secure checkout configuration.
Checkout: LoadingMonthly subscriptions renew until canceled. Prepaid Credits are non-recurring and have no cash value. Taxes and full terms appear before payment. Read our Terms, Privacy Policy, and Refund Policy.
10 / Account
Your access,
in one place.
After your first payment, activate a web account with the access email and private API key you received. Later, sign in with email and password to view access without re-entering the key.
Signed in
Plan-
Access-
Usage-
Credits-
Next renewal-
Existing customer
Sign in
Use the web account you activated after payment.
First time here? Activate your account
Use the same access email and the private API key shown after checkout. This key is used only to prove ownership and is never stored in the browser.
11 / Operations
Control for the person
running the product.
Access follows payment state.
Active, canceled, past-due, and expired accounts can be handled consistently by the gateway.
Limits are checked per request.
Customer identity and monthly usage are evaluated before upstream work begins.
Keys can be supported without exposing providers.
Access problems stay inside the blueberry customer layer, keeping provider credentials private.
Useful metadata, not payment details.
Operators can understand request outcomes and account state while checkout remains separated.
12 / About
A small team, building the layer we wanted to use.
blueberry Ai is building a focused gateway for teams that want private model access without turning billing, credentials, and usage controls into a second product.
The goal is simple: make the first purchase understandable, make the first integration familiar, and keep sensitive infrastructure out of customer code.
Clear by default
Plans, limits, account status, and next steps should be obvious.
Private by structure
Credentials and payment data stay inside the services built to handle them.
Useful before complex
Start with one endpoint and grow only when the product needs more.
Questions
What customers usually ask.
Can access be used immediately after payment?
After Paddle confirms the transaction, blueberry provisions the subscription and displays the new API key on this page.
Where are card details entered?
Only inside Paddle's secure checkout. Raw card details never reach the blueberry server.
What happens when the allowance is reached?
Requests pause until the next billing cycle or until the customer moves to a larger plan.
Can I inspect my current account?
Yes. Open Billing or use the account section with your blueberry API key to view plan and usage status.
Contact