> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wpos.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Partner Program

> Resell WPOS under your own brand: provision customer accounts, run the agent on their sites, and embed a white-label assistant in your own product.

The Partner Program lets an agency or platform operate WPOS on behalf of its own
customers, under its own brand. You provision customer accounts by API, run the
WPOS agent headlessly on their sites, embed a branded assistant inside your app,
and settle credits on your own terms. Your customers see your name, not ours.

<Note>
  This section is for partners building on WPOS. If you operate your own sites,
  start with the [Workspace](/agencies/workspace) instead. The Partner Program is
  the layer above that: you operate WPOS for other people.
</Note>

## Two ways to work

Every partner gets both, and most use both.

<CardGroup cols={2}>
  <Card title="Partner Dashboard" icon="gauge" href="/partners/dashboard">
    A self-serve control panel for your team: create and manage customer
    accounts, watch build jobs, and configure webhooks. No code required.
  </Card>

  <Card title="Partner API" icon="code" href="/partners/api-reference">
    A frozen HTTP API for provisioning accounts, running build jobs, and
    embedding the assistant. This is how you wire WPOS into your own product.
  </Card>
</CardGroup>

## What you can do

* **Provision customer accounts** on demand, each tied to your own reference id,
  with no passwords and no WPOS-branded billing. See [Accounts](/partners/accounts).
* **Run the agent on a customer site** with a structured instruction, then poll
  for the result. See [Build jobs](/partners/build-jobs).
* **Embed the assistant** inside your product for your operators and your end
  customers, fully branded. See [Embed the assistant](/partners/embed).
* **White-label every surface** your customers touch: the in-site assistant, the
  embedded chat, and the sites you hand off. See [Branding](/partners/branding).
* **Receive lifecycle events** as signed webhooks: a site connected, credits
  running low, a build job finished. See [Webhooks](/partners/webhooks).

## How billing works

Customer accounts you provision are marked partner-managed. They carry no
WPOS-facing checkout: the customer never sees a WPOS bill, and the WPOS Stripe
surfaces are closed to them at the server. You hold the credits, you grant them
to accounts as you see fit, and you bill your customer however you like.

## Getting access

Partner access is enabled by WPOS, not self-serve, so we can set your plan terms,
account limits, and default branding with you. Once your account is enabled as a
partner, the [Partner Dashboard](/partners/dashboard) unlocks in your WPOS account
automatically, and we issue the API key you integrate against.

<Card title="Apply to the Partner Program" icon="envelope" href="mailto:partners@wpos.ai">
  Email [partners@wpos.ai](mailto:partners@wpos.ai) and we will set you up.
</Card>

## Next

<CardGroup cols={2}>
  <Card title="Concepts" icon="diagram-project" href="/partners/concepts">
    The handful of ideas the rest of this section builds on.
  </Card>

  <Card title="Quickstart" icon="rocket" href="/partners/quickstart">
    Provision an account and run your first build job.
  </Card>
</CardGroup>
