100xprompt connects to its models through your account. You connect once - sign in and paste your API key - and from then on, credentials stay on your machine and are reused automatically for every session.

​
Sign in to a provider

Suppose you’ve just installed 100xprompt and want to run your first session. Connect a provider first - one command walks you through it.
1

Run the login command

100xprompt auth login
2

Pick a provider

Choose from the live list. 100xprompt tells you which connection options each provider supports as you go.
3

Connect by plan or key

Sign in with an existing plan in your browser (OAuth), or paste an API key. 100xprompt confirms Login successful and stores the credential.
Not sure which provider to pick? Start with the recommended option at the top of the list - it works out of the box. You can connect more providers any time by running 100xprompt auth login again.

​
Connect by plan or by key

Providers accept one or both of two paths. Pick the one that matches how you already access the provider.
Some providers let you authenticate with an existing subscription instead of managing an API key. Choose the provider, and 100xprompt opens a browser authorization flow:
  1. 100xprompt shows an authorization URL.
  2. You approve access in your browser (or paste back a short code, depending on the provider).
  3. 100xprompt confirms Login successful and stores the connection.
Use this when you already pay for a plan and want it directly, with no separate key to create or rotate.
Not sure which path fits your setup? Match your case to the right way to connect.
I want to…Best way to connect
Use a consumer plan I already pay forSign in with your plan in the browser (OAuth)
Run locally with my own keyPaste an API key via 100xprompt auth login
Run in CI or a containerSet the provider’s API-key environment variable

​
Your 100xprompt account

Signing in to 100xprompt is all you need. Create an API key from your account at 100xprompt.com, paste it into 100xprompt auth login, and both models are ready in every session.
ModelBest for
FlashFast, lightweight, everyday steps
ProDeep reasoning, large refactors, and hard problems
Run 100xprompt auth list to confirm you’re connected, and see Models for how to select and switch between Flash and Pro once you’re signed in.

​
Understand where credentials are stored

Your credentials - API keys and signed-in sessions - are saved to a private auth.json file in 100xprompt’s local data directory on your machine. The file’s permissions are locked down so only your user account can read it. Credentials never leave your device except to authenticate with the provider you connected.
Treat auth.json like any secret: don’t commit it to a repository, paste it into a chat, or copy it to shared machines. To move to a new machine, sign in again there rather than copying the file.

​
List and remove credentials

To see everything you’ve connected - including provider environment variables active in your shell - run: 
100xprompt auth list
This prints each connected provider and how it’s authenticated (plan or API key), the location of your credentials file, and any provider environment variables 100xprompt detects. To disconnect a provider and delete its stored credential, run: 
100xprompt auth logout
You’ll pick the provider to remove from a list. This only affects the credential stored by 100xprompt; it doesn’t revoke the key on the provider’s side - do that from your provider’s dashboard if needed.

​
Supply keys with environment variables

You don’t have to run the login flow for every provider. Most providers are recognized automatically when their standard API-key environment variable is present in your shell. Set the variable and 100xprompt picks it up - no auth login required. 
# Example: expose your API key to 100xprompt in CI (illustrative name)
export PROVIDER_API_KEY="sk-..."
Run 100xprompt auth list to confirm which provider environment variables are active right now - they appear in the Environment section of the output.
Environment variables are convenient for CI, containers, and shared automation where you’d rather inject a key at runtime than store it on disk. For interactive local use, the auth login flow is usually simpler.
Both work. If you have a key set in your environment, 100xprompt can use it without you running auth login. If you want a stable, on-disk credential that survives new shells, use auth login to store it.
Yes - credentials are stored locally per machine. Run 100xprompt auth login on each device, or provide keys via environment variables in automated environments.
Run 100xprompt auth login again and pick a different provider. You can keep several connected at once and choose models from any of them.

Models

Choose which model drives each session and switch instantly between Flash and Pro.

Settings & Configuration

Configure defaults, provider options, and which providers appear in 100xprompt.json.

Security

How 100xprompt protects your credentials and data across your team.