API Terms

01. Who can build with Syntic

These API Terms govern access to Syntic's developer platform and application programming interfaces by individuals and organizations ("Customer"). By activating API credentials or using the API, Customer agrees to these Terms and represents that the person accepting has authority to act for Customer. Syntic AI, Inc. ("Syntic") provides the API services. An executed order form, data processing agreement, or negotiated enterprise agreement may supplement these Terms and takes precedence where it expressly conflicts.

The API is designed for commercial and internal applications alike: software products, websites, community platforms, SaaS services, mobile applications, research environments, customer support experiences and other lawful integrations. Customer may make API-powered functionality available to its own end users.

02. API capabilities and documentation

Syntic provides developer access to its AI platform and proprietary model family, including Amara and Syntic models such as Syntic Code and Syntic Deep as made available through the relevant interfaces. Available capabilities, endpoints, model identifiers, parameters, supported regions, limits and versions are specified in the applicable API reference and developer console. A named capability is not a guarantee that every model or endpoint is available to every account or region.

The API reference is the source for technical integration requirements; these Terms govern legal and commercial rights. Technical documentation may evolve, but it does not silently override an executed order form or a binding data protection commitment.

03. License, embedded products and resale

During an active subscription or paid usage arrangement, Syntic grants Customer a limited, nonexclusive, nontransferable right to call authorized API endpoints and integrate their functionality into Customer applications, including products sold or offered to third-party end users. Customer may charge for its own application and its AI-powered features, subject to these Terms and any agreed commercial restrictions.

Embedding API capabilities in a Customer application is permitted. Selling or transferring raw API keys, misrepresenting an independent Syntic account as Customer's own infrastructure, or providing unauthorized access to Syntic's underlying developer console is not permitted. White-label, dedicated capacity and direct API redistribution arrangements may require separate written terms. Building a lawful competing application is not, by itself, prohibited.

04. Your end users and downstream responsibilities

Customer is responsible for its application's user experience, published terms and privacy notices, end-user consent, age-appropriate access, account administration, and lawful use of the API. Customer must ensure that its end users comply with relevant restrictions and that integrations do not expose credentials or confidential information. Syntic is responsible for the API services it provides, while Customer is responsible for its application and independent business decisions.

Where Customer makes AI-generated content available to the public, Customer should provide suitable transparency, reporting and correction mechanisms. Customer must not claim that Syntic has approved, certified or endorsed a Customer application unless Syntic has expressly done so.

05. Customer content, output and intellectual property

Customer retains the rights it holds in prompts, documents, code, audio, images, structured records and other data supplied through the API ("Inputs"). As between the parties, and to the extent legally transferable, Customer receives Syntic's rights, if any, in responses and generated materials ("Outputs"). Syntic retains ownership of its models, software, infrastructure, trademarks, documentation and other underlying technology.

Customer grants Syntic only the rights reasonably necessary to process Inputs, deliver Outputs, provide support when requested, maintain security and fulfill legal obligations. Customer warrants that it has sufficient rights and permissions for its Inputs. Outputs can be inaccurate, incomplete or similar to content produced for others; Customer must review them before consequential use.

06. Training and customer data protections

API Inputs and Outputs are not used to train general Syntic models by default. Syntic will use API customer content for general model training only if Customer affirmatively opts into an applicable data-sharing or improvement program or expressly agrees in writing. Consumer-account training defaults do not apply to API workloads.

Processing necessary to fulfill requests, operate and secure the API, prevent misuse, investigate incidents, provide requested support, or comply with law is distinct from general model training. Where personal data is processed on Customer's behalf, the applicable data processing agreement and documented processing instructions govern. Syntic does not promise zero retention, a fixed log lifetime or regional data residency unless an applicable binding agreement or published product commitment specifies it.

07. Privacy, security and subprocessors

Each party must comply with data protection laws applicable to its role. Customer is responsible for identifying a lawful basis for transmitting personal data, giving appropriate notices, honoring rights requests and ensuring that its application sends only information necessary for its purpose. Where Syntic acts as a processor, the parties should execute an appropriate data processing agreement before processing regulated personal information where required.

Customer must keep API credentials secret, use server-side key management where appropriate, rotate compromised keys, restrict scopes and implement reasonable controls against abuse. Syntic will maintain reasonable technical and organizational safeguards appropriate to the API. Specific audit, residency, incident notification, subprocessor or certification obligations require an applicable binding agreement.

08. Healthcare, finance and other regulated deployments

The API can support applications in healthcare, education, finance, insurance, government and other regulated sectors, but availability does not by itself establish compliance or authorization for a regulated workflow. Customer is responsible for evaluating its legal duties and obtaining any necessary approvals, consents and professional oversight.

Healthcare: Do not transmit Protected Health Information subject to HIPAA unless Syntic has expressly approved the intended use and the parties have executed a Business Associate Agreement where required. No general API subscription includes a BAA by default. Medical outputs require qualified human review; the API is not independently represented as a certified medical device or clinical decision system.

