API Usage Terms

API access requires authentication via API keys: • Generate API keys from your Settings page • Keys follow the format: nn_[64 hexadecimal characters] • Store keys securely - they are shown only once at creation • Multiple keys can be created per account • Keys can be revoked at any time Authenticate requests using either: • Header: x-api-key: your_api_key • Header: Authorization: Bearer your_jwt_token We may verify your identity and request additional information for fraud prevention. API access may be suspended if we detect suspicious activity.

To ensure fair usage and platform stability: • Default limit: 60 requests per minute per API key • Sliding window rate limiting is used • Rate limit headers are included in responses: - X-RateLimit-Limit: Maximum requests allowed - X-RateLimit-Remaining: Requests remaining - X-RateLimit-Reset: Time until limit resets • Exceeding limits returns 429 Too Many Requests Implement exponential backoff when you receive rate limit errors. If you need higher limits, contact us to discuss enterprise options.

API usage consumes credits from your account balance: • $0.01 is pre-reserved at the start of each request • Actual usage is calculated based on real model pricing after the response completes • Charge = actual provider cost × 2 • The difference is refunded to your balance • Requests failing due to insufficient balance return 402 Payment Required Monitor your credit usage through the Settings page or via the /custom/builder/usage endpoint.

You own all outputs generated through the API: • Outputs generated via the API belong to you • You may use outputs for any lawful purpose consistent with these terms • We claim no ownership rights to your generated content • You are responsible for how you use and distribute outputs Note: Outputs may not be unique. Other users with similar inputs may receive similar outputs. We do not guarantee outputs will not infringe third-party rights.

When using our API, you agree to: • Use the API only for legitimate purposes • Not attempt to circumvent rate limits or restrictions • Not use the API to generate harmful or illegal content • Respect the intellectual property of others • Not reverse engineer or attempt to extract our models • Include appropriate rate limiting in your applications • Handle errors gracefully and implement exponential backoff • Not use the API to train competing AI models • Not scrape or collect data from our services except through the API

You may not use the API to: • Develop products or services that directly compete with Neonous AI • Train, fine-tune, or improve AI models that compete with our services • Build an AI agent platform that replicates our core functionality • Reverse engineer, decompile, or extract our underlying models or systems • Create derivative works based on our proprietary technology This restriction does not prevent you from building applications that use our API as intended, even if those applications include AI features.

You are responsible for securing your API keys: • Never expose API keys in client-side code (browsers, mobile apps) • Use environment variables for key storage • Rotate keys periodically (we recommend every 90 days) • Revoke compromised keys immediately • Use separate keys for development and production • Monitor key usage for unusual activity • Implement server-side proxies for client applications We hash API keys and cannot recover them if lost. You are responsible for all usage associated with your keys.

We strive for high availability but do not guarantee uptime: • Standard plans: Best-effort availability (target 99.5%) • Enterprise: Custom SLA available upon request Maintenance windows: • Scheduled maintenance announced 48 hours in advance • Emergency maintenance may occur without notice • Status updates at status.neonous-ai.com We recommend implementing retry logic, graceful degradation, and fallback strategies in your applications.

When using our API: • The same Privacy Policy applies to API-submitted data • Use x-agent-id header to route requests to specific agents • Chat histories are stored per session and associated with your account • You can delete sessions and data via the API • We may log requests for debugging and abuse prevention (logs retained for 30 days) When building applications: • Respect your end users' privacy • Provide your own privacy policy explaining your use of AI services • Obtain necessary consents for data processing • Do not submit personal data without proper authorization