Is DataXAPI's data reliable, and what if a call fails? (2026)
Platforms change without notice, so any endpoint can slow down or stop for a while, and we do not promise otherwise. What you can check and control: a failed call is not charged, the status page is public, each key can carry a spending limit, and X-Max-Price caps what one call may cost. DataXAPI reads Xiaohongshu (RedNote) with 21 endpoints, from $0.0200 a call; a failed call is not charged.
Updated 2026-11-04
What you can check and control
Each of these can be tried on the free credit before you top up.
| What | How it works |
|---|---|
| A failed call is not charged | An error on our side or the platform's, or a timeout, costs nothing. An error's charged says whether it cost anything, and a good answer's meta.billing says how much. |
| The status page | Public, and it needs no key. Over MCP, the account tool's status tells an agent the same |
| A limit on each key | By day, by month or in total, in US dollars, with an expiry date and a list of endpoints it may call. A call the limit does not cover is refused before it runs |
X-Max-Price | The most one call may cost, as a request header; max_price over MCP. A call that could cost more is refused before it runs |
Idempotency-Key | Send the same key with the same request within 24 hours and it is the same call, not charged twice |
What we do not promise
There is no uptime agreement and no automatic compensation for an outage, and no promise of particular result counts or rankings. If your system cannot stand an endpoint being away for a while, build for that: keep what you have read, and retry later. If you must have an agreement, this is not the service for you.
Endpoints
Each with its price; every page has the parameters, the fields and a recorded response.