Platform

What the platform is, and how it runs

Nexora-AI is a sector-agnostic B2B multi-tier compute resale and distribution platform. Upstream are contracted model API channels; at the centre are platform governance and settlement; downstream are institutional white-label relays and end users.

Three roles

Product and brand narrative

A clear information architecture that explains the model, the three consoles, the core capabilities and the differentiators: white-label relay, contract verification, multi-channel comparison, four-pool settlement.

Registration and conversion

Institution sign-up, user sign-up, supplier onboarding and console entry points — a complete path from awareness to an opened account.

Compliance base

Terms of service, privacy policy, supplier and channel agreements, funds and refund rules, content safety policy, SLA and legal notices, all in full.

Four audiences

Institutions and channel partners

Buy compute with prepaid balance, apply as suppliers, operate white-label relays.

End users

Choose channels, apply for whitelists, submit requests and call models.

Suppliers

Approved and prospective suppliers: submit credentials and keys, post deposits, supply and share revenue.

Partners and public

Understand the model, explore cooperation, assess platform capability.

Three-console responsibilities

This site introduces and channels traffic; after signing in you enter the console that runs the actual business.

Console	Role	Responsibilities
Admin (grid)	Platform controller	Opens institutions, approves suppliers, maintains model library and official account pool, approves official accounts and whitelists, verifies contracts, governs four fund pools and settlement
Institution (core)	Channel operator	Buys compute via prepaid balance, applies to become a supplier, applies for official accounts and whitelists, publishes purchase demand and takes community orders, runs white-label relay
User (node)	Consumer	Chooses channels by value, applies for official accounts and whitelists, submits purchase requests with contracts and tracks orders; submits only, never takes orders

Admin console

grid.nexora-ai.solutions

Institution console

core.nexora-ai.solutions

User console

node.nexora-ai.solutions

The business loop, seven steps

1
Demand submitted
A user submits a purchase request with a contract; the contract underpins later verification and settlement.
2
Contract verified
Admin verifies contract authenticity and key ownership, then publishes to the community.
3
Order taken
An institution takes the order in the community, matched on scale and available supply.
4
Prepaid sourcing
The institution buys compute with prepaid balance; funds land in the prepaid pool.
5
Compared call
The same model is compared across channels on price, latency and value.
6
Consumption and fees
Orders track consumption end to end; the tiered service fee is accrued.
7
Settlement and withdrawal
Supplier proceeds land in the earnings balance; withdrawal after approval, 2% fee.

Four fund pools, strictly isolated

Prepaid, earnings, deposit and quota funds never cross-cover. Every deduction follows a fixed order.

Prepaid balance

Consumption only, no withdrawal

Compute purchase funds from institutional and user top-ups; usable only for model invocation.

Earnings balance

Withdrawal after approval, 2% fee

Revenue share for suppliers and institutions, paid out after an application is approved.

Frozen deposit

Performance guarantee, confiscable on breach

Supplier performance deposit securing quality and compliance; not usable for consumption.

Consumption quota

Read-only

A quota view tracked per sub-account; display only, never a movable balance.

Two easily confused concepts

Admin “supplier onboarding”

This is the platform's approval process for supplier applications. Suppliers submit entity credentials, model details, pricing, authorisation proof and API keys; admin tests connectivity, functionality, pricing, latency and stability, then the supplier posts a deposit, enters the whitelist and gains tier permissions. Only approved suppliers see order volume and revenue management.

“Upstream resource pool”

The model API channels contracted or uploaded by users or admin — the underlying supply for model invocation. Upstream pools and supplier onboarding are two sides of the same coin: one governs channels, the other governs supplying entities.