API Terms

These API Terms govern programmatic access to BCINexus APIs — including endpoints used by BCILattice, integrations, and any documented developer interfaces. They supplement the Terms of Service and Acceptable Use Policy; if they conflict, these API Terms control for API access. Using the APIs means you accept these terms.

API access requires a valid account and, where issued, API credentials or tokens. Credentials are personal to your account or organization: - Keep tokens secret. Don't commit them to repositories, embed them in client-side code, or share them between organizations - You are responsible for all calls made with your credentials - Rotate or revoke a token immediately if you suspect it leaked, and notify [email protected] if platform data may be affected

- Respect rate limits and plan quotas; don't distribute load across accounts to evade them - Use documented endpoints. Undocumented endpoints may change or disappear without notice, and probing them for access beyond your permissions violates the Acceptable Use Policy - Cache responsibly and honor deletion: if a user deletes content you retrieved via the API, delete your copy unless you have an independent legal right to it - No mass-harvesting of user profiles, community content, or datasets beyond what your integration reasonably needs - Automated agents and bots must identify themselves via a meaningful User-Agent

If you build tools on the BCINexus API: - Be honest with your users about what data your tool accesses and where it goes - Don't present your application as made or endorsed by BCINexus without written permission - Your application must meet the same privacy, security, and research-ethics standards this platform requires of users directly - You are responsible for your application's compliance with applicable law

We version significant API changes where practical and announce breaking changes in the changelog before they take effect, except when a security issue forces an immediate change. APIs, endpoints, quotas, and features may evolve or be discontinued as described in the Terms of Service. Don't build safety-critical systems on the assumption that any endpoint is permanent.

We may throttle, suspend, or revoke API access that violates these terms, threatens platform stability, or creates security or legal risk — with notice where practical, without notice where necessary. API access is provided "as is." The warranty disclaimers, liability limits, and indemnification obligations in the Terms of Service apply fully to API usage. Questions or higher-quota requests: [email protected]