SUPPORT / KEEP THE CONTEXT

Every issue,
with context.

Start with a request, a task or an order.
Find the cause and keep the resolution in view.

LOCAL SUPPORT DESK

Tickets and replies stay in your local account for manual review. No external email or real charges.

View runtime status ↗
01 / SELF SERVICE

Check the API contract

Confirm the capability, required parameters, response fields and pagination.

Developer docs↗
02 / SELF SERVICE

Find the original task

Inspect saved plans and receipts. Continue manually with the original key and request ID.

Saved tasks↗
03 / SELF SERVICE

Trace execution and settlement

Review success, failure, reservations and TEST entries. Distinguish original charges from replayed receipts.

Execution history↗
START WITH THE EVIDENCE

Understand the current state.
Choose the next step.

Keep the original request ID when a result is uncertain.
Use existing receipts and the TEST ledger as evidence.

The request result is unknown. Should I send it again?

Keep the original parameters, simulation scenario and idempotency ID. Inspect the task and execution history, then reconcile with the original ID if needed. A different ID can create a new logical request. The page never retries automatically.

Inspect saved tasks ↗
Why is a request blocked when I still have TEST credit?

A key also has capability permissions, an expiry date, daily request limits, daily/monthly/total budgets and a maximum price per request. Check the current step quote and the specific blocking reason. A quote does not reserve credit or execute an API.

Inspect keys and budgets ↗
Does a successful simulated order charge real money?

No. The local checkout changes the TEST ledger only. No card, WeChat Pay or Alipay collection is connected. Provider credit and customer TEST credit are separate; a simulated payment never enables real APIs.

View TEST billing ↗
Can I continue an old task after rotating its key?

Historical plans and receipts remain available. A task keeps the original key identity, so a new key cannot replace it to continue execution. If the old key is revoked or expired, reconcile the historical result before explicitly creating a new task.

Review task history ↗
What should I include in a ticket?

Describe the step, expected result and actual result. You can link an order, execution or saved task belonging to your account. Do not paste API keys, passwords or verification codes. Linking a record does not execute requests or adjust balances.

Create a local ticket ↗
Will replies arrive by email?

Replies stay in the local ticket and are handled by a local operator. Return to the ticket to check them manually. External email, automated support and service response commitments are not enabled.

View my tickets ↗
A CONVERSATION WITH CONTEXT

Share the context.
Keep the conversation moving.

Describe the step, expected result and actual result. Link your records so both sides can work from the same context.

Create a local ticket ↗