⌕
Discover
James or another coding tool asks xAPI which capabilities suit your project. The catalog returns verified availability, modes, and prices.
THE SERVICE LAYER, IN DESIGN
Everything your app needs.
One place to start.
Explore a planned way to access models, search, data, and compute through one xAPI project. Choose an xAPI-managed account or your provider-issued key or OAuth grant, service by service. Every capability below is clearly marked until it can actually be used.
See how it would work✳Planned product experience. No connected services are offered in this preview.
A SINGLE ACCESS LAYER 01 / 04
xAPI
ModelsPlanned
SearchPlanned
DataPlanned
ComputePlanned
ONE PROPOSED APINO LIVE ROUTES YET
0live services
4planned capabilities
Pendingservice base rates
1%configured service fee
THE CATALOG
Find the right capability.
Know its real status.
These are proposed xAPI categories and provider candidates. Connection mode would be selected per service. A listing is not a connected service, and no base rate is published yet.
Loading planned connection choices…
No live integrations
Loading public catalog…
THE PROPOSED FLOW
From idea to service,
with a choice of connection.
For each service, choose an xAPI-managed account or authorize your provider-issued API key or OAuth grant. BYOK credentials would be stored server-side with consent, never a provider login password or public chat message.
✓
Choose & approve
Select a service and connection mode, authorize your project, and set optional limits for calls routed through xAPI.
↗
Build
Your project calls xAPI with a scoped key. xAPI would route calls through the chosen connection and report usage. Neither mode is live yet.
One interface, typed operations.Models, search, databases, and GPU jobs each need their own request shape. The versioned customer API shown here is a design, not a live endpoint.
Ask about the API A CLEARER WAY TO PAY
Shared credits.
Clear limits.
In planned xAPI-managed mode, the base charge and the configured xAPI fee would use xAPI credits. With your provider key or OAuth grant, the provider bills the base directly unless xAPI payer takeover is verified. The configured fee applies to routed use; its collection method is planned. No payments are live.
xAPICONCEPT WALLET
Example credit balance$100.00
Illustration only · no customer funds exist
xAPI-managed services · proposed•••• 2026
Add credit to one wallet
For xAPI-managed use, the base charge and the configured xAPI fee would use xAPI credits. No service fee applies to a credit top-up.
Know which party bills you
With your provider key or OAuth grant, the provider bills the base directly unless xAPI payer takeover is verified. The configured xAPI fee is separate; collection is still planned.
Limit routed usage
Global and per-service limits are planned for calls through xAPI. Calls made directly to a provider outside xAPI cannot be capped by xAPI.
ILLUSTRATIVE PAYER OUTCOMES
Enter an example service base charge and compare payer paths. Actual base rates are unpublished.
Configured 1% fee $0.10Combined amount $10.10
xAPI payer: $10.10 would come from xAPI credits, including the base charge and configured fee.
BYOK can use xAPI as payer only where provider payment takeover is verified. Provider-direct fee collection is still planned. These numbers are examples, not live charges.
WHAT'S NEW
Updates, without the hype.
This feed records additions to the prototype. A provider will appear as launched only after its xAPI integration and pricing are verified.
Loading updates…
No production service additions have been announced.
CUSTOMER SERVICE, IN PREVIEW
Questions? Ask James.
James answers public questions about connection modes, pricing, limits, and launch status. This local preview uses checked public facts. With an explicit James test connection, it can ask James AI. It cannot inspect accounts, take payments, or run xAPI services.
✳Public facts only · no secrets · request limits on every question
J✳
JamesPublic service preview
Local answersDo not enter passwords or API keys.