Loading...
Loading...
AI Usage Distribution and Settlement Layer
Razzhood packages AI usage into listings, routes requests through a hosted runtime, and keeps billing, split, attribution, and balance inside a ledger-centered money loop.
Usage -> billing -> split -> balance
usage -> billing -> split -> balance
Architecture
The public surface stays thin. Listing definition, runtime ingress, and creator/admin operations all converge on ledger-backed settlement truth.
Market Surface
Home, listing page, share landing, creator surface, and discoverability entry points.
Listing OS
Offer packaging, pricing rules, runtime config, publish/review states, and share config.
Runtime Gateway
Hosted request intake, validation, provider routing, idempotency, and request lifecycle control.
Ledger Core
Usage, billing, split, attribution, and balance are the only financial source of truth.
Control Plane
Creator Studio, creator dashboard, admin review, and repair operations for sustainable runtime commerce.
Market Surface
The first production surface should help people discover a listing, invoke it, share it, and preserve attribution — without burying the product under legacy premium-membership flows.
Money Loop
Each hosted runtime request should move through a real accounting chain instead of stopping at a marketing or subscription shell.
Listing OS
Define offer packaging, price, runtime config, share config, and publish/review states in one place.
Runtime Gateway
Accept hosted runtime requests, validate them, route them to the configured provider, and preserve correlation IDs.
Ledger Core
Every public request should still resolve back to usage, billing, split, attribution, and balance truth.