# Pass-through billing Every sim is billed to the account whose key signed the request, which gives you two ways to cover the sims your integration runs. By default, your key pays: you hold one Simmit key, your account is billed in credits, and you build whatever pricing you want on top, whether that's a free tier, paid access, or nothing. This is the path the rest of the docs assume; see [Pricing](/docs/pricing) for credit packs and [Credits](/docs/api/credits) for how each sim is metered. With pass-through billing, each user brings their own Simmit key instead, and their sims are billed to their account rather than yours. ## How it works Each user supplies their own key, and your integration sends it as that user's bearer token, exactly as it would send its own: ```text Authorization: Bearer ``` Nothing else about the API changes: same endpoints, same payloads, same responses. The only difference is which account the sim bills. How your integration collects and holds each user's key is up to you; a key is a secret that draws on that user's credits, so handle it the way you would any other API credential. ## Where your users get keys Send your users to [app.simmit.com](https://app.simmit.com) to create an account and generate a key. That's the account surface built for players, separate from the developer dashboard at `dashboard.simmit.com` that you use to build and run integrations. Your users don't need a developer account; they sign up, generate a key, and provide it to your app. ## Branded onboarding If you'd rather your users land on a signup page named for your app instead of the generic one, [get in touch](/docs/contact) and we'll set one up. --- _HTML version: https://simmit.com/docs/pass-through-billing · Full docs index: https://simmit.com/llms.txt_