Error handling
Error handling. Follow concrete contracts, examples and reviewable steps using Douyin, Bilibili, Kuaishou, Telegram.
Copy the agent prompt manually
Error handling
Distinguish invalid inputs, authorization failures, budget rejection, execution failure and unknown outcomes.
Preserve request_id and the structured code rather than relying only on the message.
Discard stale private snapshots after 401/403; a fresh request ID is not a way around rejection.
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 ↗