Docs · API Keys

API keys

Every request to the LoopSkill API — installs, manifest fetches, bundle syncs — is authenticated with an API key. Here's how keys work, how to use them, and how to rotate them safely.

How keys work

LoopSkill API keys use the prefix rec_live_ followed by a random 32-character string. Pass them in the x-api-key request header:

curl https://recipes.wisechef.ai/api/skills/search \
  -H "x-api-key: rec_live_your_key_here"

The key encodes your subscription tier. Free keys can browse and install free skills. Pro keys unlock the full paid catalog. Pro+ keys additionally enable bundle sync and client deployment endpoints.

Per-bundle scoping (Pro+)

Pro+ accounts get up to 20 API keys. Each key can be scoped to a single bundle — meaning it will only serve the skills in that bundle and reject requests for anything else. This is how you safely hand a key to a client's agent without giving it access to your entire private catalog.

• Create a labeled key from /library and assign it to a bundle
• Share that key with the client — they can only access the skills you explicitly included in the bundle
• Pro accounts: 1 key total (not bundle-scoped). Upgrade to Pro+ for multi-key scoping.

Rotating a key

Go to /library, find the key you want to rotate, and click Regenerate. The old key is invalidated immediately — any agent or process using the old key will start receiving 401 Unauthorized responses.

The new key is shown once. Copy it immediately and update your RECIPES_API_KEY environment variable on every agent that uses that key. There is no grace period — the old key stops working as soon as you confirm regeneration.

Per-key install count

Each key tracks a running install count — the number of times a skill has been installed using that key. This count is visible in the library dashboard next to each key.

If you label keys by agent or machine (e.g. laptop-alice, server-prod), the install count tells you exactly which agent installed what and how many times — without any telemetry beyond the install event.

Setting your key

Export it as an environment variable before running your agent:

export RECIPES_API_KEY=rec_live_your_key_here

For MCP server setups (Claude Desktop, Cursor, Cline, Continue), pass the key in the env block of your MCP config — see MCP setup for the exact JSON shape.