Finding
Last reviewed 2026-11-12.
Short answer. A finding is a cheaper model Meridian has already chosen for spend you can see. The glossary lists it with the Agent FinOps terms. The definition on this page is the one the glossary shows.
A finding is a cheaper model Meridian has already chosen for spend you can see. Meridian Insights and Optimize use that same choice, including the same company rules.
On Analytics, the Meridian Insights tab shows the finding for a vendor and model. The Optimize tab shows that same alternative on the endpoint that sent the calls, with the request count, the average tokens, a switch snippet, and a guide.
A seat product and a self-hosted model stay on the card with the reason, and they do not name a replacement model. Optimize uses the same access as Analytics.
Related terms
- Agent spend attribution
- Agent FinOps vs. TokenOps
- Settlement vs. billing vs. attribution
- System of record for AI labor
- FinOps for agentic AI
- Agent FinOps
- AI labor
- Spend under management
- Attribution readiness
- Cost per outcome
- AI spend assessment
- Unattributed spend
- Agent inventory
- Chargeback in an AI context
- Zero-Access assessment
- FOCUS
- BilledCost
- EffectiveCost
- ChargeCategory
- ChargePeriod
- ServiceCategory
- Provider, Publisher, ServiceProvider, and HostProvider
- Contract Commitment dataset
- Invoice Detail dataset
- Virtual currency and token columns
- Journal entry
- Suspense account
- Accrual
- Chargeback vs. showback
- Subledger
- Tie-out and reconciliation
- Trial balance
- Dimensions and worktags
- OASA
- Rate card
- Department
- Cost center
- Cost pool
- Attributed
- Settled and estimate
- Agent 365
- OASA specification
- The Missing Ledger