Dice Fm Finops
FinOps view of the DICE partner relationship. The DICE Ticket Holders GraphQL API carries no separate published usage fee - it is provided to onboarded DICE partners. The relevant spend / revenue flow is ticketing: DICE earns a booking fee / commission on tickets sold, surfaced in the API as commission and diceCommission on tickets and orders. For a partner consuming the API, cost is primarily their own integration and infrastructure to pull and process the data, not a DICE API invoice.
Dice Fm Finops is the FinOps profile for DICE on the APIs.io network, aligned with the FinOps Foundation Framework.
It defines 3 billable meters, billed in Multiple, on a per transaction cycle, and pricing category commission-based.
The profile maps 8 FOCUS columns for cost-allocation reporting.
Tagged areas include Ticketing, Events, Partner API, FinOps, and Cost Management.
Framework Alignment
Charge Categories
FOCUS Columns
Meters
Sources
- https://dice.fm/partners
- https://mio.dice.fm/
- https://partners-endpoint.dice.fm/graphql/docs/index.html
- https://focus.finops.org/focus-specification/v1-3/
Work with this as data
Every finops artifact here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for finops
4 MCP tools reach this
find_finopsBrowse and filter every finops artifact in the catalog.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
curl "https://apis.io/api/v1/finops/dice-fm-finops"curl "https://apis.io/api/v1/finops?limit=25"Discovery needs no key. Ratings and market analysis are Pro.