> For the complete documentation index, see [llms.txt](https://docs.rtkdata.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rtkdata.com/reseller-hub/reseller-hub.md). # Reseller Hub: The RTKdata Partner Portal The RTKdata Reseller Hub is the partner portal for selling RTK corrections under your own name: create customers, provision NTRIP licenses, track usage and settle one monthly invoice. The **Reseller Hub** is the portal RTKdata partners use to run their own RTK business. You create your customers, provision NTRIP licenses for them, watch those licenses connect in the field, and settle everything with RTKdata on a single monthly bill. Your customers stay yours. They never see RTKdata pricing, and no other reseller ever sees your data. ![The Reseller Hub dashboard](https://3957820804-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FJflLSSoC9TU9MkwT5lbC%2Fuploads%2Fgit-blob-4474209faf920869911671e85d1640472181d689%2Freseller-hub-dashboard.png?alt=media) *** ## Who this section is for This section is written for **RTKdata resellers and partners**. If you are an end user connecting a rover or a drone to the correction service, start at the [Quick Start](/get-started/quick-start.md) instead. If you do not have a Reseller Hub account yet, see [Partner Program](/commercial/partner-program.md) or contact . *** ## The core loop Everything in the portal is built around one short loop, from a new customer to a working rover: 1. **Create the customer.** Name, optional email, your own reference number. 2. **Provision a license.** Pick the number of data streams and the term, and see the price before you confirm. Or start a free trial first. 3. **Deliver the credentials.** Email them to the customer, send them a login link to their own portal view, or copy the connection details yourself. 4. **Watch it work.** The license shows up on the live map as soon as the rover connects, with fix rate and session history. 5. **Settle once a month.** Everything you provisioned, renewed or upgraded in a month rolls into one bill from RTKdata. The target for steps 1 to 3 is well under a minute. *** ## What is in this section | Page | What it covers | | ------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | [Getting Started](/reseller-hub/getting-started.md) | Signing in, the first login tour, how the portal is laid out, your profile | | [Dashboard](/reseller-hub/dashboard.md) | Your KPIs, quick actions, and the customizable layout | | [Customers](/reseller-hub/customers.md) | Creating, editing, archiving and deleting customer records | | [Licenses & Provisioning](/reseller-hub/licenses.md) | Terms, trials, credentials, renewals, upgrades, suspensions | | [Billing](/reseller-hub/billing.md) | The monthly bill, tier discounts, payment, price snapshots | | [Usage & Live Map](/reseller-hub/usage-and-live-map.md) | Connections, fix rates, GPS tracks, the activity log | | [Troubleshooting](/reseller-hub/troubleshooting.md) | Diagnostics runbooks and escalating to RTKdata support | | [API](/reseller-hub/api.md) | Provisioning licenses straight from your own storefront: [v1](/reseller-hub/api/api-v1.md) for simple shop integrations, [v2](/reseller-hub/api/v2.md) for deeper ones | | [Customer Portal](/reseller-hub/customer-portal.md) | What your end customers see when you send them a login link, and the emails they receive | *** ## What you can and cannot see | You can see | You cannot see | | ----------------------------------------------------------------- | ---------------------------------------- | | Your customers, licenses and bills | Any other reseller's data | | The list price of every license and the tier discount you receive | Other resellers' conditions or discounts | | Usage, sessions and fix rates for your licenses | RTKdata's own upstream costs | The portal does not store what you charge your own customers. Your resale price is entirely your business. *** ## Good to know before you start * **Credentials are bound to a customer.** A license belongs to the customer it was provisioned for and is never reassigned to a different one. A new customer always gets a new license. * **Invoicing is monthly.** A term can run 1 to 11 months or 1 to 5 whole years, but RTKdata always bills you once a month, on one bill. * **Your discount grows with you.** Every bill applies the discount of the tier your active paid licenses reach. See [Billing](/reseller-hub/billing.md). * **An overdue bill has consequences.** Two weeks past due, new licenses and trials are paused; a month past due, renewals stop too. See [Billing](/reseller-hub/billing.md#when-a-bill-is-overdue). --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.rtkdata.com/reseller-hub/reseller-hub.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.