Rate and concurrency limits
Rate and concurrency limits. Follow concrete contracts, examples and reviewable steps using Douyin, Bilibili, Kuaishou, Telegram.
Copy the agent prompt manually
Rate and concurrency limits
Limits may apply to a key, budget group, account or concurrent execution; their remaining values are not interchangeable.
Inspect the response and account snapshot before reducing the batch; the system does not retry indefinitely.
Use bounded tasks, explicit pagination and saved receipts to reconcile concurrent outcomes.
Local exercise boundaries
This is a local simulation. Program-generated samples are not live platform data and do not establish provider availability.
TEST credits are not money. Use an isolated account to verify success, failure, timeout, replay and key revocation.
Clear inputs. Inspectable output.
Each click runs a local fixture. Advanced JSON inputs are checked against the selected method. Editing does not execute a request.
Copying does not execute. CLI quote is read-only and needs a local customer TEST key. Configure MCP in demo mode first. GET and POST batches both return only fictional local fixtures.
Download contract example (no execution) ↗For TEST budgets, Key scopes or failure scenarios, open the account console. Customer sandbox ↗