> ## Documentation Index > Fetch the complete documentation index at: https://docs.tybritelabs.com/llms.txt > Use this file to discover all available pages before exploring further. # Agencies — run commerce as your own platform > Run Galactic Core as your own branded commerce platform: your name, your domain, your plans and prices, your payment processor, your merchants. # Agencies — run commerce as your own platform Most of this documentation is written for someone building **on** Galactic Core. This page is for someone building **a business on top of it** — an agency, a studio, or a software company whose own customers are merchants. You bring the merchants and the brand. Galactic Core is the commerce engine underneath, and it stays out of sight: your merchants sign in to your product, at your domain, and the API keys they copy carry your name, not ours. The chain looks like this: ``` Galactic Core → your platform → your merchants → their customers ``` You are a distribution layer, not a reseller of someone else's dashboard. Your name, logo, domain, sender addresses, and API key prefix. Merchants never encounter Galactic Core. Name your tiers, set your prices, charge with your own payment processor, and keep the difference between what you charge and what you pay us. *** ## What your merchants see A merchant you onboard gets the full Galactic Core admin — catalog, orders, payments, the storefront API, the assistant — under your identity: | Surface | What it shows | | ------------- | ------------------------------------------------------------------ | | The app | Your logo, favicon, browser title, brand name, and product wording | | The domain | `studio.youragency.com`, or a subdomain we host for you | | Email | Sent from your address, on your verified sending domain | | API keys | `youragency_sk_live_…` instead of `tybrite_sk_live_…` | | The assistant | Named by you, if you'd rather it wasn't "Raf" | Branding is presentational. It changes what a merchant reads, never how commerce behaves: orders, payments, and webhook signatures are issued and verified by Galactic Core exactly as they are for a direct store, so integrity is never something a white-label layer can weaken. Branding covers identity — name, logo, wording, domain, sender, key prefix. The interface keeps its own visual design; colors are not currently themeable. *** ## Onboarding merchants You invite a merchant from your dashboard, choosing the plan tier they start on. They receive a branded invitation, and accepting it provisions a store that belongs to your platform from the first moment — never a Galactic Core store that is later transferred. Each invitation is single-use and expires, and is bound to the address you sent it to. Merchants you onboard get the same free trial as any other, **and a store on trial costs you nothing** — you begin paying for it when the merchant starts paying you. You can move a merchant between tiers at any time. *** ## Your plans, your prices This is the part that makes it a business rather than a rebrand: **price is data you own.** Galactic Core defines what each tier can *do*. You decide what the tiers are *called* and what they *cost*: Plan names, monthly and annual prices, which tiers you offer at all, and the currency you charge in. What each tier includes — the features and the limits. You price and package capabilities; you cannot grant one we don't ship, or raise a cap beyond what a tier allows. You enter a monthly and an annual price and the annual saving is worked out from the two, so the discount you advertise can never drift from the prices you actually charge. ### Getting paid Two ways to run it: * **Invoice your merchants yourself.** The default. You see what each merchant owes, and you collect it however you already collect money. * **Let them subscribe in-app.** Connect your own payment processor — Stripe, Paystack, Lemon Squeezy, or Paddle — and merchants pick a plan and pay inside the product. The charge settles **directly to you**; Galactic Core never holds your revenue and never sits between you and your customer. If you'd rather bill through a processor we don't support natively, you can supply your own billing integration and it will be used for subscriptions, credit top-ups, and renewals alike — see [Custom Integrations](/extensions#billing-your-own-merchants). ### What you pay us Separately from all of that, Galactic Core invoices **you** at wholesale: a base fee per active merchant store, plus metered usage. Your dashboard shows revenue, wholesale cost, and the margin between them per merchant, so an unprofitable account is visible before it becomes a problem. Merchants on a free trial are not billable to you. *** ## Domains Merchants can reach your platform two ways: * **A subdomain we host** — `youragency.gc.tybritelabs.com`. Works immediately, nothing to configure. * **Your own domain** — `studio.youragency.com`. Add the domain in your dashboard, create the DNS records it shows you at your registrar, and the certificate is issued automatically once they resolve. *** ## Sign in with your platform If you build tools of your own — a reporting dashboard, an inventory sync, an onboarding wizard — your merchants can authorize them the same way any application authorizes against Galactic Core, except the consent screen is yours: your name, your domain. Those applications are scoped to your platform. A merchant on your platform can only authorize your applications, and yours can only reach your merchants. See [GC Connect](/gc-connect) for the flow itself. *** ## Assistant credits The in-app AI assistant runs on credits. Merchants top up through **your** processor at a rate you set, and Galactic Core meters what they consume onto your wholesale bill — so, as with plans, the spread is yours. You can also cap what any one merchant is able to spend, independently of what their plan would otherwise allow. *** ## Isolation Every merchant store carries the identity of the platform that owns it, and that ownership is the data boundary. Your dashboard reaches your merchants and no others; a direct Galactic Core store is never visible to you, and yours are never visible to another platform. Your team members have roles of their own — owner, admin, and member — which control who can invite merchants, change pricing, and manage domains. *** ## Where things live Agency configuration is administrative, so it lives in your dashboard rather than the public API — there are no `/v1/agency/*` endpoints to call. Your merchants' stores use the same API, SDK, and webhooks documented throughout the rest of this site; nothing about the commerce surface changes because a store belongs to a platform. The one developer-facing piece is the billing integration described above, documented with the other [Custom Integrations](/extensions#billing-your-own-merchants). Agency access is enabled per platform. Tell us what you're building and we'll set you up.