Synchronous Processing & Plan Tiers
RAIL API returns results directly. Learn how processing speed and priority vary by plan tier.
Direct Responses
All RAIL API endpoints return results directly in a single request. No polling or job status checking required. Your request is processed with tier-based priority and returns with scores and metadata.
How It Works
When you make an API request, it's processed with tier-based priority and returns results directly:
- 1.Request Submitted: Your request is received and API key validated
- 2.Credit Check: System verifies you have sufficient credits
- 3.Tier-Based Processing: Request processed with priority based on your plan (higher tiers = faster)
- 4.Direct Response: Results returned immediately with scores, metadata, and actual credits consumed
Processing Speed by Plan Tier
Each plan tier has a dedicated priority level and concurrency limit. Higher tiers get faster processing:
| Plan | Priority | Concurrency | Typical Response Time |
|---|---|---|---|
| Free | 1 (Lowest) | 1 request | 5-10s |
| Pro | 5 | 5 concurrent | 3-5s |
| Business | 10 | 10 concurrent | 2-3s |
| Enterprise | 20 (Highest) | 50 concurrent Dedicated resources | 1-2s Fastest processing |
Enterprise Advantages
- •Dedicated Resources: Enterprise customers get dedicated compute resources, eliminating queuing delays
- •Maximum Concurrency: Process as many requests simultaneously as your infrastructure can handle
- •Priority Processing: Highest priority (4) ensures your requests are processed before all other tiers
- •Near-Instant Response: With dedicated resources, expect negligible wait times for all requests
Best Practices
✅ Batch Similar Requests
Group similar content for evaluation to optimize your credit usage and processing time.
✅ Use Appropriate Endpoints
Choose the right endpoint for your needs - use basic scoring when you don't need detailed breakdowns.
✅ Implement Retry Logic
Add exponential backoff retry logic for handling temporary errors or rate limits.
Need Faster Processing?
Upgrade your plan for higher priority processing and increased concurrency limits.
View Plans