Skip to content
SlashClone

Docs

Keys and accounts a kit needs

Set up a kit that works with another service, using your own key, without handing that key to anyone.

Some kits work with another service, like your Stripe account, a HubSpot list, or an email sender. To reach your account there, the kit needs a key from that service. This guide shows where to see what a kit needs, how to get the key, and where to keep it.

What a key is

A key is a secret code a service gives you so a kit can use your account there. Anyone who has it can act as you in that account, so treat it like a password. You keep it on your own computer. SlashClone never asks for it, shows it, or stores it.

See what a kit needs

On a kit page, look at Will this work for me? under the main button.

  • Effort tells you how much setup to expect. Works out of the box means no accounts, keys, or connectors. Needs about 10 minutes of setup means you sign in to an app, add a connector, or make a key first.
  • You need lists each thing: a Claude plan, accounts with other apps, connectors, programs, and keys. A key shows by its name, such as STRIPE_API_KEY.

Click any item to open its steps. For a key you see What it is, Where to get it, and Keep it safe. For an app, there may also be Connect it, which tells you how to add its connector to Claude.

Under a result, a kit page may also say To get this with your own data, you need: with a Where to get it link for each key.

Get the key

Follow the link under Where to get it and make the key in your own account.

SlashClone knows the keys of some well-known services by their names: Stripe, HubSpot, OpenAI, Anthropic, Supabase, Resend, and Alpaca. For those keys, the link always goes to that service's own site, even if the kit's maker linked somewhere else. For any other key, the link is the one the maker gave, so check the address before you sign in.

If the service offers test keys, like Stripe's test mode or Alpaca's paper trading, start with those.

Where to keep it

claude.ai has no place to keep keys. Use a kit that needs one in Claude Code, in the terminal or the desktop app's Code tab.

On your own computer, put the key in one of two places:

  • Your shell profile, such as ~/.zshrc, as a line like export STRIPE_API_KEY=your-value.
  • The env section of ~/.claude/settings.json, for Claude Code.

Never paste a key into a chat, a kit, or a comment. If you did, delete that key at the service and make a new one.

SlashClone never sees it

The kit runs where you use Claude Code, and the key stays there. SlashClone shows only the key's name and where to get it. The automatic check also stops a kit when it finds a key written into its files.

When a kit asks for a key it should not need

Compare the list with the job. A kit that formats meeting notes has no reason to need a payment key. The automatic check looks for keys a kit's files read but did not list, so You need is the place to look. Then open What it can access. If the kit connects to a site that has nothing to do with the service the key is for, ask why.

If something does not add up:

  • Do not add the kit.
  • Ask the maker why in Comments on the kit page.
  • If it looks like it is after your key, use Report this on the kit page.

Reading a kit page explains the rest of what you see there.

Your cookie choices

We use cookies you can say no to for analytics, ad measurement, and embedded videos. Signing in works either way. You can change this any time from Cookie settings at the bottom of every page. What we use

Cookies that keep you signed in and remember these choices are always on. Everything else is off until you turn it on.