These API Terms of Use (“API Terms”) govern your access to and use of the Nexus Glass application programming interfaces (APIs), WebSocket feeds, and related developer services provided by Nexus Quant (“Company,” “we,” “us,” or “our”). These API Terms supplement our Terms of Service. In the event of conflict, these API Terms prevail for API-related matters.
By using our APIs, generating API keys, or integrating with our data feeds, you agree to these API Terms.
1. API Access and Authentication
1.1 API Keys
Access to the Nexus Glass API requires a valid API key, obtained through your account dashboard. Each API key is:
- Bound to a single account and a specific service tier
- Non-transferable and for your use only
- Subject to the rate limits and endpoint access defined by your tier
1.2 Authentication
All API requests must include your API key in the request header. Unauthenticated requests will be rejected with an HTTP 401 response. Requests with invalid or expired keys will receive an HTTP 403 response.
1.3 Key Security
You are responsible for the security of your API keys. You must:
- Store API keys securely (environment variables, secrets managers — never hardcoded)
- Never expose keys in client-side code, public repositories, or browser-accessible locations
- Never share keys with third parties
- Immediately revoke and regenerate compromised keys
- Use separate keys for development and production environments
You are liable for all activity performed using your API keys, including unauthorized use resulting from compromised credentials.
2. Service Tiers and Rate Limits
| Feature | FREE | PRO | FASTFEED |
|---|---|---|---|
| Rate Limit | 2 req/sec | 10 req/sec | 10 req/sec |
| Burst Limit | 5 req burst | 20 req burst | 20 req burst |
| REST Endpoints | Basic (health, heatmap, OI) | All endpoints | All endpoints |
| WebSocket | Not available | Not available | Real-time stream |
| Historical Data | 24 hours | 30 days | 90 days |
| Daily Request Limit | 10,000 requests | 100,000 requests | 500,000 requests |
| Commercial Use | Not permitted | Permitted | Permitted |
| Concurrent Connections | 1 | 3 | 5 (+ WebSocket) |
2.1 Rate Limit Enforcement
Rate limits are enforced per API key at both the application layer (Fiber middleware) and infrastructure layer (nginx). When you exceed your rate limit:
- You will receive an HTTP
429 Too Many Requestsresponse - The response will include a
Retry-Afterheader indicating when you can retry - Rate limit headers (
X-RateLimit-Limit,X-RateLimit-Remaining,X-RateLimit-Reset) are included in all responses
Persistent or aggressive rate limit violations (sustained exceeding for more than 5 minutes) may result in temporary key suspension (1 hour), followed by permanent suspension for repeated offenses.
2.2 Fair Use
All tiers are subject to fair use. The following patterns are considered abuse regardless of tier:
- Automated bulk data extraction designed to replicate the full dataset
- Systematic polling of all endpoints in rapid succession
- Using multiple keys to circumvent per-key rate limits
- Sharing API responses as a competing real-time data service
3. WebSocket Feed (FASTFEED Tier)
The WebSocket real-time feed is available exclusively to FASTFEED tier subscribers. Connection rules:
- Connect to
wss://nexusglass.live/wswith your API key - Maximum 2 concurrent WebSocket connections per API key
- Connections are authenticated on handshake; invalid keys are disconnected immediately
- Idle connections (no subscription activity for 5 minutes) may be terminated
- Implement exponential backoff for reconnection (initial: 1s, max: 30s)
- Do not attempt to reconnect more than once per second
4. Data Usage and Restrictions
4.1 Permitted Use
- FREE tier: Personal, non-commercial analysis and research only
- PRO tier: Personal and commercial use, including internal business analytics, research reports, and integration into private trading systems
- FASTFEED tier: All PRO uses, plus real-time data integration into automated systems
4.2 Prohibited Use
Regardless of your tier, you may NOT:
- Redistribute raw API data or WebSocket streams as a data service
- Create a competing product that substitutes for Nexus Glass using our data
- Store and resell historical data obtained from our APIs
- Use data to manipulate markets, front-run trades, or engage in market abuse
- Scrape, mirror, or create bulk copies of the dataset
- Present API data as your own proprietary data without attribution
4.3 Attribution
If you display Nexus Glass data in any public-facing application, you must include visible attribution: “Data by Nexus Glass” or “Powered by Nexus Glass” with a link to nexusglass.live.
5. Service Level and Availability
5.1 Availability Target
We target 99.5% monthly uptime for the REST API and WebSocket feed, measured as the percentage of 1-minute intervals in which the API returns successful responses to valid requests. This is a target, not a guarantee.
5.2 Exclusions
The following are excluded from availability calculations:
- Scheduled maintenance (announced at least 24 hours in advance when possible)
- Force majeure events
- Third-party exchange API outages that affect data availability
- Issues caused by your implementation, network, or infrastructure
- DDoS attacks or security incidents requiring emergency response
5.3 Status and Incident Communication
API status, maintenance schedules, and incident reports are communicated through our status endpoint at GET /health and via email to registered API key holders.
6. API Versioning and Changes
6.1 Current Version
The current API version is v1, accessible at https://nexusglass.live/api/v1/.
6.2 Breaking Changes
We will make reasonable efforts to avoid breaking changes to existing API endpoints. When breaking changes are necessary, we will:
- Announce the change at least 30 days in advance via email
- Provide a migration guide
- Support the previous version for at least 90 days after the new version launches
6.3 Non-Breaking Changes
We may add new endpoints, new fields to existing responses, or new optional query parameters without prior notice. Your implementation should be resilient to additional fields in JSON responses.
7. Error Responses
The API uses standard HTTP status codes:
| Code | Meaning | Action |
|---|---|---|
| 200 | Success | Process response normally |
| 400 | Bad Request | Check request parameters |
| 401 | Unauthorized | Check API key |
| 403 | Forbidden | Endpoint not available for your tier |
| 429 | Rate Limited | Wait and retry (check Retry-After header) |
| 500 | Server Error | Retry with exponential backoff |
| 503 | Service Unavailable | Service is temporarily down; retry later |
8. Intellectual Property
All data, algorithms, models, and systems underlying the API are the intellectual property of Nexus Quant. Your API access grants you a limited, revocable, non-exclusive license to access and use data in accordance with these API Terms and your tier permissions. No ownership rights are transferred.
9. Suspension and Termination
We may suspend or revoke your API access immediately and without notice if:
- You violate these API Terms or the general Terms of Service
- Your usage patterns indicate abuse, scraping, or circumvention attempts
- Your API key has been compromised and is being used for unauthorized access
- You fail to pay applicable subscription fees
- Your usage poses a risk to Platform stability or other users
Upon suspension or termination, all active API keys will be immediately revoked. You must cease all API calls and delete any cached data obtained in violation of these terms.
10. Limitation of Liability
API data is provided “as is” without warranties of any kind, express or implied. We do not warrant that the API will be uninterrupted, error-free, or that data will be accurate or timely. The limitation of liability provisions in our Terms of Service apply in full to your use of the API.
11. Contact and Support
For API-related questions, technical support, or to report issues:
Nexus Quant
API Support: support@nexusglass.live
API Documentation: nexusglass.live/docs
See also: Terms of Service | Privacy Policy | Acceptable Use Policy
