API Terms

For purposes of these API Terms:

“API” means an application programming interface, endpoint, protocol, or related interface provided by Asiyst.

“API Key” means an authentication credential issued by Asiyst for accessing applicable APIs.

“Application” means software, websites, services, scripts, integrations, or other systems that access or use an Asiyst API.

“API Documentation” means technical documentation, specifications, guides, or instructions published by Asiyst describing an API.

“API Data” means information transmitted to or returned from an API.

“Usage Limits” means applicable request limits, quotas, credit limits, rate limits, or other restrictions associated with an API.

You may use an Asiyst API only if you are authorized to access the applicable Service and have the necessary permissions.

If you are using an API on behalf of an organization, you represent that you have authority to bind that organization to the applicable terms.

You must not access an API using credentials or permissions that have not been authorized for you.

API access may require:

• An Asiyst account.
• An authorized project.
• An API key or other authentication mechanism.
• An applicable subscription, credit balance, or usage entitlement.
• Configuration of an approved application.
• Compliance with technical requirements.

Asiyst may require additional verification before granting or continuing API access.

API keys and other authentication credentials are used to identify and authorize API requests.

You are responsible for protecting your API credentials.

You must:

• Keep API keys confidential.
• Store credentials securely.
• Use appropriate secret-management practices.
• Restrict access to authorized personnel and systems.
• Rotate compromised credentials promptly.
• Revoke credentials that are no longer required.

You must not:

• Publish private API keys in public repositories.
• Embed private API keys in publicly distributed client-side code where they can be extracted.
• Share credentials with unauthorized persons.
• Sell or transfer credentials without authorization.
• Use credentials belonging to another user.
• Attempt to obtain credentials that do not belong to you.

If you believe an API key has been compromised, you should revoke it and generate a replacement as soon as reasonably possible.

You are responsible for implementing appropriate authentication and authorization controls in applications that use Asiyst APIs.

Possession of a valid API key does not authorize access to information or resources beyond the permissions associated with that credential.

You must not attempt to bypass authorization controls or access resources that your credentials do not permit you to access.

You must use APIs according to the applicable API Documentation.

Documentation may specify:

• Supported endpoints.
• Authentication requirements.
• Request formats.
• Response formats.
• Required parameters.
• Usage limits.
• Error handling.
• Version information.
• Supported features.
• Restrictions.

Asiyst may update API Documentation as APIs evolve.

Asiyst may apply technical limits to API usage.

These may include:

• Requests per second.
• Requests per minute.
• Requests per day.
• Account quotas.
• Project quotas.
• Credit limits.
• Token or usage limits.
• Concurrent-request limits.
• Other resource restrictions.

You must not attempt to circumvent these limits.

Circumvention may include:

• Creating multiple accounts for the purpose of avoiding limits.
• Rotating API keys to evade restrictions.
• Distributing requests across unauthorized projects.
• Using automated methods to bypass enforcement.
• Manipulating request identifiers or authentication mechanisms.

API requests should be generated at a reasonable rate and in a manner that does not interfere with the Services or other users.

You must not intentionally:

• Overload Asiyst infrastructure.
• Generate unnecessary traffic.
• Create request loops that consume excessive resources.
• Continuously retry failed requests without appropriate backoff.
• Attempt to degrade API performance.
• Interfere with another customer's application.

Applications should implement appropriate retry, timeout, error-handling, and backoff mechanisms.

You may not use Asiyst APIs to:

• Conduct unlawful activities.
• Facilitate fraud or scams.
• Conduct phishing.
• Distribute malware.
• Conduct unauthorized security attacks.
• Gain unauthorized access to systems or accounts.
• Circumvent security controls.
• Conduct denial-of-service attacks.
• Violate another person's privacy.
• Infringe intellectual-property rights.
• Circumvent Asiyst restrictions.
• Abuse third-party systems.
• Facilitate serious physical harm or exploitation.
• Conduct other activities prohibited by the Asiyst Acceptable Use Policy.

You are responsible for securing applications that use Asiyst APIs.

Appropriate controls may include:

• Secure credential storage.
• Authentication.
• Authorization.
• Input validation.
• Output handling.
• Rate limiting.
• Logging and monitoring.
• Error handling.
• Access controls.
• Credential rotation.
• Protection against injection and other application vulnerabilities.

Asiyst is not responsible for vulnerabilities in customer applications.

API requests may contain information submitted by you or your application.

You are responsible for ensuring that you have the necessary rights and authorization to transmit that information to Asiyst.

You must not knowingly transmit information that you are legally prohibited from processing through the applicable API.

If your API requests contain personal information, you are responsible for complying with applicable privacy and data-protection laws.

You should only process personal information through the API where you have an appropriate legal basis or authorization.

You are responsible for providing required notices and handling applicable data-subject rights.

Additional information about data processing is provided in the Asiyst Privacy Policy and applicable Data Processing Agreement.

Where an Asiyst API provides access to AI functionality, your use must also comply with the Asiyst AI Usage Policy and AI Data Processing & Training Policy.

AI-generated output may be inaccurate, incomplete, or unsuitable for a particular purpose.

You are responsible for reviewing and appropriately using AI-generated output.

Some Asiyst APIs may depend on third-party infrastructure, AI providers, payment providers, hosting providers, or other external services.

