DICE · FinOps Profile

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.

Category: Ticketing and Events Pricing: Commission-Based Billing: Per Transaction FOCUS v1.3
TicketingEventsPartner APIFinOpsCost ManagementFOCUS

Framework Alignment

Framework
FinOps Foundation Framework
Data Spec
FOCUS v1.3

Charge Categories

UsageAdjustment

FOCUS Columns

BillingCurrency
Multiple
ChargeCategory
Usage
InvoiceIssuerName
DICE
PricingCategory
Commission-Based
ProviderName
DICE
PublisherName
DICE
ServiceCategory
Ticketing and Events
ServiceName
DICE Ticketing

Meters

ticket_commission
Unit: tickets
Booking fee / commission DICE earns per ticket sold, surfaced as commission and diceCommission in the API.
refund_returns
Unit: tickets
Returned tickets and refunds that adjust net sales, read from the Return entity.
integration_compute
Unit: hours
Partner-side infrastructure cost to query and process API data (no DICE invoice).

Sources