AI & Integration Credits Dashboard
OpenRouter usage, cache performance, and credit-saving monitoring.
Calls today
0
0 total logged
Cache hit rate
0%
0 cached / 0 fresh
Tokens today
0
£0 est. cost
Est. monthly cost
£0
£0 this month
By task category
No data yet.
By model
No data yet.
Top task types
No data yet.
Optimisation recommendations
- •Identical prompts are cached in the AICache entity for 24h — repeated meta titles, descriptions, and SEO tags are served from cache (status 'cached'), saving credits.
- •All AI routes through OpenRouter free-first models. Direct OpenAI calls have been removed from the property tool generators.
- •Run heavy content workflows (pillar, blog, FAQ, cluster) on a single daily schedule — avoid running multiple times per day.
- •Before regenerating any content, the gateway checks the DB cache; bump cache_ttl_minutes in AI settings to extend reuse windows.
- •Bulk-update existing published records in one pass instead of re-fetching and re-generating individually.
Note: Base44 integration credits are consumed by Core integrations (InvokeLLM, SendEmail, UploadFile, GenerateImage, etc.). AI routed through OpenRouter uses your OpenRouter key directly and does not consume Base44 integration credits — this is the primary saving.