Third-party services may have separate terms, usage restrictions, availability requirements, and data-processing practices.

Where you use an integration involving a third-party provider, you are responsible for complying with applicable third-party requirements.

If you build an application using an Asiyst API, you are responsible for the application and its users.

You are responsible for:

• Your application's functionality.
• Your application's content.
• Your users.
• Your data-processing practices.
• Your security.
• Your authentication and authorization.
• Your third-party integrations.
• Your compliance with applicable laws.
• Your compliance with applicable API restrictions.

Your use of an Asiyst API does not transfer responsibility for your application to Asiyst.

API responses may contain information generated, retrieved, processed, or supplied by Asiyst systems or third-party services.

Unless expressly stated otherwise, API output is provided without a guarantee that it will be:

• Accurate.
• Complete.
• Current.
• Uninterrupted.
• Suitable for a particular purpose.
• Free from errors.

You are responsible for validating API output before using it in consequential applications.

If an API is used as part of an automated system, you are responsible for implementing appropriate safeguards.

Where API output contributes to decisions that may significantly affect individuals, appropriate human oversight, verification, and legal compliance may be required.

You should not rely solely on automated API output for consequential decisions without appropriate safeguards.

Asiyst may update APIs over time.

Changes may include:

• New endpoints.
• Modified endpoints.
• New parameters.
• Modified response formats.
• New authentication requirements.
• New usage limits.
• Deprecation of features.
• Removal of obsolete versions.
• Changes to supported models or providers.

Where reasonably practicable, Asiyst may provide notice of material changes or deprecations.

You are responsible for maintaining compatibility with the applicable API version.

Asiyst may discontinue an API or API version.

Where appropriate, Asiyst may provide a migration period or documentation describing an alternative API.

You should not depend on undocumented or deprecated API behavior.

You must not attempt to:

• Reverse engineer protected API authentication mechanisms.
• Extract private infrastructure information.
• Circumvent technical restrictions.
• Bypass authorization.
• Defeat rate limits.
• Discover or use undocumented access mechanisms for unauthorized purposes.
• Extract private credentials or secrets.

Nothing in this section is intended to prohibit rights that cannot lawfully be restricted under applicable law.

Asiyst may maintain technical logs relating to API requests for purposes including:

• Security.
• Abuse prevention.
• Reliability.
• Debugging.
• Usage measurement.
• Billing.
• Capacity planning.
• Service improvement.
• Legal compliance.

The handling of applicable personal information is described in the Asiyst Privacy Policy and other applicable policies.

Where API usage is subject to usage-based pricing, Asiyst may measure API activity for billing and account-management purposes.

Usage measurements may include information such as:

• Number of requests.
• Tokens processed.
• Input and output usage.
• Credits consumed.
• Applicable model or provider.
• Project or account associated with the request.
• Request timestamps.
• Other information required to calculate or verify usage.

The applicable pricing and billing terms are governed by the relevant Asiyst pricing, payment, or service agreement.

If you connect your own third-party API credentials to Asiyst, you are responsible for ensuring that:

• You are authorized to use the credentials.
• The credentials remain valid.
• The provider permits the intended use.
• The credentials are appropriately secured.
• The provider's applicable terms are followed.

You must not submit credentials belonging to another person or organization without authorization.

If you discover or reasonably suspect that an Asiyst API credential, application, or integration has been compromised, you should take appropriate steps to secure the affected system and notify Asiyst where the incident affects Asiyst Services.

Depending on the circumstances, this may include:

• Revoking compromised API keys.
• Rotating credentials.
• Restricting application access.
• Investigating unauthorized requests.
• Contacting Asiyst support or security personnel.

Asiyst may temporarily or permanently restrict API access where reasonably necessary to:

• Protect the Services.
• Protect other customers.
• Address security incidents.
• Prevent abuse.
• Enforce usage limits.
• Investigate suspected violations.
• Comply with legal obligations.
• Address unpaid or otherwise unresolved account obligations where applicable.

Where appropriate, Asiyst may attempt to provide notice before taking action, but immediate action may be taken when necessary to protect security or availability.

API access may end when:

• You close your account.
• Your applicable agreement ends.
• Your API access is terminated.
• Asiyst discontinues the applicable API.
• You violate applicable terms.
• Access is otherwise terminated under the applicable service agreement.

Following termination, you must stop using the applicable API and credentials.

Unless expressly authorized by Asiyst, you may not resell, sublicense, or provide standalone access to Asiyst APIs as a service that allows third parties to independently consume Asiyst API resources under your credentials.

You may build and operate applications using Asiyst APIs where such use is permitted by the applicable Service.

Asiyst and its licensors retain rights in the APIs, documentation, software, infrastructure, trademarks, and related materials except where applicable law or an express agreement provides otherwise.

These API Terms do not transfer ownership of Asiyst intellectual property to you.

If you provide suggestions, feedback, or recommendations concerning Asiyst APIs, Asiyst may use that feedback to improve its Services without creating an obligation to compensate you, subject to applicable law.

API availability may depend on infrastructure, networks, third-party services, maintenance, security events, and other factors.

Asiyst does not guarantee uninterrupted API availability unless an applicable service agreement expressly provides otherwise.

For questions regarding these API Terms or API access, contact:

Asiyst Website: https://asiyst.com Email: support@asiyst.com