Phase Intelligence

API Terms

Effective date: June 1, 2026

These API Terms govern access to hosted APIs, private previews, closed-source services, model endpoints, workflow services, and related infrastructure provided by Phase Intelligence. They supplement our Terms of Use.

Operator

Phase Intelligence is currently an unincorporated research initiative operated by its founding team. These API Terms apply to API services provided under that initiative while it remains unincorporated, and may later be updated if a successor legal entity is formed to operate the services.

Access and API Keys

API access may require approval, registration, authentication, or an API key. You are responsible for keeping credentials secure and for all activity under your account or keys. Do not share, publish, sell, or transfer API keys without our written permission.

If you believe a key has been exposed or misused, revoke it if possible and contact us promptly.

Rate Limits and Fair Use

We may apply rate limits, usage quotas, concurrency limits, file-size limits, timeout limits, or other controls to protect reliability and shared infrastructure. You may not bypass or attempt to evade those limits.

Permitted Use

Unless we agree otherwise in writing, API access is provided for research, evaluation, development, and non-production experimentation. Production, commercial, safety-critical, regulated, or high-volume use may require a separate agreement.

Prohibited Use

You may not:

• resell, sublicense, broker, or provide the API as a competing service;
• scrape, harvest, or bulk extract data beyond documented API behavior;
• attack, overload, probe, scan, or disrupt API infrastructure;
• reverse engineer non-public systems or bypass access controls;
• submit malware, harmful code, or intentionally abusive requests;
• use the API to violate law, regulation, export controls, or rights;
• remove attribution, usage notices, or technical restrictions.

Inputs and Outputs

You are responsible for API inputs you submit and for how you use API outputs. Inputs and outputs may include prompts, scientific workflows, simulation descriptions, uploaded files, configuration files, logs, generated code, generated scripts, results, and model responses.

You should independently validate all outputs before relying on them. API outputs may be wrong, incomplete, unsafe, unstable, or unsuitable for a specific scientific, engineering, regulatory, or safety context.

Data Handling

We may process API inputs, outputs, metadata, logs, and error reports to provide the API, maintain security, debug failures, enforce limits, improve reliability, and understand system performance.

We do not sell your private API inputs or outputs. We do not use private API inputs or outputs to train public models unless you explicitly agree, the data is already public, or the data has been aggregated or de-identified so it no longer reasonably identifies you or your project.

Confidential and Sensitive Data

Do not submit confidential, proprietary, regulated, export-controlled, security-sensitive, or personally sensitive data unless we have a separate written agreement that permits it and defines the required protections.

Monitoring and Abuse Prevention

We may monitor API usage to operate the service, enforce these terms, investigate abuse, prevent security incidents, and protect shared infrastructure. We may throttle, block, suspend, or terminate access if we believe usage creates risk or violates these terms.

Availability and Changes

APIs may be experimental and may change without notice. We do not guarantee uptime, latency, compatibility, availability, accuracy, reproducibility, or continued access. We may modify endpoints, models, parameters, documentation, limits, pricing, or access requirements.

If the initiative later forms a company or other legal entity to run the API services, we may update these terms and transfer API operations to that successor operator with updated notice on this site.

Termination

We may suspend or terminate API access at any time, including for security risk, abuse, non-payment if applicable, legal compliance, discontinued infrastructure, or violation of these terms. You may stop using the API at any time.

Attribution and Publications

If you publish research, benchmarks, datasets, results, or tools that substantially rely on a Phase Intelligence API, we ask that you cite or acknowledge the relevant project where practical. Specific citation instructions may be provided in project documentation.

No Warranty

APIs are provided "as is" and "as available" without warranties of any kind. You are responsible for testing whether the API is appropriate for your use case and for validating results independently.

Liability, Indemnification, and Governing Law

Your use of the API is also subject to the limitation of liability, liability cap, indemnification, severability, and governing-law provisions of our Terms of Use, which are incorporated here by reference. If there is a conflict on these topics, the Terms of Use control.

Applicable Law

These API Terms apply only to the extent permitted by applicable law. Nothing here limits rights that cannot lawfully be limited or waived.

Contact

For API access questions, security concerns, or data handling requests, contact Phase Intelligence at contact@phaseintelligence.org.