Pricing Overview
The Snippets AI API uses a simple, transparent pricing model:API Pricing
$10 USD per 100,000 requests Pay only for what you use with no hidden fees
What Counts as a Request?
Each API call counts toward your usage quota. The cost varies by endpoint:- Single resource operations: 1 request (GET, POST, PUT, DELETE one item)
- Batch operations: N requests (where N = number of items processed)
- Paginated operations: 1 + N requests (1 for metadata + N for items returned)
Request Costs by Endpoint
Snippets
Fetch a single snippet
Create a new snippet
Update a snippet
Delete a snippet
Fetch multiple snippets - costs 1 request per accessible snippet
Create multiple snippets - costs 1 request per snippet created
Delete multiple snippets - costs 1 request per accessible snippet deleted
Variations
Fetch a single variation
Update a variation
Delete variation(s) - costs 1 request per variation deleted
Get version history - costs 1 request per history record returned
Folders
Get folder with snippets - costs 1 request for folder + 1 per snippet returned
Create a folder
Update a folder
Delete a folder (contained snippets are orphaned)
Get multiple folders - costs M requests for folders + N for total snippets
Create multiple folders - costs 1 request per folder
Update multiple folders - costs 1 request per folder
Delete multiple folders - costs 1 request per folder
Tags
Get tag with snippets - costs 1 request for tag + 1 per snippet returned
Create a tag
Update a tag
Delete a tag
Get multiple tags - costs 1 request per accessible tag
Create multiple tags - costs 1 request per tag
Update multiple tags - costs 1 request per tag
Delete multiple tags - costs 1 request per tag
Understanding Request Costs
Single Operations (1 Request)
Simple operations on single resources always cost 1 request:Batch Operations (N Requests)
Batch operations cost N requests, where N is the number of items:Paginated Operations (1 + N Requests)
Operations that return a resource plus a list of items:Checking Your Usage
Every API response includes usage information:Cost Optimization Strategies
Use Batch Endpoints Wisely
Use Batch Endpoints Wisely
While batch endpoints are convenient, they can be expensive. Optimize by:
Implement Smart Caching
Implement Smart Caching
Reduce API calls by caching frequently accessed data:
Use Pagination Wisely
Use Pagination Wisely
When fetching folders or tags with snippets, use appropriate pagination:
Optimize Variation History Queries
Optimize Variation History Queries
Version history can be expensive if not limited:
Batch Only When Necessary
Batch Only When Necessary
Don’t use batch endpoints if you only need a few items:
Billing Examples
Example 1: Small Project
Monthly Usage:- 5,000 snippet fetches
- 200 snippet creates
- 100 snippet updates
- 1,000 folder fetches with 10 snippets each
- Snippets: 5,000 + 200 + 100 = 5,300
- Folders: 1,000 × (1 + 10) = 11,000
- Total: 16,300 requests
Example 2: Medium Integration
Monthly Usage:- 50,000 snippet fetches
- 5,000 snippet creates
- 10,000 snippet updates
- 5,000 variation fetches
- 2,000 folder operations
- Snippets: 50,000 + 5,000 + 10,000 = 65,000
- Variations: 5,000
- Folders: 2,000
- Total: 72,000 requests
Example 3: High-Volume Application
Monthly Usage:- 500,000 snippet operations
- 100,000 variation operations
- 50,000 folder/tag operations
Monitoring Usage
In Your Dashboard
Monitor your API usage in real-time:- Navigate to Settings → API Usage
- View current billing period usage
- See breakdown by endpoint
- Track daily/weekly trends
- Set usage alerts
In API Responses
Track usage programmatically:Billing Cycle
- Billing Period: Monthly (from the 1st to the last day of each month)
- Usage Reset: Quota resets on the 1st of each month
- Payment: Automatic charge on the 1st for previous month’s usage
- Minimum Charge: No minimum - pay only for what you use
Handling Insufficient Quota
When you run out of API requests, you’ll receive a403 Forbidden error:
- Wait until the next billing cycle (auto-refill on the 1st)
- Purchase additional request packages
- Upgrade to a higher plan with larger included quota
Purchasing Additional Requests
Need more requests before your cycle resets?1
Go to Settings
Navigate to Admin → API Access
2
Purchase Add-on
Click Add
3
Select Package
Choose package size (100K, 500K, 1M requests)
4
Confirm
Complete payment - requests added immediately
Enterprise Pricing
For high-volume applications, we offer custom enterprise plans:Custom Limits
Higher rate limits and request quotas
Priority Support
24/7 support with SLA guarantees
Contact Sales
Discuss enterprise pricing for your organization
FAQs
Do failed requests count toward usage?
Do failed requests count toward usage?
Yes, all authenticated requests count toward your quota, including those that return errors. However, if a request fails due to rate limiting (429), it does not count as an additional request.
What happens if I exceed my quota?
What happens if I exceed my quota?
Once you’ve used all your API requests for the billing period, you’ll receive
403 Forbidden errors until you purchase additional requests or your quota
resets on the 1st of the next month.Can I roll over unused requests?
Can I roll over unused requests?
No, unused requests do not roll over to the next billing period. We recommend
monitoring your usage to right-size your plan.
Do you offer free tiers?
Do you offer free tiers?
Currently, all API usage is billed. However, new workspaces receive an initial credit to test the API. Contact sales for evaluation credits.