I'm experiencing persistent "Not Authorized" errors when attempting to use the Railway public API with API tokens from my account.

Here's what I've done so far:

- I am the Workspace Owner of my account (profile: Ginger, email: denniesework@protonmail.com).

- I generated multiple API tokens from the "Tokens" section of my personal account settings (not from any team or project), making sure to copy each token immediately after creation.

- Each time, I tested the token with the documented GraphQL endpoint:

```

POST https://backboard.railway.com/graphql/v2

Authorization: Bearer <my_token>

{ "query": "query { me { name email } }" }

```

In every case, the response was: { "errors": [ { "message": "Not Authorized", ... } ], "data": null }

- I also injected these tokens into Docker containers and the MCP automation workflow; the result was always an "Invalid API token" or "Not Authorized" error in both logs and direct API use.

- My profile and permission state confirm I'm the workspace/project owner.

- I have already tried revoking, deleting, and re-creating new tokens, waiting several minutes before retrying, and ensured no whitespace or copy issues.

Per https://docs.railway.com/reference/public-api, these tokens should grant full access, but all API requests are failing authorization.

Can you please confirm if there is a known restriction or propagation issue with my account, or review why tokens are being rejected? I can provide example token IDs and full CLI output upon request.

Thank you for your help.