What Are Blueprints?
Each blueprint includes:- Event structure recommendations: Optimal event naming and metadata design
- Meter configuration: Suggested aggregation types and filters
- Sample code: Working implementation examples in multiple languages
- Best practices: Tips for accuracy, performance, and cost optimization
Why Use Blueprints?
Faster Setup
Best Practices Built In
Production Ready
Available Blueprints
Choose the blueprint that matches your use case:LLM Blueprint
API Gateway Blueprint
Object Storage Blueprint
Stream Blueprint
Time Range Blueprint
How to Use a Blueprint
1
Choose your blueprint
Select the blueprint that best matches your billing scenario. Each blueprint page includes detailed implementation guides.
2
Review the event structure
Understand the recommended event naming and metadata design. Copy the event structure for your use case.
3
Create the meter
Follow the blueprint’s meter configuration instructions. Use the suggested aggregation type and filters.
4
Implement event sending
Copy the sample code for your language or framework. Replace placeholder values with your actual API keys and customer IDs.
5
Test and verify
Send test events and verify they appear in your meter dashboard with correct aggregation.
6
Customize as needed
Adapt the blueprint to your specific requirements: add custom metadata, adjust filters, or modify pricing.
Blueprint Comparison
Not sure which blueprint fits your needs? Here’s a quick comparison:Custom Implementations
Don’t see a blueprint for your exact use case? No problem:- Start with the closest blueprint: Pick the one most similar to your needs.
- Adapt the event structure: Modify metadata fields to match your requirements.
- Adjust meter configuration: Change aggregation type or filters as needed.
- Test thoroughly: Verify billing calculations with sample usage.
All blueprints are starting points. Feel free to mix concepts from different blueprints or create entirely custom implementations.