---
canonical: https://docs.jentic.com/guides/credentials/get-your-api-key/
representation: markdown-alternate
# Canonical page: https://docs.jentic.com/guides/credentials/get-your-api-key/
# This is the Markdown alternate of the page above.
title: "Jentic Agent API Key (Archived)"
description: >-
  Generate a Jentic Agent API Key that authenticates SDK and MCP requests and scopes
  access to only the APIs and workflows you choose, using JENTIC_AGENT_API_KEY.
---

# Get your Agent API Key

!!! warning "Deprecated"
    This page is **deprecated** and kept only for reference. The hosted **Agent API Key**
    (`JENTIC_AGENT_API_KEY`) belonged to the retired `app.jentic.com` platform and the `jentic-sdks`
    library. With **self-hosted [Jentic One](../../reference/jentic-one/index.md)**, an agent instead
    registers its own identity (`jentic register`) and is granted access per operation by an operator —
    see the [Quickstart](../../getting-started/quickstart.md). Upstream API credentials are stored
    encrypted in your Broker and injected at execution time.

Your **Agent API Key** authenticates SDK and MCP requests and scopes access to only the APIs/workflows you choose. Generate it in the Jentic app, then use it from code or an MCP client.

> **Required for SDK & MCP.** The environment variable is now **`JENTIC_AGENT_API_KEY`** (not `JENTIC_UUID`).

## Why You Need an Agent Key

* **Python SDK** – authenticate `search → load → execute`
* **MCP Plugin** – expose the same capabilities to Claude Desktop, Windsurf, Cursor, etc.

Each request is authorized and **scoped** to the APIs you enabled for that agent.

---

## Quick Start (2 minutes)

### 1) Create account & add credentials

1. Go to **[https://jentic.com/register](https://jentic.com/register)** and sign up.
2. In **Credentials**, add any API secrets you’ll use (e.g., Discord bot token, NYT key).

### 2) Create an Agent & generate a key

1. Open **Agents → New Agent**.
2. Select the APIs/workflows this agent can access.
3. Click **Generate API Key** and copy it.

   * Keys are shown **once**. Treat like a password.

### 3) Set the environment variable

**macOS / Linux**

```bash
export JENTIC_AGENT_API_KEY="<your-agent-api-key>"
```

**Windows (PowerShell)**

```powershell
setx JENTIC_AGENT_API_KEY "<your-agent-api-key>"
$env:JENTIC_AGENT_API_KEY = "<your-agent-api-key>"  # current session
```

---

## Using the Key

| Context             | How to provide the key                                                         |
| ------------------- | ------------------------------------------------------------------------------ |
| **Python SDK**      | Environment variable `JENTIC_AGENT_API_KEY`                                    |
| **MCP clients**     | Add `JENTIC_AGENT_API_KEY` under `mcpServers.jentic.env` in your client config |
| **Raw HTTP / REST** | `Authorization: Bearer <your-agent-api-key>`                                   |

### Example: Claude Desktop MCP config

```json
{
  "mcpServers": {
    "jentic": {
      "command": "uvx",
      "args": [
        "--from",
        "git+https://github.com/jentic/jentic-sdks.git@main#subdirectory=mcp",
        "mcp"
      ],
      "env": {
        "JENTIC_AGENT_API_KEY": "<your-agent-api-key>"
      }
    }
  }
}
```

> After saving, restart your MCP client.

---

## Key Management Best Practices

* **Scope by design:** Create separate agents (and keys) per bot/app (“content-bot”, “ops-bot”, …).
* **Rotate regularly:** Re-generate keys in **Agents** and update your environment/CI.
* **Never commit keys:** Store in a secrets manager (GitHub Actions, 1Password, AWS Secrets Manager, etc.).
* **Revoke on leak:** Delete the key from **Agents** and issue a new one.

---

## Troubleshooting

| Symptom                      | Likely cause                              | Fix                                                                                |
| ---------------------------- | ----------------------------------------- | ---------------------------------------------------------------------------------- |
| `401 Unauthorized`           | Missing/invalid env var                   | Verify `echo $JENTIC_AGENT_API_KEY` (or `$env:JENTIC_AGENT_API_KEY`) and re-export |
| “Operation requires auth”    | API creds not added for this agent        | Add the API credentials in **Credentials**, ensure the **Agent** includes that API |
| MCP can’t see tools          | Client not restarted or config path wrong | Restart the client; check you edited the correct MCP config file                   |
| Key works in SDK but not MCP | Env var only set in shell                 | Also add it under `mcpServers.jentic.env` in the MCP config                        |

---

## Migration Note (from `JENTIC_UUID`)

* **Deprecated:** `JENTIC_UUID`
* **Use instead:** `JENTIC_AGENT_API_KEY`
  Update SDK code, CI, and MCP configs to the new variable name. Keys must now be generated in **Agents** and are **scoped** to selected APIs/workflows.

---