Get started
Quickstart
Switch developer mode on, make a key, paste the prompt into your agent and make your first call, in five minutes.
Before you start
You need a Panlytics company account. Two things must be true before you can make a key:
- Developer mode is on for your company. Only the CEO can switch it on.
- Your role holds "Make keys for programs and AI agents". The CEO holds it already. Only the CEO can give it to another role, on the Roles page.
If you are the CEO, you can do every step below yourself.
1. Switch developer mode on
The CEO opens the organisation's settings (the Settings row in the rail, or the organisation switcher) and picks Developer under Your organisation (/settings/organisation/developer). In the panel called Developer mode:
- Switch Developer mode on.
- Choose How long a key works, from 1 to 5 hours. One hour is the default.
- Press Save.
Switching developer mode on asks for a recent sign-in. If you signed in a while ago, Panlytics asks you to confirm your password or passkey first.
2. Make a key
Open your own settings from the account menu and pick Developer (/settings/developer). The row only shows when your role holds the ability. In the panel called Make a key:
- Give the key a label you will recognise later, such as "Claude Code on my laptop".
- Press Make a key.
A dialog called Your new key opens. It shows two things:
- The agent prompt: everything an AI agent needs, with the key inside it.
- The key on its own: for a program or a script.
Making a key also asks for a recent sign-in, and you can hold at most five live keys at once.
3. Give it to your agent
If you use an AI agent, press Copy the prompt and paste the whole prompt into the agent's chat. The prompt tells the agent who it acts as, where to call, when the key ends and the rules it must follow. Connect an AI agent shows where it goes in each tool.
If you are writing a program, copy the key on its own and put it in an environment variable rather than in a file:
export PANLYTICS_KEY="pan_..."4. Make your first call
GET /v1/me answers with who the key acts as, which shops it reaches, what it may do and when it ends.
curl https://panlytics.net/api/v1/me \
-H "Authorization: Bearer $PANLYTICS_KEY"import os
import requests
answer = requests.get(
"https://panlytics.net/api/v1/me",
headers={"Authorization": f"Bearer {os.environ['PANLYTICS_KEY']}"},
timeout=30,
)
answer.raise_for_status()
print(answer.json())const answer = await fetch("https://panlytics.net/api/v1/me", {
headers: { Authorization: `Bearer ${process.env.PANLYTICS_KEY}` },
});
if (!answer.ok) throw new Error(`${answer.status}: ${(await answer.json()).code}`);
console.log(await answer.json());A 200 with your own name in user.name means the key works. A 401 means the key is wrong or has ended: make a new one. Every field of the answer is described on the GET /v1/me page.
What to read next
- Keys and rotation: when keys end and how to make a fresh one without stopping your work.
- Rate limits: 120 calls a minute per key.
- Errors: every code an answer can carry.