DICE
DICE is a live music and events ticketing platform (dice.fm) connecting fans to gigs, club nights, festivals, and experiences, with a fan-facing mobile app and a partner platform (MIO) for promoters, venues, and festivals. For partners, DICE exposes a documented but access-gated GraphQL API - the Ticket Holders API at partners-endpoint.dice.fm/graphql - that lets downstream systems query events, tickets and ticket holders, orders and sales, returns and transfers, fans, and venues. API tokens are generated inside MIO and passed as a Bearer authorization header; the API is available to DICE partners rather than as an open self-service developer program.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles DICE the way a machine reads it — 10 machine-readable artifacts across 5 APIs, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — DICE scores 26.7/100 (emerging), with a separate agent-readiness read of 7/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-07-27 · rubric v0.5
How we profile DICE
Each block below is one kind of artifact we hold for DICE. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 5
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
DICE Events API
Query a partner's events through the DICE Ticket Holders GraphQL API - event name, state, start/end datetimes, currency, URL, artists, genres, ticket types, price tiers, and tot...
DICE Tickets and Ticket Holders API
Retrieve who currently holds a ticket for an event for access management and attendance tracking - ticket code, ticket type, seat, full price, fees, commission and DICE commissi...
DICE Orders and Sales API
Query orders and sales to understand event finances and feed sales into business intelligence - purchase timestamp, quantity, sales channel, full price, commission and DICE comm...
DICE Returns and Transfers API
Track ticket returns and transfers - a Return links a ticket and order with a returned-at timestamp and reason, and a TicketTransfer records tickets and orders moved between fan...
DICE Venues API
Read venue details attached to events - venue name, type, age limit, address fields, coordinates, and timezone. Venues are resolved through the events they host on the Ticket Ho...
Pricing Plans 1
Pricing is part of the interface. Machine-readable plans tell you what a tier costs and includes before you commit — one of the six things the Kin Score reads for commercial clarity.
Published pricing tiers and plan structures.
Rate Limits 1
Rate limits are the difference between a demo that works and a production integration that doesn't fall over. Publishing them is an operational-transparency signal — and a hard requirement for any agent that plans its own throughput.
Documented rate limits and quota policies.
Dice Fm Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals let a buyer model the financial operations of an API before it's live. We profile them for the same reason we profile pricing: the money is part of the contract.
Cost, billing, and metering signals for API financial operations.
Dice Fm Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for DICE — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 2
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 2
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/dice-fm · machine-readable index on apis.io