DataNavoAPI / PRICING / WECHAT

WeChat Official Accounts local TEST pricing

WeChat Official Accounts local TEST pricing. Follow concrete contracts, examples and reviewable steps using WeChat Official Accounts.

LOCAL SIMULATIONAll displayed records are fictional fixtures. Live APIs, payments and external email are disabled.中文版 ↗
01

Local TEST accounting

This page covers local credit accounting and task planning without real payments. Anonymous demo is free. The rates below apply per successful customer TEST request, not per returned record.

02

Read two articles and their visible comments

List articles for an account, then choose two and request their details and comments. Lists, details and comments are distinct calls.

The account list uses id. Article details and comments use full mp.weixin.qq.com article URLs.

5 successful requests total 10 TEST; real charges are 0.

Only one comment page per article is included. Additional cursor pages need additional requests; supplier charges are not part of the TEST estimate.

  • Read one account article page with the account id.
  • Choose two full article URLs and request each detail.
  • Read one visible-comment page per article.
CapabilityRequestsTEST per requestTotal TEST
wechat_mp.accounts.articles.list122
wechat_mp.articles.get224
wechat_mp.articles.comments.list224
03

TEST rate by capability

CapabilityObjectTEST per successPagination
wechat_mp.accounts.articles.listPost2Each new page is a separate request
wechat_mp.accounts.getAccount1No cursor
wechat_mp.articles.comments.listComment2Each new page is a separate request
wechat_mp.articles.getPost2No cursor
wechat_mp.articles.metricsPost2No cursor
wechat_mp.comments.replies.listComment2No cursor
wechat_mp.accounts.searchAccount1No cursor
wechat_mp.accounts.owner.getAccount owner1No cursor
04

Adjust the task estimate

The calculator below uses the shared TEST rates. Choose capabilities and successful request counts. It runs only in the browser, executes no request, reserves no balance and needs no key.

05

Budgets, quotes and settlement

Check account balance, shared Key daily/monthly/lifetime TEST budgets, Key daily counts and the per-call price cap separately. Settled credits and pending reservations consume the shared budget; rotating a Key does not reset spending.

A read-only quote checks input, scope, balance and budget without execution or reservation. Set X-Guanliu-Max-Credits to cap the TEST price of a new call; a higher quote is rejected before execution. A quote is a snapshot and does not guarantee future balance.

Each newly successful page is metered separately. Replaying a completed idempotent request does not debit again. Simulated failure or timeout releases reservations. Fictional provider costs use a separate test unit and are not real profit calculations.

PLAN BEFORE YOU CALL

Plan this task before calling.

Estimate local TEST credits per successful request. Calculated in this browser without a key.

test-credit-v1
2 TEST / requestContract ↗
2 TEST / requestContract ↗
2 TEST / requestContract ↗
1 TEST / requestContract ↗
1 TEST / requestContract ↗
1 TEST / requestContract ↗
2 TEST / requestContract ↗
2 TEST / requestContract ↗

This estimate reserves no balance. New successful pages are metered separately; failure, timeout and completed-request replay add no charge. Execution still checks balance, scope, daily counts and Key budgets. Provider costs are separate; real charges remain 0.

Use a customer Key to inspect a call quote →
TRY THE CONTRACT

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 ↗