1. Evaluation and ordering
Public pages describe available product categories and example interfaces. An engagement begins after both sides confirm the selected endpoints, sites, fields, capacity, billing scope, delivery method, support, and applicable documents.
2. Credentials and access
Project credentials are for the agreed project and should be protected against disclosure. Access scope, rotation, revocation, concurrency, and rate limits are project terms.
3. Acceptable use
Customers are responsible for their use of requested data, access inside their systems, and compliance obligations applicable to their use case and region. Do not use the service to interfere with the service, bypass agreed limits, expose credentials, or resell access outside the confirmed scope.
4. Data and output
Field coverage and freshness vary by endpoint, platform, region, and source conditions. Acceptance samples, required fields, empty results, partial results, and change handling should be documented before production use.
5. Fees and billing
The public pricing page explains an estimation path but does not publish a contract price. Unit, successful-call definition, exceptions, settlement, taxes, and invoice requirements are confirmed in the applicable order.
6. Service changes and support
Endpoint changes that affect a project should be communicated through the agreed channel. Support hours, severity, response targets, migration periods, and remedies apply only when documented.
7. Suspension and end of service
Triggers, notice, outstanding fees, credential revocation, export, deletion, and transition assistance are project terms.
8. Contact
Use the homepage inquiry form for procurement or terms questions and identify the relevant project and endpoint.