Free drinks for conference attendees, ordered by AI agents, inside limits Starbucks sets
A proposed sponsorship for the Penn State AI competition in March 2027. During the live demonstration, Starbucks offers a set number of free drinks, picked up at a Starbucks store in State College. Attendees order by chatting with an AI agent on their phone. C=US is the control plane between the agents and Starbucks: Starbucks signs the terms of the promotion once, and C=US enforces them on every order, so no agent can give away more than Starbucks agreed to.
- Partner API credentials and terms for the demonstration: menu, store and price lookups, and placing a pickup order that Starbucks fulfills free of charge.
- The promotion: how many free drinks, for which hours of the conference, at which State College store or stores, and any limit on the drink.
- Permission to show it at the competition, with Starbucks named as the sponsor.
Starbucks keeps the customer account, the order and the pickup. Attendees pay nothing, and nothing reaches a Starbucks system until Starbucks issues the credentials.
What an attendee does
- AttendeeOpens the demo on their phone, enters the one-time code from their badge or a card at the booth, and creates a passkey (fingerprint, face or screen lock). One code gives one passkey, which is what limits each attendee to one free drink. No password, card or app. Once Starbucks offers an account link, linking a Starbucks account can replace the code.
- Attendee and agentAsks the agent for a drink in plain words, and picks and customizes one.
- AgentOffers the State College stores the promotion allows, and orders the exact drink at the chosen store. An order within Starbucks’ terms is placed at once; anything outside them is refused with the reason.
- Starbucks appWith the partner API, the order appears in the attendee’s Starbucks app, free, ready for pickup at the store.
Starbucks’ terms, enforced on every order
Starbucks signs the promotion once. The C=US gateway checks every order against it before anything reaches Starbucks, and refuses anything outside it.
| Term | What happens |
|---|---|
| Total free drinks | When the promotion’s count is used up, every further order is refused. The count is kept by the gateway, so two agents cannot spend the same last drink. |
| One per attendee | A second order for the same attendee is refused, however it is asked for. Orders name the attendee only by an anonymous code, never a name or account. |
| Demonstration hours | Orders before the start or after the end are refused. |
| Stores | Only the State College stores Starbucks names can be chosen. |
| Which drinks | A price or menu limit, if Starbucks sets one, is checked on the quoted drink. |
| Starbucks’ kill switch | Starbucks can stop any agent acting under its promotion: one agent it does not like, or all of them at once. A stopped agent is refused at its next request, by the C=US gateway and by Starbucks’ own check, and cannot resume until it is restarted. Starbucks can also suspend the whole promotion. Every stop is itself a signed record. |
How Starbucks can trust an agent it has never seen
- C=US directoryThe agent has its own entry (for example
cn=coffee-hosted-agent,ou=AI-Agents,o=Cequs,c=US) and runs only as a short-lived instance with a certificate that names it. - C=US gatewayChecks the agent’s certificate and Starbucks’ promotion terms for the attendee the order is for, and issues a short-lived signed permit for that one order.
- StarbucksBefore giving away a drink, Starbucks’ side can check the agent’s certificate and the permit itself, against keys Starbucks pins. It does not have to take the agent’s word.
- Starbucks’ kill switchStarbucks stops an agent with an order signed by the same key that signed the promotion, sent to the C=US gateway. Nobody else can stop or restart an agent on Starbucks’ behalf, and a stop also blocks an order already approved but not yet placed.
- Signed recordEvery order and every refusal is signed and kept in an append-only log. Any order can be re-verified offline from its export.
What the audience sees
A dashboard on a screen beside the stage (Grafana or Kibana): free drinks dispensed and remaining, drinks per store, how many people received one, and refusals by reason (already had one, promotion used up, outside the hours, agent stopped by Starbucks). It is fed by Starbucks’ own report: Starbucks asks for it with its key, the C=US gateway signs every report, and a report whose signature does not check is never shown. Starbucks can run the same dashboard on its side. Reports hold counts only, never who received a drink.
What runs today, and what is still to build
The ordering path runs today at cequs.com/coffee/, against a simulated coffee store. No real store is contacted and no payment is made. The promotion is built and tested end to end on the simulated services, and is not deployed yet. Current status: LOADING
| Live on the simulated store | Built and tested, not deployed | Still to do |
|---|---|---|
|
|
|
On the live demo today, the agent’s authority comes from a grant its owner signs, and the owner approves each order with a hardware security key. The promotion moves that authority to Starbucks’ signed terms, and each attendee signs in with their own passkey.
Contact
To discuss the sponsorship, or to arrange a live demonstration: security@cequs.com.
Until Starbucks approves, everything here runs on the simulated store, and this page describes a proposal only. Starbucks has not reviewed, approved or endorsed it. Starbucks is a trademark of Starbucks Corporation, named here only as the intended sponsor.