> **Building with AI coding agents?** If you're using an AI coding agent, install the official Scalekit plugin. It gives your agent full awareness of the Scalekit API — reducing hallucinations and enabling faster, more accurate code generation.
>
> - **Claude Code**: `/plugin marketplace add scalekit-inc/claude-code-authstack` then `/plugin install <auth-type>@scalekit-auth-stack`
> - **GitHub Copilot CLI**: `copilot plugin marketplace add scalekit-inc/github-copilot-authstack` then `copilot plugin install <auth-type>@scalekit-auth-stack`
> - **Codex**: run the bash installer, restart, then open Plugin Directory and enable `<auth-type>`
> - **Skills CLI** (Windsurf, Cline, 40+ agents): `npx skills add scalekit-inc/skills --list` then `--skill <skill-name>`
>
> `<auth-type>` / `<skill-name>`: `agentkit`, `full-stack-auth`, `mcp-auth`, `modular-sso`, `modular-scim` — [Full setup guide](https://docs.scalekit.com/dev-kit/build-with-ai/)

---

# Bring your own credentials

By default, Scalekit uses its own OAuth app credentials when your users go through the OAuth consent flow. This works for development and testing, but in production your users will see Scalekit's name and branding on the consent screen, not yours.

**Bring your own credentials** lets you replace Scalekit's shared OAuth credentials with your own. Once configured, users see your app name, logo, and terms on every OAuth consent screen.

## What changes when you use your own credentials

- **Consent screens** display your application's name and branding
- **Rate limits and quotas** are tied to your OAuth app, not Scalekit's shared pool
- **Provider relationship** is direct, and your OAuth app appears in provider dashboards and audit logs
- **Compliance**: useful if your organization requires a direct relationship with each OAuth provider

Nothing changes in your code or the Scalekit SDK. The switch is purely a dashboard configuration on the connection.

## Configure your credentials

1. ### Copy the redirect URI from Scalekit

   Go to **Agent Auth > Connections** and click **Edit** on the connection you want to update. Select **Use your own credentials**. The form expands and displays a **Redirect URI**. Copy it.

2. ### Register your OAuth app with the provider

   In the provider's developer console, create a new OAuth app (or use an existing one). Add the Redirect URI you copied in the previous step to the list of authorized redirect URIs.
**Redirect URI must match exactly:** The URI must match character-for-character. A mismatch will cause OAuth flows to fail with a redirect_uri_mismatch error.

   The provider gives you a **Client ID** and **Client Secret** after registration.

3. ### Enter your credentials and save

   Back in Scalekit Dashboard, enter the **Client ID** and **Client Secret** from your OAuth app and click **Save**.

   All new OAuth flows for this connection will now use your credentials.

## Existing connected accounts
**Existing connected accounts are not affected immediately:** Switching credentials does not re-authorize users who are already active. They continue using the previous credentials until they re-authorize. If you need all users to see your branding immediately, generate new authorization links and prompt them to re-authorize.

---

## More Scalekit documentation

| Resource | What it contains | When to use it |
|----------|-----------------|----------------|
| [/llms.txt](/llms.txt) | Structured index with routing hints per product area | Start here — find which documentation set covers your topic before loading full content |
| [/llms-full.txt](/llms-full.txt) | Complete documentation for all Scalekit products in one file | Use when you need exhaustive context across multiple products or when the topic spans several areas |
| [sitemap-0.xml](https://docs.scalekit.com/sitemap-0.xml) | Full URL list of every documentation page | Use to discover specific page URLs you can fetch for targeted, page-level answers |