Client Portal

Buy and manage Service Credits for text, image, video, coding and other AI API workloads.

Account Overview

One balance for multiple AI workloads, with usage, receipts and provider policy controls.

Multiple API keys can be purchased and tracked by project, department or downstream client.
Available Credit$0.00
API Keys0
Receipts0
Policy Providers0
Ready.

API Key Usage

Track spend and requests for every key, so a small business can manage multiple keys and a consumer can still see personal usage.

Service Coverage

Text & chat APIsOpenAI-compatible text, reasoning and assistant workflows.
Image generationCredits can meter image models and creative generation routes.
Video generationVideo model access can use the same balance, policy and receipt flow.
Coding & agentsCoding assistants, agents and API tool calls are part of the same credit model.

This demo only runs a text request today; the commercial model is unified Service Credit for multiple AI workloads.

Model Marketplace

Choose which text, image, video or coding model routes you want to buy credits for.

Purchase Plan No models selected yet.

Actual checkout is not enabled in this testing build; selected models form a purchase and onboarding request for sales/ops.

Model Configuration Guide

Beginner-friendly notes for choosing models, buying credits, creating keys and understanding routing.

1. Choose workload first

Text, image, video and coding models have different latency, cost and policy requirements. Pick the workload before picking a provider.

2. Check provider status

Active providers can be routed. Inactive providers are visible for planning, but need API keys, contract review and resale approval.

3. Confirm region and retention

Some customers require SG, US, CN or global routing. No-retention requirements can remove providers from the route.

4. Use separate keys

Small businesses should use different keys for departments, projects or downstream customers so billing and audit trails stay clear.

5. Understand billing

Service Credit is consumed by usage. The platform records customer charge, provider cost, gross margin, receipt and ledger entries.

6. Know fallback behavior

If a provider fails, routing can try another compliant provider. Audit events record route decisions and fallback reasons.

Configuration checklist

For every model route, confirm provider, model ID, workload type, region, retention, resale authorization, price, API key scope, budget cap, logging policy, SLA and support owner.

Example:
Provider: deepseek
Model ID: deepseek-v4-flash
Workload: text / chat
Region: global
Retention: provider standard terms
API key scope: chat.completions, usage.read
Billing: Service Credit, per usage event
Logging: metadata only, no raw prompt by default
Owner: customer workspace admin

Open detailed Chinese model configuration document

API Access

Testing UI only. Production portal login will use session auth, MFA/passkeys, CSRF protection and RBAC.

Seller of Record

- -

Service Credit is sold by the named reseller. Platform technology is provided by GLOBAL AI GATEWAY.

Latest receipts and policy data are available in technical details for testing.
Technical details 
Ready.

Developer Quickstart

Pick a workload and copy the integration shape for your backend.

Text APIPOST /v1/chat/completions

      

      

    

    

      

        

          
Workspace Data

          
API keys, recent usage, receipts and provider policy are visible from the client side.

        

      

      

        
        
        
        
      

      

        
NamePrefixScopesStatusCreated