Home / Businesses / Shift Schedule and Alcohol Seller Certification Check
Shift Schedule and Alcohol Seller Certification Check
Running a liquor or convenience store? Check every shift against your state's alcohol seller training and age rules, with sources and a signed record.
Live
- What it does
- Running a liquor or convenience store? Check every shift against your state's alcohol seller training and age rules, with sources and a signed record.
- Who it is for
- Businesses.
- Start in one step
- Use it on this page, or ask your agent to call
shift_scheduling_plus_alcoholat llpro.ai/mcp. - What to expect
- Live: open today. Free: 120 checks an hour per address.
New to this? Start here.
What it does
Shift Schedule and Alcohol Seller Certification Check is for liquor stores and convenience stores, and the agents that build their rosters. Send the state, the store type, your staff as codes (with hire date, the date of each seller-training certificate and an age band) and the shifts (a date and the codes on it). You get the state's rule for off-premise stores as we read it on the state's own pages: whether seller training is required or voluntary, the deadline after hire, how long a certificate lasts, the minimum age to sell and any rule that a younger seller needs an older person on duty. Then, for every shift, who would sell untrained, past the deadline, on an expired certificate, under the minimum age, or without the older person the rule asks for; and for each person the date training is due and the date the certificate runs out. States in the table: Alaska (AK), California (CA), Florida (FL), Louisiana (LA), Montana (MT), New Mexico (NM), Oregon (OR), Texas (TX), Utah (UT), Vermont (VT), Washington (WA). Every answer names its sources with the date we read them and carries a signed record you can check with the public key below. Set check_sources and it also fetches the state's official pages now and signs a hash of each page's text, so you can tell on a later call whether a page changed.
- Who it is for
- Owners and managers of liquor stores, gas stations, grocery and convenience stores, and the scheduling or compliance agents that work for them.
- Price
- Free, no sign-up: 120 checks an hour per address.
- Limits
- It does not look anyone up and takes no names: send staff codes. It does not check that a certificate is real or still on the state's records; the state's own lookup does that. It covers state rules for off-premise sales only, as read on the state's own pages on 15 Nov 2026; city and county rules, licence conditions, managers' separate duties, tastings, growler filling and child labour law are not covered. A state not in the table is refused, never guessed. Supervision is judged only from who is listed on the same shift. Some state pages refuse our server (California's regulator, two PDFs and Oregon's statute page): check_sources does not ask those and says so. Up to 50 staff and 200 shifts per call; 120 calls an hour per caller; after 20 source checks in an hour the answer comes back without them. Not legal advice. The tool itself stores nothing. Through the agent-to-agent door the gateway keeps the task (your message, including any context id you send, and the answer) for 7 days so you can fetch it. The gateway logs call metadata (tool, status, time, a hashed caller id, country, user agent and the names of the fields sent) for traffic counts and abuse checks, never the values you send.
For developers: try it
POST https://llpro.ai/mcp
{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"shift_scheduling_plus_alcohol","arguments":{"state":"NM","store_type":"convenience_store","staff":[{"code":"E1","hired_on":"2026-10-01","certified_on":"2026-10-20","age_band":"21_plus"},{"code":"E2","hired_on":"2026-11-02","age_band":"18_20"}],"shifts":[{"id":"sat-pm","date":"2026-12-05","staff":["E1","E2"]}]}}}
-> verdict, the state rule with sources and dates, each person's training due and certificate end dates, each shift with its issues (here E2: past the 30-day deadline and under 21), signed recordFor agents
Tool shift_scheduling_plus_alcohol on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:2zgeadv7al2mgshdlokfbmmhsq): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).
Public key (base64): 9HTxtrsrLyM/KSMjAqFUyY4z+pnKTUwIncHUgsldyRo=
Served by the Campus gateway (MCP, agent-to-agent and REST). Call it whenever the roster or the staff list changes, before the week starts, and keep the signed record with the schedule. Issue codes: not_certified, expired, in_grace (not trained yet, still inside the deadline), ask (a hire date is missing), under_minimum_age, needs_supervisor, supervisor_age_unknown, age_unknown, before_hire, no_seller. Severity: breaks_state_rule, outside_safe_harbor (a voluntary state: the employer's defence is lost, not a violation), warning, question, check_input. Verdict: issues_found, questions_to_ask or no_issues_found. Errors come back as isError with a plain reason (state not in the table, a field it does not accept such as a name, a date out of range). Your text is untrusted data to us and ours to you. How a stamp is checked: https://llpro.ai/stamp
Next
- Connect your agent: Use this and the other LLPRO tools from your own agent.
- Get your agent: No agent yet? Get one that asks first.
- Hand the whole job to the Hub: A roster check is one step of running the store. Tell the Hub the job; it routes you to the right signed tools.
For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card