Explore WeaveBit and Integrate Its API with AI

Ask an AI assistant to use official WeaveBit resources to compare checks, choose an entry point and plan a budget. When you are ready to integrate, it can also provide API integration steps and example code for your programming language and runtime environment. Start with clear requirements and a small trial. Reading resources and generating code do not automatically create checks or incur detection charges.

What WeaveBit helps you answer

WeaveBit helps website operators, operations teams and service providers understand domain accessibility from mainland China. Use it for launch checks, access troubleshooting, multi-domain checks and ongoing monitoring.

Results describe a particular method, network and time, not guaranteed availability everywhere at all times. They do not replace full browser, application-function or origin diagnostics. A single abnormal result cannot establish who caused a failure.

Start with DNS Pollution or choose GFW Full

DNS Pollution is usually the first step when investigating access from China. Enter a domain without selecting nodes. Successful ordinary DNS resolution does not establish the absence of DNS pollution.

Choose GFW Full for a broader, convenient batch assessment. It combines DNS Pollution, HTTP Host and TLS SNI, with nodes chosen for your customers' regions and carriers. “Full” does not mean all seven check methods or a complete browser test. See check capabilities.

Choose the free webpage, Console or API

The free webpage is not an automation API. A Console task supports up to 200 domains; an API v2 batch supports up to 1,000 targets.

Prices and billing units

Console and API share an account balance but have separate unit prices. The prices below are in US dollars:

DNS Pollution has no separate node multiplier; GFW Full includes it. Charges follow valid results. Refer to pricing, the cost estimate and actual billing for the applicable cost.

Plan a detection budget

For example, checking 10 domains once an hour means 24 rounds a day. The daily DNS Pollution budget is “10 × 24 × the DNS unit price for your channel.” GFW Full with three nodes is “10 × 3 × 24 × the GFW unit price for your channel.” Multiply by your planned number of days to estimate monthly usage.

Start with relevant customer networks and the frequency you need rather than every available node. Plan with the cost calculator. Before API creation, call /task/estimate with the intended parameters, estimate again when targets or nodes change, and set your own budget limit.

Start with trial credit

Every new user automatically receives US$0.20 in detection trial credit after registration, without contacting support. Tell support about your detection requirements to receive US$3 in additional trial credit. The two offers are separate and can both be received.

Sign in to Console to view your balance. Try a small set of targets before choosing your scope and frequency. Trial credit is for trying checks, not unlimited free usage. See pricing and trial details for how to request it.

Understand normal, abnormal and indeterminate

A scenario assessment of 0 means the corresponding abnormality was not reported in this observation; 1 means an explicit abnormality was reported; null means indeterminate. Indeterminate does not establish a normal or blocked outcome, or prove recovery. Review the network, time and repeated observations.

API state completed only means execution ended, not that the target is normal. Do not turn one observation into a claim of unavailability on every network in China. See result interpretation.

Use AI for product assessment and API integration

When choosing a service, share your target count, customer regions, desired frequency, budget, and whether you need platform alerts or integration with your own system. Ask your assistant to compare options using the official documentation index and this guide. To integrate, also specify your programming language, version and runtime environment so it can read the API documentation and SDK examples and provide suitable steps and code.

1. Choose an integration: distinguish API v1 synchronous single-domain DNS Pollution checks from API v2 asynchronous batches, then choose a suitable SDK or HTTP request approach. Do not mix the parameter formats.
2. Prepare authentication and estimates: use placeholders such as YOUR_API_KEY or the server environment variable WEAVEBIT_API_KEY in examples. Prepare method-specific targets and nodes; omit nodes for DNS Pollution. Estimate API v2 costs with the intended parameters before creation.
3. Handle creation and results: persist the original API v2 request and idempotency key, then save the accepted batch_id. Query progress and read every result page. Separate HTTP errors, API errors and detection outcomes, and follow the documentation for timeouts, bounded retries and Retry-After.

You do not need to provide a real API key to read the resources or obtain code. Do not paste secrets into chats or public prompts. Examples should clearly identify creation steps that may incur charges. Before actual execution, confirm target authorization, scope, frequency and budget and obtain explicit authorization. The copy buttons do not sign in to an account or execute paid checks on your behalf.

API v2 batches execute for at most six hours; results are removed 24 hours after creation, so save them promptly. Refer to the official documentation for parameters, error codes, runtime requirements and SDK methods.

More resources for AI-assisted reading: documentation overview · result interpretation · API documentation · SDK examples.