/vendor/dice/AgentRouting.json or
/vendor/dice/AgentContext.json directly.
dice.fm
Overview
Does dice.fm support MCP?
No confirmed MCP support was found for dice.fm as of 2026-06-30.
What agentic protocols does dice.fm support?
As of 2026-06-30, dice.fm has confirmed support for proprietary.
Is dice.fm's API publicly accessible or partner-gated?
Partner only.
Does dice.fm explicitly prohibit automated access?
Yes. dice.fm's terms of service explicitly prohibit automated or scraper access to the public website without prior written permission.
Is dice.fm agent-ready?
Partial. dice.fm supports some agentic workflows but requires a human handoff for certain operations — see the protocols and summary sections for details.
Protocols
No evidence that dice.fm appears in any A2A launch partner list or has any public documentation, announcement, or integration related to the Agent2Agent protocol. Known A2A launch partners include Atlassian, Box, Cohere, Intuit, Salesforce, SAP, PayPal, and Workday — all enterprise software vendors with no overlap with dice.fm's ticketing/events domain. Not confirmed_absent because no vendor-specific statement from dice.fm exists; simply no evidence of any connection.
No evidence that dice.fm participates in the Agentic Commerce Protocol (OpenAI + Stripe). Named ACP launch partners identified in Stripe and OpenAI announcements are retail/fashion merchants: URBN (Anthropologie, Free People, Urban Outfitters), Coach, Kate Spade, Revolve, and Ashley Furniture — none are ticketing platforms. dice.fm is a music event ticketing and discovery platform, and no dice.fm-specific ACP integration, application, or announcement was found.
No evidence that dice.fm is among AP2's launch partners or has any documented AP2 adoption. Named launch partners included Mastercard, PayPal, Adyen, Coinbase, Etsy, Lowe's, Salesforce, and others — ticketing/event platforms like dice.fm are not mentioned in any AP2 partner lists or announcements. AP2 is an early-stage protocol (v0.2 as of April 2026) with adoption concentrated in card networks, payment processors, and enterprise platforms; consumer ticketing verticals appear absent.
No MCP server offered by dice.fm itself was found. The only MCP-related findings are third-party Apify scraper actors (e.g., hoholabs/dicefm-scraper on apify.com) that wrap dice.fm's public web surface without any official involvement from dice.fm. dice.fm has a partner-facing GraphQL API at partners-endpoint.dice.fm but no MCP interface was found associated with it. Choosing not_found rather than confirmed_absent because no vendor-specific denial or deprecation notice was located — absence is from a genuine search finding nothing, not from a dice.fm statement.
No evidence found of dice.fm adopting or being named as a launch partner for the Machine Payments Protocol (MPP). Stripe's own launch announcement and associated coverage name no ticketing or live-events vendors among early adopters; named partners are concentrated in developer-tooling and crypto-infrastructure segments. dice.fm's existing payment infrastructure relies on standard Stripe integration for ticket sales, with no public indication of MPP adoption.
No evidence found that dice.fm has implemented NLWeb or appears in any NLWeb launch partner list. Known NLWeb early partners include O'Reilly, Tripadvisor, and Snowflake — dice.fm is not among them. No /ask or /mcp endpoint surfaced for the dice.fm domain.
No evidence found that dice.fm has implemented or announced support for the Universal Commerce Protocol (UCP). Searches surfaced dice.fm's own partner/API documentation (a GraphQL ticketing API and an embeddable widget) and UCP coverage focused on retail commerce platforms (Shopify, Walmart, Target, Etsy, Wayfair). No mention of dice.fm appears in UCP participant lists or announcements. Not confirmed absent via a vendor-specific statement — status is not_found rather than confirmed_absent because no dice.fm-specific denial or deprecation notice was found.
No evidence found that dice.fm has implemented or announced WebMCP support. Searches returned no dice.fm-specific results in any WebMCP launch partner lists or developer documentation; known early adopters referenced in WebMCP coverage are unrelated to event ticketing. This is a not_found rather than confirmed_absent because no dice.fm-specific statement or deprecation notice exists — simply no presence detected.
No evidence found that dice.fm has adopted or announced x402. Searches against dice.fm specifically and against x402 launch-partner lists returned no mention of DICE. Known early adopters of x402 include Coinbase, Cloudflare, Stripe, Stellar, and Eco.com — none of the results involved DICE. The 'Partners' results for dice.fm refer exclusively to venue/promoter/artist business partnerships, not the x402 protocol.
No usable finding available for this protocol (no legitimate scan available within the candidate window).
Two distinct interfaces: (1) a GraphQL API at partners-endpoint.dice.fm/graphql for ticket-holder and order data — querying ticket codes, holder details, event finances, and sales analytics by venue/promoter partners; (2) an embeddable event-listing widget for third-party websites, providing affiliate-attributed display of DICE event inventory. The GraphQL API is read-only for post-purchase data; it does not support creating events or initiating purchases.
The GraphQL Ticket Holders API is documented at partners-endpoint.dice.fm/graphql/docs/index.html and requires a partner-generated API token from DICE's internal MIO portal, indicating access is gated behind a partner relationship rather than self-serve signup. A separate embeddable widget tool exists at dice.fm/partners/widget for affiliate/event-listing use cases. No evidence of a public, unauthenticated REST event-creation or ticketing API from DICE itself; a third-party site (ticketsdata.com) offers a wrapper but that is not a DICE-official surface.
Direct HTTP checks of dice.fm were blocked by the sandbox network environment (all requests returned connection error 000), preventing direct inspection of paths such as /llms.txt, /.well-known/agent, /AGENTS.md, and /.well-known/ai-catalog.json. Web searches returned no evidence of dice.fm publishing any self-declaration files; results only surfaced generic industry articles and dice.fm's GitHub org (dicefm), which contains engineering repositories unrelated to agent discovery. No vendor-specific evidence of any self-declaration convention was found.
Summary
Has agent interface: partial
Apply for a DICE partner relationship through official channels to obtain MIO portal access and a Bearer token for the GraphQL Ticket Holders API at partners-endpoint.dice.fm/graphql; then assess whether the API's current read-only, post-purchase scope meets the use case, and monitor for any future expansion toward event creation or purchase initiation endpoints.
AgentContext
Verified discrepancies
Vendor claim: DICE presents itself as the ticketing platform through which consumers purchase event tickets, implying it is the party responsible for the transaction. DICE's own consumer-facing US Purchase Terms state that refunds will be issued for cancelled or postponed events, creating a reasonable expectation that DICE is the consumer's direct counterparty.
What actually happens: In practice, DICE deflects refund and chargeback liability to the 'Event Partner' (Vendor), while simultaneously holding the consumer's payment. When a venue cancels or goes bankrupt, DICE tells consumers it cannot refund them because it has not received funds from the Vendor — even though the consumer paid DICE directly. DICE's own standard B2B ticketing terms explicitly make the Vendor responsible for chargebacks and refunds, creating a gap where the consumer's legal counterparty is ambiguous and disputes fall into a grey zone between DICE and the Event Partner.
Agent guidance: When purchasing tickets on dice.fm, an agent should explicitly warn the user that DICE's internal terms place refund and chargeback liability on the Event Partner rather than DICE itself. If an event is cancelled or the venue becomes insolvent, the user may be unable to obtain a refund from DICE directly despite having paid DICE. The agent should advise the user to pay with a credit card that supports chargebacks and to document all purchase confirmations, as a card dispute may be the only reliable recovery path.
- DICE's US Standard Ticketing Terms state that the Vendor is responsible for chargebacks and that DICE may withhold up to 5% of sales proceeds per event to cover chargebacks, establishing that the Event Partner — not DICE — bears refund liability internally, despite consumers paying DICE.
- A documented pattern of consumer complaints (BBB filings) shows DICE refusing refunds for cancelled events, citing non-receipt of funds from the Venue/Event Partner, even though consumers paid DICE directly and DICE's own policy states refunds are owed for cancellations.
- An October 2025 investigation documents widespread consumer complaints and legal expert commentary that DICE's practice of blaming venue bankruptcies or Event Partners to deny refunds may violate state consumer protection statutes, highlighting the merchant-of-record ambiguity.
Vendor claim: DICE's published help center policy states that if an event is cancelled, DICE will automatically issue a full refund to the customer. The in-app messaging also confirms refunds will appear in the customer's bank account within 10 business days of cancellation.
What actually happens: Multiple independently documented complaints show that when events are cancelled — including due to organizer bankruptcy — DICE withholds refunds indefinitely, citing the event organizer's financial situation as a blocker. Customers report waiting 3+ months without receiving refunds that DICE's own system confirmed were owed, and DICE support communicates that refunds will not be issued until the dispute with the organizer is resolved, contradicting the 'automatic refund' promise in their stated policy.
Agent guidance: Do not rely on DICE's stated 10-business-day automatic refund timeline when completing a transaction for a user. Before purchasing, check whether the specific event organizer has known financial or operational issues. If a cancellation refund is expected, instruct the user to initiate a credit card chargeback within their card's dispute window as a parallel safeguard, rather than waiting exclusively for DICE to process the refund voluntarily.
- Multiple BBB complaints from 2025 document users who were promised automatic refunds by DICE for cancelled events but waited over three months without payment; DICE's own response cited an organizer's Chapter 11 bankruptcy as justification for non-payment.
- DICE's official help center states customers are entitled to a 'full refund' automatically issued if an event is cancelled, creating the policy that is at issue.
- An October 2025 Medium article by OpenClassActions documents growing consumer complaints about DICE denying legally owed refunds for cancelled events.
Human handoff required for
Refund disputes where the event has been cancelled or postponed but DICE has not yet received funds from the Event Partner (organiser), causing DICE to withhold a refund it has explicitly promised in its consumer-facing policy — agent must stop, notify the user that DICE's B2B terms place liability on the Event Partner rather than DICE, and advise the user to initiate a credit card chargeback within the card issuer's dispute window rather than waiting for DICE to resolve the inter-party dispute.
- DICE's own B2B ticketing terms contractually shift chargeback and refund liability to the Event Partner, while consumers pay DICE directly — creating a verified merchant-of-record ambiguity documented in an October 2025 investigative report and multiple BBB complaints where DICE denied refunds for cancelled events by citing non-receipt of funds from Event Partners.
- A Medium investigative article from October 2025 documents DICE withholding refunds for cancelled events, with DICE support explicitly telling customers refunds are conditioned on resolving disputes with organizers, directly contradicting DICE's published automatic-refund policy.
Purchases for events where the organiser is known to be in financial distress, facing bankruptcy proceedings, or has a recent history of event cancellations — agent must pause the transaction, surface the merchant-of-record ambiguity risk to the user, confirm the user understands that a DICE refund may be withheld indefinitely if the organiser cannot settle with DICE, and confirm the user intends to pay by a credit card with chargeback capability before proceeding.
- BBB complaints and the October 2025 investigative report specifically document DICE withholding refunds in cases involving organiser Chapter 11 bankruptcy, with customers waiting 3+ months despite DICE's help center promise of automatic refunds within 10 business days.
- DICE's consumer-facing US Purchase Terms state that refunds will be issued for cancelled or postponed events, but DICE's B2B terms make the Vendor responsible for chargebacks, creating a gap where the consumer's legal counterparty is ambiguous when the organiser is insolvent.
Situations where a cancelled-event refund promised by DICE has not appeared in the user's account within 10 business days — agent must not reassure the user that the refund is simply delayed; instead escalate to a human to assess whether the organiser is in financial dispute with DICE and whether the card chargeback window is still open, since waiting further may cause the user to lose their chargeback right.
Five discrepancy categories were checked for dice.fm: (1) Pricing — no finding; searches found DICE's own documentation of all-in pricing and a historical 2018 fee controversy now resolved, with no current evidence of a search-to-checkout price gap. (2) Availability — no finding; no verified pattern of ghost inventory or tickets displayed as available but unbookable was surfaced from any independent source. (3) Identity/Merchant-of-Record — finding present; multiple sources including BBB complaints, DICE's own B2B terms, and a 2025 investigative report confirm that DICE deflects refund and chargeback liability to Event Partners while holding consumer payments directly, creating an active and documented merchant-of-record ambiguity. (4) Policy — finding present; DICE's help center promises automatic full refunds within 10 business days for cancelled events, but 2025 BBB complaints and an October 2025 investigative article confirm DICE conditions refunds on resolving disputes with organizers, with customers waiting months without payment. (5) Undisclosed Constraints — no finding; post-transaction refund failures and event-level transfer restrictions were noted but no mid-transaction hidden constraints were independently verified. The identity and policy findings are mutually reinforcing and represent the primary risk area for agent-assisted transactions on this platform.