Galliun is payment infrastructure built around a small set of platform primitives. Understanding these helps you integrate correctly on the client and configure endpoints on the server.
Platform flow
developer → project → registered API → endpoint
→ accepted payment rails → protected request → payment → usage → receipt
Every paid call to a developer's protected API follows this path.
Key concepts
Protected API endpoint
A paid endpoint exposed through /p/:projectSlug/*. Example:
POST https://api.galliun.com/p/acme/search
Payment requirement
The 402 Payment Required response that tells the SDK how much to pay, which chain, and the splits[] recipients for provider and platform fee legs.
Payment proof
Signed/verified transaction data sent back in the X-PAYMENT request header on retry.
Request hash
A SHA-256 binding between payment, endpoint, HTTP method, request body, price, and expiry. Prevents payment reuse across different requests.
Wallet adapter
The object that lets the SDK request exact_split payments from Sui or Solana. See Wallet Adapters.
Ownership model
Projects belong to organizations. Business developers manage their own projects, APIs, endpoints, and payment rails via the dashboard.
Unified API domain
All requests go to https://api.galliun.com. Optional public aliases on endpoint records resolve through the same platform execution layer as /p/:projectSlug/* routes.