Last updated: April 2026
These API Platform Terms ("Platform Terms") govern access to and use of the Amass API, developer platform, API documentation and related features made available by Amass at platform.amass.tech or such other URLs as Amass may designate (collectively, the "API Services"). These Platform Terms form part of, and are incorporated into, the Amass Terms of Service available at amass.tech/legal/terms-of-service (the "General Terms"). In the event of any direct conflict between these Platform Terms and the General Terms, these Platform Terms prevail solely with respect to the API Services. For Customers with an applicable Order Form, Subscription Agreement, Master Service Agreement or other Enterprise Agreement, that agreement may or may not prevail over both the General Terms and these Platform Terms to the extent of any direct conflict, depending on the specific agreement.
1. Definitions
"API Documentation" means the technical, operational and usage documentation made available by Amass for the API Services, as updated from time to time.
"API Key" means the credential(s), token(s) or other authentication mechanism issued by Amass to enable access to the API Services.
"API Request" means any request, query, call, prompt, filter, parameter set or other instruction submitted to the API Services.
"Output Data" means the responses, search results, summaries, classifications, entity resolutions, metadata, or other content returned by the API Services.
"Platform Account" means the account used by Customer to access the API Services and related dashboard functionality.
"Usage Telemetry" means technical and operational usage information relating to the API Services, including endpoints called, request timestamps, response codes, latency, error rates, request volumes and other service telemetry.
"Query Content" means the customer-supplied content submitted through API Requests, including prompts, search parameters, filters, identifiers, and other submitted text or structured inputs, to the extent such content constitutes Customer Data under the General Terms.
2. Account and API Key Management
2.1 Registration. Access to the API Services requires a Platform Account. A Platform Account may be linked to an existing Amass account or created as a standalone account, as determined by Amass.
2.2 API Keys. Customer may be issued one or more API Keys. API Keys are confidential credentials and must be protected using reasonable security measures.
2.3 Customer Responsibility. Customer is responsible for all acts and omissions occurring through its Platform Account, API Keys, systems, applications and personnel, including its employees, contractors and service providers acting on its behalf.
2.4 Security Requirements. Customer must not embed API Keys in client-side code, public repositories, or publicly exposed applications. Customer must promptly notify Amass at support@amass.tech of any actual or suspected compromise, misuse or unauthorized disclosure of API Keys.
2.5 Rotation and Revocation. Amass may rotate, suspend or revoke API Keys where reasonably necessary for security, abuse prevention, legal compliance, or platform integrity, including without prior notice where immediate action is reasonably required.
3. Permitted Use
3.1 Subject to these Platform Terms, the General Terms, the applicable plan, and any applicable Enterprise Agreement, Customer may use the API Services to build internal workflows, applications, integrations and services that consume Output Data.
3.2 Customer may integrate Output Data into its own products and services and may display, transform and process Output Data as permitted under Section 7 below.
3.3 Automated and programmatic access to the API Services is permitted within applicable rate limits, quotas and usage restrictions.
3.4 Customer must comply with all applicable laws and regulations in connection with its use of the API Services, including applicable sanctions, export controls, privacy and data protection laws.
3.5 Any feedback, suggestions or feature requests regarding the API Services constitute "Feedback" under the General Terms.
4. Rate Limits, Quotas and Fair Use
4.1 The API Services may be subject to rate limits, quotas, concurrency limits, credit limits, and other technical or commercial restrictions based on Customer's plan, as described in the API Documentation, Platform dashboard, applicable Order Form or Enterprise Agreement.
4.2 If Customer exceeds applicable limits, Amass may throttle requests, return error responses (including HTTP 429 or equivalent), temporarily reduce throughput, or suspend access.
4.3 Amass may adjust rate limits, quotas or fair use thresholds from time to time. Where such change materially reduces Customer's permitted usage under a paid plan, Amass will provide at least thirty (30) days' prior notice unless a shorter period is reasonably necessary for security, abuse prevention, legal compliance, or third-party source restrictions.
4.4 Access exceeding standard plan limits may be made available under a separate enterprise arrangement.
5. Billing and Payment
5.1 Usage-Based Pricing. API Services may be billed on a usage-based, metered, subscription or credit basis, as specified in the applicable plan, dashboard, API Documentation, Order Form or Enterprise Agreement.
5.2 Usage Measurement. Usage is measured by Amass using its internal systems and records. Such records will form the basis for billing absent manifest error.
5.3 Invoicing. Unless otherwise stated, usage-based charges are invoiced monthly in arrears. Subscription or minimum commitment fees may be invoiced in advance.
5.4 Usage Visibility. Where available, Customer may monitor API usage through the Platform dashboard. Dashboard data is provided for convenience and may be subject to delay.
5.5 Invoice Disputes. Any good-faith dispute regarding an invoice must be raised in writing within thirty (30) days after the invoice date, with reasonable detail. Customer must pay all undisputed amounts when due.
5.6 Credits and Free Tiers. Any free tier, promotional credits, trial credits or similar usage allowances are non-transferable, non-refundable, may expire as stated, and may be modified or discontinued by Amass.
5.7 Late Payment. If Customer fails to pay any undisputed amount when due, Amass may suspend API access upon at least fourteen (14) days' written notice, in addition to any other rights available under the General Terms.
5.8 Pricing Changes. Amass may change API pricing on at least thirty (30) days' prior notice. For recurring subscription elements, pricing changes apply from the next billing period unless otherwise stated.
6. Availability and Support
6.1 The API Services are provided on an "as available" basis unless otherwise expressly agreed in a separate SLA or Enterprise Agreement.
6.2 Amass aims to maintain commercially reasonable availability of the API Services, but does not provide any uptime commitment, service credit or guaranteed response time unless expressly agreed in writing.
6.3 Scheduled maintenance may occur from time to time. Where reasonably practicable, Amass will provide advance notice of planned maintenance affecting the API Services.
6.4 Support channels, hours and response expectations, if any, are determined by Customer's plan or Enterprise Agreement.
7. Output Data, Storage and Redistribution
7.1 Permitted Use of Output Data. Subject to these Platform Terms, the General Terms, and any applicable source restrictions, Customer may use, display, transform, process and incorporate Output Data into its internal workflows, analyses, applications and services.
7.2 Storage and Caching. Customer may store and cache Output Data as reasonably necessary for its permitted use of the API Services and for operation of its applications, products and internal systems. Customer must comply with any deletion, refresh, attribution or usage restrictions stated in the API Documentation, required by applicable law, or notified by Amass where reasonably necessary to reflect source corrections, source updates, third-party obligations, security concerns, or platform integrity needs.
7.3 Redistribution Restrictions. Customer may redistribute Output Data only as integrated into Customer's own products, services, workflows or analyses, and not as a standalone raw dataset, bulk export, database, API, data feed or substantially similar substitute for the API Services.
7.4 No Substitute Dataset. Customer must not systematically extract, index, harvest, accumulate or store Output Data at a scale or in a manner that creates a substitute for, or materially reproduces, the API Services or Amass's underlying datasets.
7.5 Attribution is not required unless stated in the API Documentation or required by applicable source-specific terms, notices, or disclaimers communicated by Amass.
7.6 Output Data may incorporate or be derived from public sources and other third-party sources. Customer is responsible for complying with any source-specific restrictions, notices, attribution requirements, copyright terms, or usage conditions communicated by Amass or otherwise applicable to Customer's use of such Output Data. Amass does not represent or warrant that Output Data is free of third-party rights or restrictions.
8. API Usage Data and Data Use
8.1 Usage Telemetry. Amass collects and uses Usage Telemetry for security, billing, abuse prevention, analytics, service monitoring, maintenance, support, reliability improvement and related operational purposes. Usage Telemetry is not Customer Data except to the extent it contains Customer Data as strictly necessary for such purposes.
8.2 Query Content and Output Data. As between the parties, Query Content constitutes Customer Data to the extent it contains customer-supplied content. Amass may process Query Content and Output Data to operate, support, analyse, improve and develop the API Services and related Services, including to improve search relevance, ranking, retrieval quality, classification, summarisation, and to train, fine-tune, evaluate and improve models, algorithms and system performance used in the Services, in each case to the extent permitted by applicable law.
8.3 Personal Data and Sensitive Data. Where Query Content or Output Data includes personal data, Amass will process such data in accordance with applicable data protection law, the Privacy Policy, and any applicable Data Processing Agreement. Amass may use such data in aggregated, de-identified, pseudonymised or anonymised form as appropriate for the relevant purpose. Unless otherwise expressly agreed in writing, Customer must not submit Sensitive Data through the API Services.
8.4 Optional Programs and Enterprise Overrides. Amass may offer optional programs, settings or enterprise arrangements under which Customer may elect, or the parties may agree, to restrict, expand or otherwise tailor Amass's rights to use specified Query Content, Output Data or Usage Telemetry for model improvement, benchmarking, feature development or related purposes.
8.5 Exclusions. Nothing in these Platform Terms gives Amass rights in Customer's proprietary application code, internal business logic, or end-user content beyond the rights expressly granted under the General Terms and these Platform Terms.
9. Additional Restrictions
In addition to the restrictions set out in the General Terms, Customer must not:
a) circumvent or attempt to circumvent rate limits, authentication controls, access controls or technical restrictions;
b) share, resell, sublicense or otherwise make API access available to third parties except as expressly permitted in writing;
c) use the API Services to create, provide or support a competing service, substitute database, standalone data feed or similar product;
d) use the API Services in a manner that violates applicable sanctions, export controls or trade restrictions;
e) misrepresent Output Data as originating from a source other than Amass where attribution is required by source terms or API Documentation;
f) attempt to manipulate, bypass or exploit model behaviour or system integrity through adversarial inputs, prompt injection, credential abuse or similar techniques; or
g) submit Sensitive Data through the API Services except as expressly permitted under the General Terms, any applicable DPA, and any applicable Enterprise Agreement.
10. Downstream Applications and End Users
If Customer incorporates the API Services or Output Data into its own products, applications or services for use by third parties, Customer is solely responsible for:
a) its downstream terms, notices and disclosures to its own users;
b) compliance with applicable laws and regulations in relation to its own product or service;
c) implementing appropriate authentication, monitoring, retry logic, timeout handling, fallback behaviour and other technical safeguards; and
d) any claims, representations or warranties made to its own users regarding availability, accuracy, freshness, provenance or suitability of Output Data.
11. Suspension and Termination
11.1 Amass may suspend or restrict access to the API Services immediately where reasonably necessary due to security threats, suspected credential compromise, abuse, legal obligation, non-payment, platform integrity issues, or material breach of these Platform Terms or the General Terms.
11.2 Unless otherwise agreed in an Enterprise Agreement, Amass may discontinue the API Services or terminate access to them on thirty (30) days' written notice for convenience.
11.3 Customer may stop using the API Services at any time. Termination does not relieve Customer of any accrued payment obligations.
11.4 Upon termination or expiry, API Keys may be revoked immediately and access to the API Services will cease. Customer may retain Output Data already incorporated into its products, services, workflows or records, subject to Section 7 and any applicable legal or source-based restrictions.
12. Changes to the API Services and Platform Terms
12.1 Amass may make additive changes to the API Services, including adding new endpoints, fields or features, without prior notice.
12.2 Amass will use commercially reasonable efforts to provide advance notice of material breaking changes, endpoint deprecations or version sunsets, typically as follows unless a shorter period is reasonably necessary for security, legal, operational or third-party source reasons:
- minor breaking changes: thirty (30) days;
- endpoint deprecations: thirty (30) days;
- major version sunset: thirty (30) days.
12.3 Beta or experimental endpoints and features may be modified, restricted or removed at any time without notice.
12.4 Amass may update these Platform Terms from time to time. Material changes will be notified by email, dashboard notice, documentation update or other reasonable means. Continued use of the API Services after the effective date constitutes acceptance of the updated Platform Terms.
13. Disclaimers and Liability
13.1 The API Services and Output Data are provided subject to the disclaimers and liability limitations in the General Terms.
13.2 Without limiting the foregoing:
a) the API Services are provided on a best-efforts basis unless otherwise expressly agreed in writing;
b) Amass is not liable for downstream impacts of API unavailability, latency, throttling, or errors on Customer's applications, services or end users;
c) Customer is responsible for implementing appropriate error handling, retry logic and fallback behaviour in its systems;
d) Output Data may include AI-generated content, including summaries, classifications or entity resolutions, and may contain inaccuracies; and
e) Customer is solely responsible for independently reviewing and validating Output Data before relying on it for any clinical, regulatory, legal, commercial or other consequential purpose.
14. Governing Law and Disputes
These Platform Terms are governed by the governing law and dispute resolution provisions set out in the General Terms, unless otherwise stated in an applicable Master Services or Enterprise Agreement.