TRAI Request Limits Explained: 20, 50, 100 or 200

How many TRAI requests do you get a month?

Trainers get 20 TRAI requests a month on Starter, 50 on Pro, 100 on Business and 200 on Enterprise; the Free plan has no TRAI. Solo clients get 40 on Client Pro and 90 on Client Premium, and every gym plan includes 200. One request is one message you send, and these are the October 2026 plan defaults.

The number alone says little. What matters is what one request can do, what does not cost a request at all, and where TRAI sits next to the separate AI plan generators.

TRAI allowance by plan

The monthly allowance sits next to separate quotas for the AI plan generators (the Generate buttons in the app).

Prices are the US-dollar list; prices differ by country on trainera.fit/pricing. Trainera can change features for an individual account, so a specific account can differ from this table.

Client TRAI is only for solo clients: no trainer and no gym membership. A client coached by a trainer, or a gym member, does not see the TRAI launcher. The sibling post on Client Pro vs Premium covers that side in detail.

What counts as one request

Every message you send to TRAI is one request, reserved the moment you send it.

It does not matter whether the message is a quick question or a job that reads five clients and saves a plan. "Where do I change my timezone?" costs one request. "Build Marko a 4-week plan and assign it" also costs one request.

The count runs per calendar month. A new month starts the counter from zero, and the chat header shows where you are, as used and limit, for example "12/50 requests this month".

Most AI services price by tokens, the pieces of words a model reads and writes; the Hugging Face tokenizer documentation explains how text is split into them. TRAI hides that from you. A long message with an attached document and a one-word question count the same: one request.

What does not cost a request

Three things are free: confirm-card clicks, failed runs and the plan generator quota inside the chat.

The confirm-card rule matters more than it looks. TRAI asks before it changes data for trainers and gyms: assigning a plan, sending a message, scheduling a session. If every Yes cost a request, safety would eat the allowance. It does not.

The plan-build rule is the other half. A Starter trainer has 10 AI training plans on the Generate button and 20 TRAI requests. A plan TRAI builds in the chat uses one of the 20 and leaves the 10 untouched.

How much one request can do

For trainers and gyms one request can run up to 10 agent steps and 20 tool calls; building a plan takes up to half a minute.

A tool call is one action on your account: reading a client's profile, looking up exercises, saving a plan, creating a session. Twenty of them fit a lot of work into one message, as long as the message carries everything TRAI needs.

Example prompt (one request): "Build Ana a 3-day full-body plan, beginner, home with dumbbells only, bad left knee, 45 minutes, warm-up first and stretching at the end, then assign it to her."

That one message gives the goal, level, equipment, injury, length and order. TRAI reads Ana's profile, builds the plan with the plan engine from the exercise library, and shows a confirm card before it replaces her active plan. The click is free.

Example prompt (one request): "Which of my clients haven't logged a workout this week? Draft a short check-in message for each."

Compare that with three separate messages ("show my clients", "who didn't train", "write a message"): same result, three requests.

What 20, 50, 100 or 200 requests a month look like

Divided across a month of about 4.3 weeks, Starter gives roughly 5 requests a week, Pro about 12, Business about 23 and Enterprise about 46.

Set against the client limits of each trainer plan, the arithmetic looks like this. These are divisions, not usage data:

• Starter, up to 10 clients, 20 requests: about 2 requests per client per month at full roster. Enough for a new plan and one adjustment each.
• Pro, up to 30 clients, 50 requests: under 2 per client. Works well if you batch: one message for several clients' check-ins.
• Business, up to 75 clients, 100 requests: about 1.3 per client. Here the Generate buttons (40 training and 40 nutrition plans) carry much of the plan building, and TRAI does the questions and edits.
• Enterprise, unlimited clients, 200 requests: plus unlimited generator plans, so TRAI can stay the place for analysis, messaging and automations.

One easy leak: short replies such as "thanks" or "ok" are messages too, and each one counts as a request.

Solo clients: 40 vs 90 requests

Client Pro has 40 requests a month and Client Premium 90; both can build and save training and nutrition plans in the chat.

The AI food photo scan (Premium, up to 20 scans a day) and the AI nutrition chat meal logger are separate features with their own limits. They are not TRAI and do not use TRAI requests. A Premium client who scans lunch every day still has all 90 requests for coaching questions and plan changes.

Gyms: 200 requests on every plan

Every gym plan includes 200 TRAI requests a month, including the free trial; a locked gym (trial over, not paying) gets none.

The owner's 200 is shared. When gym staff use "Ask AI" inside Automations, their messages count against the owner's allowance, and the same goes for the owner's own Automations AI messages: it is one monthly pool. In-app gym TRAI reads data (members, leads, classes, transactions) and works on automations, so a typical request is a question, not a plan build. The sibling post on questions gym owners ask TRAI has examples.

How to make your requests go further

Write fewer, fuller messages and let the free parts stay free.

1. Put the whole job in one message. Client, goal, days, equipment, injuries, order, and whether to assign.
2. Click the confirm card instead of typing "yes". The click continues the paid message; a typed reply is a new message.
3. Import instead of retyping. Attach a .docx or text plan and TRAI transcribes it in one request. PDF is not read, so convert it to .docx first. See importing a Word plan.
4. Use the Generate buttons for routine plans when you have generator quota left, and keep TRAI for the jobs that need conversation.
5. Retry failures without worry. A failed or empty run is refunded.
6. Start a new chat for a new topic. Each turn sees the newest 40 messages; a focused chat needs fewer corrections. You can keep up to 5 saved chats.

Requests vs connecting Claude or ChatGPT

Paid trainer plans and every gym plan can also connect an external AI app such as Claude or ChatGPT through the Model Context Protocol (MCP).

That route is metered differently: a plan built through MCP spends a generator slot, like the Generate button, and the conversation runs on the external app. In-app TRAI is metered on its own message allowance. The decision guide in-app TRAI vs Claude or ChatGPT via MCP compares the two, and the setup guide shows how to connect.

Picking the plan that fits how you use TRAI

Count the messages you would actually send in a normal week, multiply by about 4.3, and compare with 20, 50, 100 or 200.

If most of your AI use is building standard plans, the generator quota matters as much as the TRAI number. If you mostly ask questions, edit plans and message clients, the TRAI number is the one to watch. For a broader view of what each plan includes, see how an AI assistant builds client plans and the fitness software pricing index.

Compare plans, TRAI allowances and prices for your country on the Trainera pricing page.