Updates: Reporting, Real-Time Pricing & More
Β· 2 min read

π’ Update Announcement π’β
We've rolled out several improvements and fixes to streamline functionality, enhance reporting, and improve the user experience.
β Model Reporting Updatesβ
- Image models and models with special characters now report latency properly
- Coding models are now being actively tested for availability and latency metrics
βοΈ Real-Time Price Reportingβ
We now provide real-time input/output cost reporting based on actual queries and real provider charges. This gives you the most precise breakdown of model usage costs.
Example (models route):
{
"enabled": 1,
"available": 1,
"type": "llm",
"subtype": null,
"provider": "bedrock",
"id": "titan-text-premier-v1",
"model": "titan-text-premier-v1",
"route": "amazon.titan-text-premier-v1:0",
"description": null,
"max_tokens": 32000,
"max_response_tokens": 32000,
"latency": "7022/8810/395/na/na/5409",
"query_count": 56,
"img_price": null,
"img_json": null,
"avg_cost": 0.0002729346,
"price_type": "token",
"input_cost": 1.00123355,
"output_cost": 1.49994697
}
Details:
- input_cost and output_cost reflect real costs per million tokens (e.g., $1 per million input tokens, $1.50 per million output tokens)
- If no specific cost data is available, the avg_cost column provides an average cost per 1000 charactersβuseful but less precise
π UI and SEO Improvementsβ
- Fixed the Robots file to improve web crawler behavior
- Created a SiteMap for both the root site and documentation
- Added Meta Tags to the root site
- Implemented OG Schema & OG Image Generator to generate rich previews when sharing links
- Included missing Meta Tags to ensure better indexing
π Bug Fixesβ
- Resolved an issue causing slow load times on the User Interface
Thanks for your continued support!
The APIpie Team π₯§