API Terms of Use

1. API Access and Authentication

1.1 API Keys

• Each API key is unique and tied to your account
• API keys must be kept secure and never shared publicly
• You must rotate API keys regularly for security
• Lost or compromised keys should be regenerated immediately
• API keys must be included in the Authorization header

1.2 Authentication Requirements

Authorization: Bearer your-api-key-here
Content-Type: application/json

2. Rate Limits and Quotas

2.1 Request Limits

• Free Tier: 100 requests per hour, 1,000 per month
• Pro Tier: 1,000 requests per hour, 50,000 per month
• Enterprise: Custom limits based on agreement
• Burst limits allow temporary spikes up to 2x hourly rate

2.2 Response Headers

X-RateLimit-Limit: 100
X-RateLimit-Remaining: 99
X-RateLimit-Reset: 1642761600
X-RateLimit-Retry-After: 3600

3. API Usage Guidelines

3.1 Request Format

• All requests must use HTTPS
• Content-Type must be application/json for POST requests
• Include proper User-Agent headers identifying your application
• Use UTF-8 encoding for all text content

3.2 Error Handling

• Implement exponential backoff for retries
• Respect 429 (Too Many Requests) responses
• Log and handle 5xx errors appropriately
• Do not retry 4xx errors except 429
• Maximum of 3 retry attempts with increasing delays

3.3 Caching Requirements

• Cache successful responses to reduce API calls
• Respect Cache-Control headers in responses
• Implement appropriate cache invalidation strategies
• Do not cache error responses

4. Video Generation Specifications

4.1 Input Requirements

• Prompt Length: 1-500 characters
• Duration: 1-30 seconds (provider dependent)
• Resolution: Varies by provider (720p-4K)
• Aspect Ratio: 16:9, 1:1, or 9:16
• Frame Rate: 24fps or 30fps

4.2 Output Formats

• Video Format: MP4 with H.264 encoding
• Audio: AAC encoding when applicable
• File Size: Typically 1-50MB depending on duration
• Delivery: HTTPS URLs with temporary access

5. Webhook Configuration

5.1 Endpoint Requirements

• HTTPS endpoint required for security
• Must respond with 200 status within 10 seconds
• Implement proper signature verification
• Handle duplicate deliveries gracefully

5.2 Event Types

• generation.started - Video generation began
• generation.completed - Video generation finished
• generation.failed - Video generation failed
• account.quota_exceeded - Usage limits reached

6. Provider-Specific Terms

6.1 Provider Selection

• Specify provider in the "model" parameter
• Fallback providers may be used if primary is unavailable
• Different providers have varying processing times
• Cost varies significantly between providers

6.2 Content Policies

• Each provider enforces their own content moderation
• Rejected content may result in failed generations
• Appeals should be directed to the specific provider
• VidRouter may add additional content filtering

7. Performance and SLA

7.1 Response Times

• API Response: < 200ms for validation and queuing
• Video Generation: 30 seconds to 10 minutes (provider dependent)
• Webhook Delivery: Within 30 seconds of completion
• Status Checks: Real-time via polling endpoint

7.2 Availability

• API Uptime: 99.5% target (alpha limitations apply)
• Provider Availability: Varies by third-party service
• Maintenance Windows: Announced 24 hours in advance
• Incident Communication: Via status page and email

8. API Versioning

• Current version: v1 (alpha)
• Version specified in URL path: /api/v1/
• Breaking changes will require new version
• Deprecated versions supported for minimum 6 months
• Version deprecation announced via email and documentation

9. Monitoring and Analytics

• All API requests are logged for debugging and billing
• Usage analytics available in dashboard
• Real-time monitoring of quotas and limits
• Error tracking and performance metrics
• Custom alerts for usage thresholds

10. Contact and Support

For technical questions about the API: