1. Endpoint-specific contracts
This Addendum applies to DataXAPI’s usage-priced public-data endpoints. Each page and versioned document specifies inputs, fields, limitations, billing unit, price and charging conditions. Review them before calling. Similar names, platforms or results do not make endpoints interchangeable.
Results are normalized data within the scope agreed for that call, not a guarantee of all platform content, unlimited history, zero latency or fixed search rankings. Interpret pagination, sampling, unavailable fields and missing source data under the corresponding endpoint description.
2. Results and charges
| Situation | Meaning |
|---|---|
| Complete | Successful output satisfying the endpoint contract, charged under its conditions; not necessarily all underlying platform data |
| Empty | No records within this response scope; charging follows the pre-execution description and emptiness is not automatically failure |
| Partial | Output affected by disclosed limits or the execution result state; identification and charging follow the endpoint contract |
| Failed execution | No service fee for that failed execution; reserved credit must be released or corrected according to accounting outcomes |
| Unconfirmed result or charge | Network/settlement conditions leave final status uncertain; check Usage and retry the original operation or contact support, rather than treating uncertainty as free or successful |
HTTP status, result completeness and charge status are distinct. Review Request ID, charge status and Usage rather than infer consumption solely from a page message or timeout.
3. Retries and stored results
Retry the same business operation with the same documented idempotency identifier and inputs. Replays within that scope are not charged twice. A new identifier or changed inputs may create a new execution; deliberately changing identifiers does not make independent executions one free call.
Stored normalized results are retained for replay for at most 24 hours. After expiry they may be unreadable, but historical charges are not automatically canceled. A newly created execution follows its then-current contract. Current rights and security restrictions also apply before replay, so content is not promised to remain replayable indefinitely. Store legitimately obtained results yourself where permitted; this service is not a long-term content archive.
For example, if a successful response is lost on the client, retry the original identifier to reconcile that operation. Creating a new request instead may produce two independently chargeable successful executions. When a result has expired, check its original charge before deciding whether to start another paid execution.
4. Availability and changes
Endpoints, objects and creators may be paused or restricted because of supply changes, faults or rights handling. Paused endpoints do not accept new paid executions. Endpoint/status pages or change notices describe known effects. Without a verified equivalent, we do not promise automatic replacement or recovery of missing data.
This initial release includes no separately contracted uptime SLA, automatic service compensation, continuous monitoring jobs, dataset delivery, platform write operations or underlying content licenses. Refunds, support and legally required responsibility remain governed by the relevant policies despite the absence of an SLA.
5. Support and evidence
Report the Request ID, endpoint/version, time, charge status and a minimal redacted reproduction. Do not attach plaintext keys or unnecessary complete personal information. We reconcile request, Usage and accounting evidence and address confirmed errors. Support will not require another payment to investigate the original call.
Support: support@dataxapi.com; privacy: privacy@dataxapi.com; content rights: rights@dataxapi.com.