Authentication and keys
Authentication and keys. Follow concrete contracts, examples and reviewable steps using Douyin, Bilibili, Kuaishou, Telegram.
Copy the agent prompt manually
Authentication and keys
Send customer keys in Authorization: Bearer, never in URLs, browser source or screenshots.
A new key is displayed in full only once. Rotation or revocation invalidates its gateway and read-only access.
Capability scopes, daily success counts and daily/monthly/lifetime TEST budgets are separate controls; rotation retains shared budget consumption.
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 ↗