DICE automation
Add a new DICE ticket release when early bird sells out
It is Wednesday night, early bird is down to its last tickets and no second release exists. If the tier runs out before someone opens MIO, the cheapest way into the show simply disappears from sale until the morning.
Cotlet does it in your own DICE account with list_events, get_event, get_sales_summary and add_price_tier, called by your AI agent, an n8n workflow or a script.
Hosted · nothing to install or maintain
Official options
Can DICE do this on its own?
DICE has no API to add or change price tiers (checked 12 Oct 2026). The Ticket Holders API reads each ticket type's tiers with allocation or switch time, face value and door price, and stops there. MIO moves to the next tier by itself once that tier exists, so the gap is the release nobody set up in advance and the choice of its price and size.
By hand
How you do it in DICE today
- Sign in to MIO, open the event and check how many tickets are left in the current tier of the early bird ticket type.
- Work out the next price and size by hand from how fast early bird went.
- Add a price tier to the same ticket type. On DICE a ticket type moves between tiers either when the earlier tier sells out (allocation) or at a set date and time (time).
- Set a door sales price on the new tier if tickets will still be sold at the door, since DICE keeps a door price on each tier.
- The check happens whenever someone remembers. A tier that sells out overnight has nothing behind it, and the next release is priced in a hurry.
With an agent
How to add a new DICE ticket release when early bird sells out
Prompt
Early bird for Club Night is almost gone. Check how fast it is selling and add a second release at 18 USD for 150 tickets.- 01
Read the tier that is selling
get_event shows the current tier of each ticket type and whether it moves on by allocation or by time. The agent works on the ticket type you named and stops if a later tier already waits behind it, so it never stacks a duplicate release.
- 02
Measure the pace
get_sales_summary with since set to 7 days ago gives this week's tickets for that ticket type. The agent turns it into days left at the current pace and puts that next to the proposal.
- 03
Propose price and size
A price in your prompt is used as given. Without one, the agent finds your last comparable event with list_events, reads the step between its first and second release, and proposes the same step for you to accept or change.
- 04
Match the tier type and the room
An allocation-based ticket type gets an allocation, a time-based one gets a switch time; a mismatch is refused before any call. The new allocation plus the other ticket types must fit the event's total, or the agent proposes a smaller release.
- 05
Add after your OK, then read back
add_price_tier waits for confirmation, because fans see the new price at checkout the moment early bird runs out. Afterwards the agent reads the event again and shows the full tier ladder.
What you get back
Example data
Club Night, 14 Nov: Early bird 91 of 100 sold, 23 in the last 7 days, about 3 days left at this pace.
Early bird has no later tier; tier type: allocation.
Proposed: Second release, USD 18.00 x 150 (Rooftop Session in September stepped from 15.00 to 18.00).
Room check: Early bird 100 + Second release 150 + General admission 250 = 500 of the 500 allocation.
Added after your OK. Tiers now: Early bird 15.00 x 100, Second release 18.00 x 150.Other ways to ask
- Every evening, check Club Night and propose a second release once early bird has fewer than 20 tickets left.
- Add a final release at 22 USD to the time-based General admission ticket type, starting 7 Nov at 12:00.
- Which of my upcoming DICE events have a ticket type with no next tier and less than a week of tickets left?
Before you automate it
What DICE allows, and what to know first
- DICE shows fans the price of the tier on sale at that moment; if that tier sells out during checkout, the fan sees the next tier's price before paying and is never charged more than checkout shows.
- DICE price tiers are either allocation-based, moving on when the earlier tier sells out, or time-based, moving on at a set time, and the Ticket Holders API reports that type for each ticket type.
- Each DICE price tier stores its own face value and its own door sales price, so the door price is set release by release.
- DICE presents its wait list to partners as the measure of unmet demand on a sold-out show, telling you how many fans want in so you can raise allocation or add dates.
add_price_tier asks for your OK by default. To run it on a schedule without you, switch confirmation off for that tool in your dashboard.
Sources: DICE Help: How ticket tiers work · DICE Ticket Holders API reference · DICE for partners: ticketing
REST
Call add_price_tier from a script
curl
curl https://cotlet.dev/api/v1/dice/add_price_tier \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"ticket_type_id":"8841273","name":"Second release","price":1800,"allocation":150}'Example response
{
"ticket_type_id": "8841273",
"price_tier_type": "allocation",
"tiers": [
{
"id": "510922",
"name": "Early bird",
"price": 1500,
"allocation": 100
},
{
"id": "510987",
"name": "Second release",
"price": 1800,
"allocation": 150
}
]
}MCP: add https://cotlet.dev/mcp/v1 with the same key; the tool is dice_add_price_tier. Example data.
Schedule it in n8n, Make, Zapier or cronTools
DICE tools this automation uses
| Tool | Parameters |
|---|---|
| list_events | state, starts_after, starts_before, limit, cursor |
| get_event | event_id |
| get_sales_summary | event_id, since |
| add_price_tier | ticket_type_id, name, price, allocation, time |
Frequently asked questions
Can the agent lower a price or stop early bird sooner?
Not with add_price_tier. update_ticket_type changes a ticket type's price or allocation, or archives it to stop sales, and it also waits for your OK by default.
Give your agent access to DICE.
Free 7-day trial with 5,000 credits, no card needed. Cotlet is independent and not affiliated with DICE.