Limits and credits
Size, time and rate limits for Archee MCP, and how a call is charged.
Limits
| Limit | Value |
|---|---|
| Program size | 50 KB |
| Time per program | 1–120 s (default 30 s) |
| Output | 20,000 characters of stdout, 12,000 of result; the head and tail are kept |
| Requests | 60 per minute per user, 30 per minute per token |
| Programs at once | 2 per user |
| Upload | 25 MB per file |
| Files read | 200 MB per file |
When you hit a rate or concurrency limit, the error says how many seconds to wait.
How a call is charged
Everything is metered in the same credits as the web app: sandbox time per second, Knowledge Base calls, TCVN checks and deliverable packages. search is free.
- Reserve. Before the program starts, Archee reserves credits for its full time limit plus an allowance for the SDK calls it may make.
- Run. If the program spends its allowance, the next paid call raises
BudgetExceeded, which the program can catch. - Settle. You pay what the program used; the rest of the reservation is released. The result’s
creditsfield shows the amount.
If your balance cannot cover the reservation, nothing runs and the error says how much is needed. A lower timeout_s means a smaller reservation.
A call is charged once. If a client retries a call that was already charged, the retry is refused instead of charged again.
Rates
The current rates are on the Billing page in the web app, with your usage per day, item and token. Rates are set by the Archee team and can change without a client update.