Demo environment. Credits, keys, selections, limits, and usage shown here are simulated. No customer payments or provider services are active.
PREVIEWA clearer way to build.
One place for credits, API access, and spending controls.
xAPI-managed charges would use credits. Provider-direct base bills stay with your provider.
Selected APIs
Your planned stack and account choice in one workspace.
Spending controls
Set demo caps on xAPI credit charges.
For xAPI-managed services, credits would cover the service base charge plus a 1% xAPI fee. With provider-direct billing, the provider bills the base charge and the xAPI fee is separate. Adding credits has no xAPI transaction fee. Service prices are unpublished.
API catalog.
Explore services planned for one xAPI key, with a payer choice per service.
For each service, save either an xAPI-managed account or your own provider account. If you choose your account, you can also save a payment preference. These are planning choices only: no provider credentials are collected, no payment is taken over, and no service is live.
Connections.
Review how each selected API would connect when services launch.
This preview cannot accept a provider key, start OAuth, activate an xAPI-managed account, or route a service request. Choose an account and payer preference in the catalog to preview the next steps here.
Selected service plans
0 services selected for preview
Credits & payments.
Explore demo credits and the planned route to a real prepaid balance.
These credits are simulated and cannot pay a provider. The xAPI fee applies to service charges, not credit purchases.
Hosted checkout is planned.
Stripe is selected for a future secure checkout. A verified customer account, one durable wallet authority, and payment confirmation are required first.
Real payments are not configured in this preview.Service fee
The xAPI fee is shown separately on each service charge. The xAPI operator sets this rate. Credit purchases have no xAPI transaction fee.
A verified account would see a clear USD purchase amount and the wallet receiving it.
Card details would be entered with the payment provider, never in this demo console.
Credits would appear only after the payment is verified and posted once to the selected wallet.
A return from checkout would show payment status, not immediately credit the balance. No checkout session or real charge can be started here.
Usage & spend.
See xAPI credit charges and future service usage in one view.
Recent activity
Each charge will show the service base charge and xAPI fee separately.
| Service | Date | Service base charge | xAPI fee | Total |
|---|
All usage is demo data. Future records should separate xAPI charges from provider-direct base bills. The method for collecting the xAPI fee on provider-direct usage is still undecided.
Spending limits.
Set demo dollar caps on xAPI credit charges. Routed-usage controls are planned.
Global monthly credit cap
This demo cap tracks charges to xAPI credits, including applicable xAPI fees. It does not cap supplier bills paid directly.
When a customer provider account sends calls through the future xAPI gateway, xAPI would meter and limit those calls even if the provider bills the base charge directly. These usage limits would be separate from the demo credit caps below. Calls made outside xAPI cannot be metered or capped here.
Per-service credit caps
Optional demo ceilings on each service's xAPI credit charges. They do not cap off-platform provider calls or activate services.
API keys.
One project key is planned for your entire xAPI stack.
Demo keys cannot call providers. Key creation and revocation here exercise local prototype behavior only. Never use a demo key in production or share it publicly.
Project key
Demo project · one key for the planned gateway
Build a shortlist from the planned catalog.
Choose global and service caps before usage.
A single xAPI key is planned for James or another coding system.
Settings.
Workspace identity and the planned James connection.
Workspace
Your account and project in this local prototype.
- Workspace
- Demo workspace
- Project
- demo-project
- Currency
- USD
- Services
- Not live
One balance with James.
If James has verified customer credits, the planned opt-in will connect to a trusted wallet authority without copying credits into a second balance. This connection is not live.
NOT CONNECTED