Other consequential decisions: Customer must not use unreviewed AI output as the sole basis for decisions materially affecting a person's health, safety, credit, housing, employment, education, insurance or legal rights. Additional safeguards or separate agreements may be required for financial, biometric, children's, government or other sensitive data.

09. Safety and prohibited conduct

Customer and its end users must not use the API to facilitate unlawful harm, fraud, exploitation of minors, malicious cyber activity, unauthorized surveillance, privacy violations, deceptive impersonation, or infringement of others' rights. They must not bypass authentication, circumvent usage or safety controls, interfere with service availability, extract protected model weights, or use stolen credentials.

These restrictions protect the service and people affected by it; they do not prohibit ordinary software development, security research conducted with authorization, interoperability, or lawful competition. Syntic may investigate credible violations and take proportionate action under Section 14.

10. Rates, quotas and reliable integrations

API use may be subject to request limits, token or media quotas, concurrency limits, throughput restrictions, model availability, fair-use rules and capacity controls shown in the developer console or documentation. Customer must implement reasonable retries, backoff, timeouts, error handling, credential protection and usage monitoring. Syntic may adjust limits to protect platform integrity or reflect purchased capacity; committed reserved capacity and service levels are governed by written agreements.

Customer should design for transient errors, version changes and provider-side maintenance. Syntic will endeavor to communicate material breaking changes and deprecations with reasonable advance notice when practicable. Any binding uptime, support response or deprecation notice period must be agreed separately.

11. Metering, billing and usage controls

API fees may be calculated from tokens, requests, compute time, audio duration, generated media, storage, reserved capacity or other meters identified in the applicable pricing schedule. The console or accepted order form determines rates, currency, payment timing, prepaid credits and any subscription components. Customer is responsible for usage generated by its authorized credentials, subject to applicable billing dispute rights and Syntic's obligations in cases of its own error.

Displayed usage information may be delayed or subject to reconciliation. Budgets, alerts and spending caps are effective only to the extent explicitly offered and configured; an alert is not necessarily a hard billing limit. Pricing changes are prospective and subject to notice and active order commitments. Taxes may apply. Prepaid credit expiration, refund eligibility and account closure treatment must follow the terms disclosed when purchased and applicable law; Syntic will not confiscate a balance merely as an automatic penalty for an alleged policy breach.

12. Confidentiality and permitted disclosures

Each party must protect the other's confidential business information using reasonable care and limit access to persons who need it and are subject to confidentiality duties. Confidentiality excludes information lawfully public, independently developed or obtained without restriction. Syntic will assess governmental requests for validity and appropriate scope and ordinarily disclose customer information only as required by applicable law or valid legal process.

Exceptional disclosures involving an imminent threat of death or serious physical injury may occur where legally permitted, with human review when feasible and information limited to what is reasonably necessary. Notification will be provided where legally permitted and appropriate. A model-generated flag alone does not automatically trigger reporting to authorities.

13. Service changes, warranties and limitations

Syntic will provide the API with reasonable care and in material accordance with its applicable documentation, subject to any express contractual service commitments. AI outputs are probabilistic and may contain errors; Syntic does not warrant that all results are accurate, unique or suitable for a particular regulated use. Customer must maintain backups of information important to its application and plan for interruptions.

To the extent permitted by law, neither party is liable for indirect or consequential damages, and each party's aggregate contractual liability under these Terms is limited to fees paid or payable for the affected API services during the twelve months preceding the claim. This cap does not limit liability that cannot legally be limited, fraud or willful misconduct. Any higher cap, indemnification arrangement or dedicated service warranty requires a separate written agreement.

14. Suspension, termination and transition

Syntic may temporarily restrict or suspend API access when reasonably necessary to address urgent security threats, material abuse, unlawful activity or nonpayment. Where practicable, Syntic will notify Customer, identify the reason and offer an opportunity to remedy it. Immediate action may be necessary to prevent serious harm. Customer may stop API use or close an account subject to existing charges, subscription commitments and lawful retention requirements.

On termination, access to credentials and API services ends, subject to any agreed export or transition rights. Data deletion and retention follow the applicable data processing agreement, published retention commitments and legal obligations. Syntic does not promise immediate erasure from every backup or automatic forfeiture of unused prepaid credits.

15. Disputes, agreements and notices

The parties will attempt to resolve disputes through good-faith business discussions before litigation where practicable. These standard API Terms do not impose mandatory arbitration or a one-year contractual deadline for all claims. Applicable law and any valid negotiated jurisdiction provision determine the forum. An executed order form or enterprise agreement takes precedence where it expressly conflicts with these Terms, followed by any applicable data processing agreement for data-processing matters, then these API Terms and incorporated policies.

Questions about commercial API access and enterprise arrangements may be directed to sales@syntic.ai. For privacy questions, use privacy@syntic.ai. For account support, consult the developer console or the published support channel.