In both plans

Your API and AI connector.
No tolls.

Your own tools and your own AI can read and change your gym's data the way your console does: as your gym, within what you allow. It comes with your plan, with no per-call fees, ever.

01

Make a key

In your console: Settings, then API keys (it takes Manage API keys on your staff level; All-Access has it). One key per tool, so you can see and stop each on its own.

  • A key belongs to your gym alone. It never reaches another gym’s data, whatever it sends.
  • It has a scope: the parts of RZNG it reaches, and read only or read and change.
  • It works at one of your staff levels, and never does more than the person who made it.
  • It’s shown once. Copy it then: RZNG keeps only a fingerprint. Rotate or revoke it any time.
  • Every change a key makes is in your gym’s log, under the key’s name.
02

Call it

Send the key as a header to https://api.rzng.app/api/trpc/<name>: GET to read, POST with a JSON body to change. api.reference lists every name your key can call, what each takes, and a sentence on what it does.

curl -H "Authorization: Bearer rzng_live_…" \
  https://api.rzng.app/api/trpc/api.reference
03

Connect your AI

Give your AI assistant RZNG’s connector (an MCP server) and a key, sent as a Bearer header. It sees what the key can call as tools, and works inside your gym only.

https://api.rzng.app/mcp
Authorization: Bearer rzng_live_…
  • Works today in any client that lets you set a header: Claude Code, the Claude API’s MCP connector, OpenAI’s MCP tool, and mcp-remote for desktop apps.
  • Adding RZNG by link inside the claude.ai or ChatGPT apps needs a sign-in step. Coming soon
  • A read-only key is a good start. A test key lets your AI try changes that are never kept.
04

Limits

  • Each key: 10 calls a second, with bursts up to 50.
  • All of your gym’s keys together: 20 calls a second, with bursts up to 100.
  • Past that, the answer is a 429 with a Retry-After header saying how many seconds to wait.
  • Never a per-call fee. The limits only keep every gym fast.
05

Test keys

A test key (rzng_test_…) runs every change with all its checks, then rolls it back: nothing is kept, and nobody gets a text. Reads are real, so your tools and your AI can try a change against your own gym first.

06

What a key can never do

  • Reach another gym, or anything of RZNG’s own.
  • Make API keys, or change staff levels.
  • Sign documents, or act as one person.
  • Do more than its staff level allows, or more than the person who made it could.

See your gym on RZNG first.

Build your appSee the plans