Start here: choose your path

What are you trying to do?

PrimeRouter connects model users with account suppliers. Choose your role before configuring anything.

Goal	Where to work	Start with
Use models in Codex, Claude Code or another tool	User Client	User quick start
Supply your model accounts and earn revenue	Partner Client	Partner quick start
Understand the request and trust boundaries	Technical guides	Architecture

One website account can have both user and partner permissions. Visible menus depend on the permissions actually granted by the platform.

The shortest user workflow

1. Sign in to the website.
2. Create a User API Key and configure an available routing scope.
3. Install User Client and sign in with that platform key.
4. Create a local key inside the Client.
5. Give your tool the local endpoint and local key.
6. Send a short request and inspect Usage records.

Balance, model permissions, price limits and available supply can all affect the result. Follow User quick start for each screen.

The shortest partner workflow

Obtain partner access, create a Partner API Key and sign in to Partner Client. Connect an account, configure its price and protection, and explicitly enable scheduling and a public or private supply scope.

Importing credentials does not automatically make an account available to customers. Supplying a locally signed-in account consumes its subscription allowance; read Local account supply before enabling it.

Common questions

Do I need both Clients? Model users need User Client. Suppliers need Partner Client. Install both only when you do both jobs.

Can the website replace User Client? The website manages configuration and records. Your local API endpoint runs in User Client, which must remain running while tools use it.

Why is a button missing? Check your role and permissions, then the account state. A documentation link does not grant access to an administrative operation.

Continue with Installation and Keys explained.