Sell private AI access with a brand customers can trust.

blueberry Ai turns model access into a clean product: customers top up € credit, receive their own gateway key, and use DeepSeek, Qwen, or other routes through your branded endpoint while provider credentials stay private on the server.

View live-style example View top-up flow

Sample monthly volume€100,000

Customer keys1,240

Provider keys exposed0

Checking gateway Provider keys never shown to customers Private customer access

Example

A customer chats with DeepSeek through your private gateway.

This is the kind of product moment customers should understand immediately: they buy € credit, use a blueberry access key, and never receive your upstream provider key.

RouteDeepSeek via blueberry

Credit€20 top-up

PrivacyProvider key hidden

blueberry Ai chat private route

Customer endpoint blueberrry.net/v1/chat/completions

Model route deepseek-chat

Available balance €19.86

Customer

Explain mixture-of-experts models in a short onboarding note.

DeepSeek route

Mixture-of-experts models activate only the specialist parts needed for each request, so responses can stay strong while compute stays efficient.

Top-up+€20.00

Example usage-€0.14

Remaining€19.86

What blueberry Ai is

A commercial wrapper around AI models, built for selling access clearly.

Most AI products start as a direct provider integration. That is fine for a prototype, but it becomes awkward when real customers need invoices, limits, support, and a safe way to use your service. blueberry Ai gives the business a front door and keeps the sensitive machinery behind it.

The goal is not to look like a complicated admin system. The goal is to make the offer feel understandable: buy credits, get access, use the API, and let the gateway measure what happened.

Customer sees

A clear € credit product

Pricing, top-up choices, access instructions, and a clean support path.

Your server owns

Provider keys and routing

The upstream API key stays out of the browser and away from customers.

You monitor

Usage, balance, and revenue

Requests and credit movement are recorded so the business can be managed.

Platform

Designed for teams that need AI revenue to look like a business, not a pile of keys.

A normal AI integration gets messy fast: provider accounts, customer access, payment status, token usage, and support questions all live in different places. blueberry Ai turns that into one operating layer with a simple public API and a private server-side control plane.

ProviderRoutes live server-side

AccessCustomer keys, not provider keys

MoneyTop-ups, ledger, balance state

VisibilityUsage, requests, margin signals

What It Controls

The practical pieces behind an AI token business.

Provider abstraction

Customers call blueberry first. The server forwards to the configured model provider, so upstream credentials never appear in website JavaScript or customer apps.

Prepaid access

A customer can top up credits, receive a private access key, and consume balance through protected API routes.

Usage records

Requests, token estimates, pricing rules, and account activity are recorded server-side for operations and customer support.

Margin awareness

Public prices can sit above provider cost. That gives you a clearer view of revenue, spend, and when pricing needs to change.

Workflow

From payment to model response, every step has an owner.

Customer adds credit

Checkout happens through a hosted payment page, while blueberry waits for the result and prepares the account ledger.

blueberry issues access

The customer receives a private `bb_...` key. The server stores a protected record and keeps the provider key hidden.

Apps call the gateway

Requests use familiar `/v1/chat/completions` style routes, then blueberry forwards to the configured model.

Usage becomes visible

Operations can review request volume, top-up events, customer balance, and pricing assumptions in one place.

Operations

A calmer euro view of revenue, usage, and customer access.

The operational layer is intentionally quieter than a full analytics suite. It focuses on the numbers a small team needs to run the gateway with confidence.

blueberry operations preview ledger

Euro top-up revenue €100,000 sample monthly volume

Requests 4.80M last 7 days

Active keys 1,240 customer access

Policy pass rate 98.6% gateway checks

Traffic

Request activity

protected

Models

Routing table

Defaultdeepseek-v4-flash

Premiumdeepseek-v4-pro

Browser exposureblocked

Provider keyserver only

Ledger

Recent account movement

sample view

Harbor Studio€30paid

Northline Apps€20key issued

Founders Lab€50usage active

SearchPilot Tools€10balance watch

API

Use familiar routes while keeping credentials private.

The public contract can stay simple for customers. Your internal provider choice, pricing, and access policy remain on the server.

curl https://blueberrry.net/v1/chat/completions \
  -H "Authorization: Bearer YOUR_BLUEBERRY_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "model": "deepseek-v4-flash",
    "messages": [
      { "role": "user", "content": "Write a short welcome message." }
    ]
  }'

Gateway routes

/health public service status
/billing/config billing readiness
/v1/models protected model list
/v1/chat/completions protected chat route
/v1/usage protected usage summary

Billing

Prepaid € credits with card checkout or BTCPay crypto checkout.

Card entry belongs on the payment provider's hosted checkout page. Crypto checkout creates a BTCPay invoice and credits the customer account after the invoice is settled by webhook.

BTCPay checkout

Automatic crypto top-ups

BTCPay creates a private invoice and returns settlement through a webhook. blueberry credits the account after the invoice is settled, without publishing wallet addresses on the page.

ProviderBTCPay Server

SettlementWebhook verified

KeysIssued after paid

Checking BTCPay checkout configuration.

Customer wallet

Balance, key, and spend rules

Available balance€20.00

Customer keybb_live_...

MeteringInput/output pricing pending

Transaction state

Checkout sessioncreated

Payment statuspending Stripe key

API key deliveryafter payment

Security

Private access, clear boundaries, easier trust.

Provider keys stay server-side.

DeepSeek or other upstream keys are read by the gateway service, not exposed to customer browsers.

HTTPS protects public traffic.

The public site and API routes are served through HTTPS on `blueberrry.net` and `www`.

Card data stays with checkout.

blueberry stores payment results and ledger state, not raw card numbers.

Customer keys can rotate.

Access can be changed without replacing the upstream provider key or editing customer code.

About blueberry Ai

We are a product team focused on making AI access sellable.

blueberry Ai exists for founders, studios, and small teams that want to offer AI access under their own brand without exposing provider accounts or stitching together payments by hand.

We care about calm, explainable software. A customer should understand what they are buying. An operator should understand what was paid, what was used, and what needs attention. That is the difference between a pretty demo and a product people can actually use.

01Make the offer simple before adding more models.

02Keep secrets private even when the product is public.

03Show enough usage detail to support customers quickly.

Packages

Start with a clean gateway, then add operations.

Starter

€490

Gateway readiness, billing setup review, and launch checklist.

Request Starter

Managed

€1,200/mo

Gateway operations, usage reports, customer access support, and spend controls.

Request Managed

Business

Custom

Multi-team policy, procurement support, provider review, and custom reporting.

Request Business

Contact

Start the conversation without publishing private details.

Use brand contact channels for sales, support, and security messages. Personal addresses, home details, provider keys, and payment secrets should never be sent through the public website.

General hello@blueberrry.net Access requests, onboarding, and partnerships Support support@blueberrry.net Account, usage, billing, and gateway questions Security security@blueberrry.net Responsible disclosure and access concerns

Privacy-first launch

Private-first means the public site only shows brand channels: company mailboxes for conversations, a registered office or virtual business address for legal notices, and no provider keys, card details, or private credentials in public forms.