Quickstart

You will mint a test key, call GET /v1/me, then list chatbots. Test keys share the same contract as live keys.

Why start with a test key

agy_test_ keys are rate-limited more tightly, on a budget separate from your live traffic, so a runaway script cannot starve production. They act on your real account and spend the same message credits, so keep experiments small. Use them in CI and local scripts until the integration is boring.

Create a test key

Sign in to the dashboard and open Developers → API keys.
Create a key. Copy the secret immediately — it is shown once.
Grant only the scopes you need. Leave high-risk scopes unticked unless you are the account owner and have confirmed them.

Call the API

GET/v1/me

Send the key as a Bearer token. There is no /api prefix on the Laravel host.

curl

curl -X GET https://api.agentency.com/v1/me \
  -H "Authorization: Bearer <YOUR_KEY>" \
  -H "Accept: application/json"

Common pitfalls

Putting /api in front of /v1 — the host is already api.{domain}.
Using a dashboard session cookie against /v1 — /v1 accepts API keys only.
Retrying POST /v1/chat without Idempotency-Key — that can double-charge.