This is a working template prepared for review by qualified counsel in the United States, India, the United Kingdom and the European Union. It is not yet in force and creates no rights or obligations until a final version is published.
- Keep your keys secret, stay within your scopes and rate limits, and don’t try to get around end-user approval.
- No API or MCP tool can place an order without the account holder’s approval or policy. Don’t build anything that pretends otherwise.
- Show our risk disclosures with any output you display to end users, and respect market-data licence restrictions.
- We give at least six months’ notice before breaking changes to a stable API version.
The summary helps you navigate; the sections below are the document.
1Scope
These terms apply to your use of the AlgoNexus REST API, GraphQL API, MCP server, SDKs and sandbox (the “APIs”), in addition to the Terms of Service and the Acceptable Use Policy. If you use the APIs for a business, you accept them on its behalf and confirm you have authority to do so. Enterprise agreements prevail where they conflict.
2Accounts, keys and scopes
- Keys are issued per environment (sandbox or production) with the scopes you request and we approve. Keep them secret and server-side; never embed production keys in client apps.
- Rotate keys at least every 90 days and immediately if you suspect exposure. You are responsible for activity under your keys.
- End-user access uses OAuth 2.1 with PKCE. You may access an end user’s data only with their consent, only for the scopes they grant, and must stop when they revoke it.
3No execution without the account holder
- The APIs can create proposals. Orders are placed only after the account holder approves in AlgoNexus, or under an investment policy they signed. You must not design flows that obscure this, auto-approve on a user’s behalf, or imply that AlgoNexus will trade without approval.
- The MCP server exposes no order-execution tool. AI assistants connected through MCP may research and propose only.
4Displaying output to end users
- Display the risk disclosure returned with each response, and do not edit outputs in a way that changes their meaning or confidence.
- Do not describe output as personalised advice, or as guaranteed, unless you hold the authorisation to provide advice and that is accurate.
- Attribute AlgoNexus where output is shown, as described in the developer docs.
- Market data delivered through the APIs is licensed from exchanges and vendors. Redistribution, storage and display are limited to what the response’s licence field allows; real-time data may require you to hold your own exchange agreements.
5Rate limits and fair use
Rate limits and quotas are shown in response headers and your developer console. Don’t circumvent them, for example by using multiple accounts. Sustained abuse may lead to throttling or suspension.
6Security and data protection
- Protect end-user data with appropriate technical and organisational measures, and notify us at security@algonexus.trade within 48 hours of any incident affecting it.
- Where you send us personal data as a business customer, our Data Processing Addendum applies.
7Fees and SLAs
The sandbox is free and has no service level. Production usage is billed as shown in your plan or order form. Paid production plans target [99.9%] monthly availability, with service credits as set out in the order form. Status: status.algonexus.trade.
8Versioning and changes
Stable APIs are versioned (for example /v1). We give at least six months’ notice, via Deprecation and Sunset headers, email and the changelog, before removing or making breaking changes to a stable version, unless a shorter period is required for security or by law. Beta features may change without notice.
9Suspension and termination
We may suspend keys immediately to protect users, markets or the platform, and will tell you why where lawful. Either party may terminate for convenience on 30 days’ notice, or immediately for material breach. On termination you must delete cached AlgoNexus data except where the law requires you to keep it.
10Warranties and liability
Except as stated in an order form, the APIs are provided “as is”. Our aggregate liability under these terms is limited to the fees you paid for the APIs in the 12 months before the claim. These limits do not apply where liability cannot be limited by law.