Aletheia

Aletheia Terms of Service

Account Registration

In order to access our API’s you may be required to provide certain information (such as identification or contact details) as part of the registration process for the APIs, or as part of your continued use of the APIs. Any registration information you give will always be accurate and up to date.

API Consumption & Use

You will comply with all applicable law, regulation, and third party rights (including without limitation laws regarding the import or export of data or software, privacy, and local laws). You will not use the APIs to encourage or promote illegal activity or violation of third party rights.

You will only access (or attempt to access) an API by the means described in the documentation of that API. If you are assigned developer credentials (e.g. API Keys), you must use them with the applicable APIs as stated in our documentation. You will not misrepresent or mask either your identity or your API Client's identity when using the APIs or developer accounts.

We set and enforce limits on your use of the APIs (e.g. limiting the number of API requests that you may make or the number of users you may serve), in our sole discretion. You agree to, and will not attempt to circumvent, such limitations documented with each API.

The Terms are non-exclusive. You acknowledge that we may develop products or services that may compete with the API Clients or any other products or services.

The APIs are designed to help you enhance your websites and applications. you agree that we may monitor use of the API’s to ensure quality, improve our products and services, and verify your compliance with the terms.

We do not acquire ownership in your API Clients, and by using our APIs, you do not acquire ownership of any rights in our APIs or the content that is accessed through our APIs.

Confidentiality

Developer credentials (such as your account password and associated API key) are intended to be used by you and identify your API Client. You will keep your credentials confidential and make reasonable efforts to prevent and discourage other API Clients from using your credentials. Developer credentials may not be embedded in open-source projects.

Content

We do our best to ensure that the data we release is complete, accurate and useful. However, due to this data be sourced externally and the complex nature of our data processing techniques, we cannot be liable for omissions or inaccuracies.

Our API’s serve content that is sourced externally. As such, we do not have control of inaccuracies or misstatements, both material and immaterial in nature. Our API content is supplied as is, and we do not take responsibility for any inaccuracies or the damages/implications caused by these inaccuracies.

In no event shall we be liable for costs of procurement of substitute goods or services, lost profits, lost sales or business expenditures, investments, or commitments in connection with any business, loss of any goodwill, or for any direct, indirect, special, incidental, exemplary, or consequential damages arising out of this agreement or use of the data and any related materials, however caused, on any theory of liability, and whether or not we have been advised of the possibility of such damage. These limitations shall apply notwithstanding any failure of essential purpose of any exclusive remedy.