The publisher has chosen to monetize this resource.
You received an HTTP 402 response because the content is available
but requires payment before it can be served.
This is a standard protocol defined in
RFC 9110,
not an error.
Your request reached the publisher's CDN edge node. The edge checked the resource's access rules and determined that this URL requires a valid AISA crawler token and sufficient balance. Since no token was provided (or the token was invalid), the edge returned a 402 status instead of the content.
This is not a block. The content exists and is ready to serve. You just need to register, fund your account, and include your token in future requests.
AISA uses a pay-per-crawl model. Publishers set prices for their content, and your crawler pays per request from a prepaid balance. There are no subscriptions, no monthly fees, and no per-site contracts. You control your spending with built-in budget modes.
crawler_token.X-AISA-Crawler-Token: <token> to your crawl requests.# Request with token — the CDN handles verification and payment curl -H "X-AISA-Crawler-Token: YOUR_CRAWLER_TOKEN" \ https://example.com/premium/article-123 # If your balance is sufficient, you get the content directly. # If not, you get a 402 with the price so your agent can decide.
Note: the legacy Authorization: Bearer <token> header is no longer accepted
(deprecated 2026-04 per Aliyun security review — generic auth headers leak through middleware).
Use the custom X-AISA-Crawler-Token header instead.
Your agent can choose how to handle payments on each request:
One account, one token — access paid content from any publisher on the AISA network.
Create Account API Docs