Termos da API

These terms cover the Syncek Content API: the public, read-only endpoints described by openapi.json, which serve what syncek.com already publishes as web pages. They do not cover the Syncek product's own API, which is a feature of the CRM and is governed by the Terms of Service.

1. No key, no account, no charge#

Every endpoint is anonymous, unauthenticated and free. There is nothing to sign up for and nothing to agree to before calling one. Using it means accepting these terms and the Acceptable Use Policy.

2. Rate limits#

We enforce no rate limit on these endpoints today. We ask two things instead: identify your client in its User-Agent so we can tell a crawler from an incident, and do not degrade the Service for other people. If we ever need to enforce a limit we will publish the figure here and return it in RateLimit response headers before enforcing it, so a client can adapt without guessing.

3. What you may do with what it returns#

The answer differs by resource, and stating one licence for the whole API would be wrong in both directions:

• The CRM pricing dataset is published under CC BY 4.0. Quote it, chart it, check it. Attribute it to Syncek and link the source page.
• Everything else is our published site content: guides, posts, comparison pages and the summaries built from them. It is served in machine-readable form on purpose, and it may be crawled, indexed and used as robots.txt and its Content-Signal directive permit. That is not a relicence: normal copyright applies, quotation with attribution is welcome, and wholesale republication is not.

openapi.json deliberately carries no info.license for this reason. A single value there would license the whole corpus under the terms of one dataset.

4. No warranty and no service level#

These endpoints are provided "as is". They may be slow, wrong, or briefly unavailable, and nothing here carries an uptime commitment. The uptime commitments in the Terms of Service attach to paid Subscriptions to the CRM, not to this. Do not put a production dependency on an endpoint you have not cached.

5. Changes and deprecation#

The document is versioned by info.version, as semver, and there is no version segment in the paths. When an endpoint is deprecated we mark it with the standard Deprecation and Sunset response headers (RFC 9745 and RFC 8594) and a Link to its replacement, so a client can notice without reading this page. We may add, change or retire endpoints under that policy.

6. Liability and governing law#

To the maximum extent applicable law permits, Syncek's total aggregate liability arising out of or relating to these API Terms or the Content API will not exceed one hundred US dollars ($100), and Syncek will not be liable for indirect, incidental, special, consequential or punitive damages, or for lost profits, lost revenues or business interruption. These endpoints are free and anonymous; that figure is what a free, anonymous, read-only feed is worth, and it is the reason Section 4 asks you to cache rather than depend.

These API Terms are governed by the laws of the State of Wyoming, USA, without regard to conflict-of-laws rules, and its state and federal courts have exclusive jurisdiction, except that either party may seek injunctive relief in any court of competent jurisdiction. Nothing here deprives a consumer of the protection of mandatory law in their own country of residence.

7. Contact#

Questions, or a heads-up that you are about to fetch at volume: legal@syncek.com. Security issues go to security@syncek.com under our disclosure policy.