Troubleshooting

Look at the error number; 401 means identity, 403 means permission, 429 means rate limit — and all three are fixed in the panel.

Where to find: Your app's error message + Settings → AI Access in the panel Who it's for: Anyone whose connection will not come up or who gets an unexpected error In short: Look at the error number; 401 means identity, 403 means permission, 429 means rate limit — and all three are fixed in the panel.

Quick table

What you see	What it means	What to do
401 / "invalid token" / "needs authentication"	The key was not accepted	The 401 section below
403 / "this key's scope cannot call …"	The key exists but is not allowed to do that	The 403 section below
429 / "too many requests"	Calls came in too fast	The 429 section below
It will not connect, the address is not found	Wrong address, or access is not open	The I cannot connect section
It connects but there are no tools	Packs are closed, or the list is stale	The A tool is missing section

401 · The key was not accepted

Treyza deliberately does not say which of the reasons applies (that is a security choice), so work down the list:

The key may have been copied incompletely. Keys are long; make sure the leading trz_mcp_ and the trailing characters are all there, with no space at either end.
The key may have been revoked. Check the Status column on its row in the panel: if it says Revoked, create a new key.
It may have expired. If the status is Expired, create a new key.
The IP allowlist may be blocking it. If you entered IP addresses when creating the key and your internet address has since changed, the key stops working. The fix: create a new key and leave the IP box empty.
The key may belong to another store. If you have more than one store, make sure you are using the right store's key.
The header format may be broken. The header must read exactly like this (including Bearer and the single space):
```
Authorization: Bearer trz_mcp_live_...
```
The person who created the key may have been removed from the store. In that case their keys are revoked automatically.

The fastest test: look at the View usage card in the panel. If your attempts show up there as Error, the key is reaching Treyza and the problem is the key's state. If there is no record at all, the request never reaches Treyza — check the address.

403 · Not enough permission

There are two different 403s:

"This key's scope cannot call the tool …"

The key is valid, but that tool sits outside the packs that are open.

Open Edit scope on the key's row in the panel and see which packs were granted.
If the pack you need is missing: a scope cannot be widened afterwards. Create a new key that includes the packs you need.
If the pack you need involves writing, the key must be in Read and write mode; the mode cannot be changed either, so a new key is required.

"The Origin header was not accepted."

The request is coming from a web page Treyza does not recognise. This usually happens with a browser extension or tool Treyza does not support. For the supported routes: AI Access (MCP)

429 · Too many calls

A key may make 60 calls a minute and 2,000 a day (write tools: 20 a minute).

If you saw it once: you need do nothing; the app retries shortly.
If you see it constantly: you may have given the AI a very large job in one go ("go through every product one by one"). Narrow the question: give a threshold, give a period, say how many results you want.
If you use the same key in several apps, give each app its own key; the limit is per key.

I cannot connect

Check the address. It must be exactly:
```
https://api.treyza.co/mcp
```
If the trailing /mcp is missing, no connection is made.
Check the file format. The configuration files for Cursor, VS Code and Gemini CLI are different from each other; pasting one app's block into another silently fails. The correct blocks: Cursor, VS Code and other apps
Check your plan. If the tab says "AI Access is not part of your plan", no connection can be made.
Can you even see the tab contents? If it says "Only the store owner can use this screen", ask the store owner for a key.
If the address is right, the plan is fine and the server still cannot be found, AI Access may not be switched on for your account yet — write to support.

A tool is missing

The connection is up but the AI says "I have no such tool":

Cause	Fix
The pack is not open on the key	Check with Edit scope; create a new key if needed
The key is in Read only mode and you want a write tool	A read-only key never sees write tools; you need a new read-and-write key
The tool is not released yet	The full list of released tools: Tool catalogue
You just narrowed the scope but the app shows the old list	Apps remember the tool list for a short while (about 5 minutes). Wait, or close and reopen the connection.

I lost my key

A key is shown only once and cannot be recovered. What to do:

Revoke the old key (so nobody is left holding it).
Create a new key: Creating a key
Replace the old key with the new one in your app.

Consent (OAuth) requests are short-lived. If the browser tab stayed open for a long time, the request lapses.

The fix: delete the connector in the app, add it again, and complete the consent screen straight away.

Claude Code's consent-screen (OAuth) route requires signing in from a real terminal; it cannot be driven from automation or a script. For Claude Code the shortest route is connecting with a key: Claude Code

The numbers differ from the panel

There are two possible reasons; work out which one first.

1. A difference of definition (the most common reason — not a fault). "Revenue" does not count the same thing on every screen:

Number	What it counts
The revenue the AI gives you	The order amount — it enters the total the moment the order is placed, even if payment has not been taken yet
The Net Revenue card on the dashboard	Collection-based — orders whose payment has completed

Both are correct; they are expected to differ. If you want to compare, compare against the order amounts on the order screen.

2. The tool's data source. Some report tools read from order records and some from visit events; if an event was not collected, the second group can fall below the real totals. Which tool belongs to which group is written in the "Where do the numbers come from?" section of the tool catalogue, and that table is generated from the tool registry, so it is always current: Tool catalogue

Use the order list for anything that must be exact. The order count and the order list should match the panel's order screen exactly — if they do not, let us know.

Still not solved?

When you open a support request, include these — they speed up the diagnosis a lot:

The app you use and its version (Claude Code, Cursor, ChatGPT…)
The key's mask as shown in the panel (never the whole key)
The full text of the error message and its number, if it has one
The time of the last call in the View usage card

On this page