# One API Key per Tool: Set Up Appalize the Right Way

> Create an Appalize API key, limit what it can touch, and see how much it's used, all in under three minutes. This tutorial is for developers who want to connect a script or an AI agent like Claude or Cursor to their Appalize data.

- Lesson page: https://www.appalize.com/tutorials/one-api-key-per-tool-set-up-appalize-the-right-way
- YouTube: https://www.youtube.com/watch?v=yXUXUlTNsU8
- Duration: 2:38
- Section: Automation & AI Agents (lesson 48 of 50)
- Appalize panel pages (sign-in required): https://app.appalize.com/api-dashboard
- Updated: 2026-11-16

## What you'll learn

- Where to create a key on the API & Keys page, and why you must copy it right away: Appalize shows the full key only once.
- How your tool sends the key: in a header called x-api-key.
- How Edit permissions works. An MCP (Model Context Protocol) client only sees the tools its key allows, so a read-only tool should not get write access.
- Where to check usage: the Usage tab, plus Requests and Last used for each key in the Keys tab.
- Where the REST reference and the MCP docs are, and where your key goes in the config block.
- One habit that saves trouble later: one key per tool, named after the tool. If one key leaks, you revoke only that key and the others keep working.

## Chapters

- [0:00](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=0s) Create, limit, track in under 3 minutes
- [0:12](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=12s) Create an API key (shown only once)
- [0:42](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=42s) Edit permissions: what your agent can see
- [1:10](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=70s) Check usage per key
- [1:32](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=92s) API Docs and MCP Docs
- [1:54](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=114s) Tip: one key per tool
- [2:24](https://www.youtube.com/watch?v=yXUXUlTNsU8&t=144s) Recap and next: Custom Dashboards

## Transcript

Narration of the video with timestamps (minutes:seconds). On-screen steps can add detail; masked values (campaign names, money) are placeholders.

### 0:00 Create, limit, track in under 3 minutes

[0:00] In under three minutes, you'll create an Appalize API key, limit it before it can do damage, and see how much it's used.
[0:07] Building a script or an AI agent?
[0:10] Start here.
[0:11] Let's create the first key.

### 0:12 Create an API key (shown only once)

[0:12] Open API and Keys, and click Create API Key.
[0:16] Give the key the name of the tool that will use it.
[0:19] I'll call this one claude-desktop.
[0:21] That's just an example.
[0:23] Then confirm.
[0:24] Common mistake: closing this window too fast.
[0:27] Appalize shows the full key only once.
[0:30] Copy it now, and save it in a password manager or an environment variable.
[0:35] Your tool sends this key in a header called x-api-key.
[0:39] A new key should not have more power than it needs.

### 0:42 Edit permissions: what your agent can see

[0:42] On the claude-desktop row, open the menu and pick Edit permissions.
[0:47] Here's the rule.
[0:48] M-C-P, the Model Context Protocol, is how an AI agent talks to Appalize.
[0:54] An M-C-P client only sees the tools its key allows.
[0:58] So switch off everything this tool doesn't need.
[1:01] If it only reads your keywords and rankings, don't give it write access.
[1:05] Then save.
[1:06] Now, how do you know the key is actually being used?

### 1:10 Check usage per key

[1:10] Open the Usage tab on the same page.
[1:12] This is where you see how your keys are actually being used.
[1:15] In the Keys tab, check each key's Requests and Last used.
[1:20] That's why you named it after its tool.
[1:22] I'd check this once a week.
[1:23] Appi tip: if a key shows activity from a tool you stopped using, revoke that key.
[1:29] Once the key works, you need the reference.

### 1:32 API Docs and MCP Docs

[1:32] Click API Docs.
[1:33] This is the REST reference, for your own scripts.
[1:36] For AI agents, open the M-C-P docs on appalize dot com.
[1:40] Copy the config block into Claude or Cursor, and paste your key where it says YOUR API KEY.
[1:47] Not sure which permission a tool needs?
[1:49] When your agent connects, it lists the tools its key allows and the permissions each needs.

### 1:54 Tip: one key per tool

[1:54] One last habit saves you a lot of trouble.
[1:57] Here's the habit: one key per tool.
[2:00] Claude, Cursor and your script each get their own.
[2:03] Say your script's key leaks.
[2:05] You revoke that one key.
[2:07] The others keep working.
[2:08] With one shared key, there is no that one key.
[2:12] Revoke it, and everything stops.
[2:14] The docs add: one key per Appalize account or client profile.
[2:19] If you only remember one thing: name every key after the tool that uses it.

### 2:24 Recap and next: Custom Dashboards

[2:24] So: one key per tool, only the permissions it needs, and a look at its usage.
[2:29] Next, I'll show you Custom Dashboards, where you build one view of the numbers you check most.
[2:35] Every tutorial is on appalize dot com slash tutorials.

## Topics

appalize api key, api key tutorial, create api key, api key permissions, api key usage, revoke api key, api key best practices, mcp, model context protocol, mcp setup, claude mcp, cursor mcp, ai agent api key, aso automation

## More lessons

- Previous: [Give Your AI Agent Real App Store Data (MCP)](https://www.appalize.com/tutorials/give-your-ai-agent-real-app-store-data-mcp.md)
- Next: [Too Many Charts? Build One ASO Dashboard](https://www.appalize.com/tutorials/too-many-charts-build-one-aso-dashboard.md)
- All lessons: https://www.appalize.com/tutorials.md

---
Source: Appalize (https://www.appalize.com). Content license CC-BY-4.0; cite the lesson page.
