LLPROBeta

Home / Businesses / Pay Period Calendar (US Holidays)

Pay Period Calendar (US Holidays)

Build a year's weekly, biweekly, semimonthly or monthly payroll calendar with pay dates moved off weekends and US federal holidays (5 U.S.C. 6103 or the Federal Reserve schedule), with a signed record.

Testing

What it does
Build a year's weekly, biweekly, semimonthly or monthly payroll calendar with pay dates moved off weekends and US federal holidays (5 U.S.C. 6103 or the Federal Reserve schedule), with a signed record.
Who it is for
Businesses.
Start in one step
Ask your agent to call pay_period_calendar at llpro.ai/mcp (free, no sign-up). This page explains the tool; it has no form to run it.
What to expect
Testing: open to try. Free

New to this? Start here.

What it does

Pay Period Calendar (US Holidays) is for agents that set up or run payroll in the United States and need every pay period and pay date for a year, with holiday and weekend moves worked the same way every time. Build a year's payroll calendar: every pay period and pay date for a weekly, biweekly, semimonthly or monthly schedule, with pay dates that fall on a weekend or a US federal holiday moved to the business day before (or after, if you choose). Send the year, the frequency, how many days after the period ends you pay, and for weekly or biweekly one period end date from your schedule. Holidays follow 5 U.S.C. 6103 as federal offices observe them (Saturday holiday on the Friday before, Sunday holiday on the Monday after) or, if you pay by direct deposit, as the Federal Reserve Banks do (a Saturday holiday is not moved). Get back each period's start and end, the scheduled and actual pay date with the reason it moved, the number of pay dates in the year, and the holidays used. It is one of the HR and payroll department tools LLPRO builds for the work agents do across business software (Gusto, ADP, Paychex, Quickbooks Payroll, Rippling). Every answer carries the written rule it used, what it does not do, its sources with dates, and an Ed25519 signature you can check against the key below.

Who it is for
Agents that set up or run payroll in the United States and need every pay period and pay date for a year, with holiday and weekend moves worked the same way every time.
Price
Free, no sign-up: 120 calls an hour per address and 3,000 an hour across all callers. Paid calls are planned and not charging.
Limits
Up to 30,000 bytes per call; larger requests are refused, never cut. Unknown fields are refused with the list of accepted ones. Money takes up to 2 decimals unless a field says more, and every sum is exact (send amounts as numbers or strings; commas only as thousands separators, 1,234.56). Nothing you send is stored by the tool; no model and no network are used. Does not include state holidays, Inauguration Day (5 U.S.C. 6103(c), Washington, D.C. area only), one-off closings by Executive order (such as an extra day at Christmas) or a bank's own closings. Does not check state pay-frequency or payday laws (many states set how often and how soon wages must be paid, and some say which way a payday on a non-workday moves); the direction is your choice. Does not handle semimonthly or monthly schedules whose periods do not follow the calendar (for example the 26th to the 10th), or pay dates set by weekday instead of a day count. Not legal or payroll advice.

For developers: try it

POST https://llpro.ai/mcp
{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "pay_period_calendar", "arguments": {"year": 2026, "frequency": "monthly"}}}

For agents

Tool pay_period_calendar on https://llpro.ai/mcp and in the tools list. Signed answers are checked with the public key below (signer llpro1:3xzt6h3ijkuokiumyoukyklypm): an Ed25519 signature over the observation as canonical JSON (sorted keys, no spaces).

Public key (base64): oAjbifF9mc7Bpw/+h2VOdz9AeSwR148QZoLs+QNgSSU=

For agents that search MCP registries for payroll calendar, pay dates, biweekly pay schedule tools (listed in MCP registries, served by the Campus gateway: MCP, agent-to-agent and REST). One fixed, written rule per call, a signed record, no account needed.

Next

For agents: this page as Markdown · JSON · llms.txt · MCP endpoint llpro.ai/mcp · agent card