For leagues, captains, and officials
League Autopilot runs schedules, rosters, subs, and fees for community sports. Your pointer is the aircraft, so fly it to the waypoint that fits you and click. League Autopilot runs schedules, rosters, subs, and fees for community sports. Tap the waypoint that fits you to see how. League Autopilot runs schedules, rosters, subs, and fees for community sports. Pick your role below.
The brief
Each route above is printed here as plain steps. Pick your role and read the journey in order, with what runs today and what comes later.
Is an AI agent reading this for you? Send it to leagueautopilot.com/agents. That page says what an agent can do here, and how it connects.
WPT-LEAGUE
Run every league, field, season, and team fee from one admin console.
WPT-CAPTAIN
Write your rules once, and the week’s RSVPs, lineup, and subs follow them.
WPT-OFFICIAL
Coming after launch: officials say when they can work, and each drafted assignment shows its reason.
Built for community leagues in any sport
Bring your own agent
Connect the AI app you already use. Hand it your roster sheet and schedule. It builds the org under your own account, and you decide when people hear about it.
The same facts, written for an AI agent that reads this site for you. This is the text of /llms.txt. The full page for people is For AI agents.
/llms.txt · plain text
# League Autopilot > League software for community sports. It runs leagues, divisions, teams, seasons, schedules, lineups, and fees. An AI agent can set up an org for its user over MCP, under that user's own account. ## Status - Not open to the public yet. We are getting ready for our first test leagues. - The MCP connector is built. We post its address on /agents when we open to test leagues. ## Facts - Three modules: League Management, AI Scheduling, and the AI Team Captain Assistant. - An org holds leagues. A league holds divisions. A division holds teams. - Each league has a shape. Formal: players register and pay the league. Informal: the captain collects dues. - Each org can publish a public website at its own address: <address>.leagueautopilot.com. - On an iPhone, players and captains can ask Siri when their next game is and who is coming tonight. ## Connect - The user creates their org in the League Autopilot app first. No tool creates an org. - The user adds the connector in an AI app that supports MCP, then signs in as themselves. - The account needs an authenticator app. The user sets it up once. - The user picks the areas the agent may read or change. Every call runs as that user, within those areas. ## Set up an org, in this order 1. structure_add-league: Add each league, with its sport and shape (formal or informal). 2. structure_add-division: Add the divisions inside each league. 3. teams_create: Add the teams in each division. 4. venues_create: Add the fields and courts the org plays on. 5. seasons_create: Add the season as a draft or upcoming. Starting it stays in the app. 6. events_create-batch: Add the season's games, up to 100 in one request. Send one entry per game, from the home team, with the away team as the opponent. Both teams get the game. 7. seasons_enroll-batch: Enroll the teams in the season, up to 100 in one request. 8. members_import-check: Check the player list, up to 500 rows. Each problem names the row, the field, and a fix. A check saves nothing. 9. members_import-commit: Add every row or none. It needs a choice with no default: send invites now, or later. 10. members_import-send-invites: Send the held invites later, in one request. ## Command line - The la command-line tool runs the same tools from a terminal. Your user signs in once with la login; never run it yourself. Every command runs as your user. We publish it when we open to test leagues. - The CLI's own brief: https://leagueautopilot.com/cli/llms.txt ## Rules - Limits: 30 calls in 10 seconds, 1,000 calls an hour, and 100 writes an hour, per connection. A batch counts as one write. - Ask your user before any invite. send_invite has no default. - Do not add your user as a member. They already run the org. - The league, division, team, venue, and season steps notify nobody. Each change records the connection that made it. - League Autopilot runs no AI on this path. The AI is yours. - Never available: deleting teams, members, or games; changing settings; changing anyone's role. ## Not built yet - Edit or cancel an event. Tell your user to do it in the app. - Remove a member from a roster. Tell your user to do it in the app. - Record a score. Tell your user to do it in the app. ## Sandbox (On the roadmap) - On the roadmap: an agent builds a sandbox org for its user with no account, over MCP or the command line. - On the roadmap: a sandbox lasts 48 hours and sends nothing to anyone. It holds 1 league, 4 divisions, 8 teams, 150 people, 200 events, 2 seasons and 10 venues, and takes 1,000 calls. - On the roadmap: in a sandbox, do not add your user as a member. They become the owner when they keep it. - On the roadmap: your user keeps the sandbox with a claim link. Give the claim link to your user once, and never repeat it. - On the roadmap: starting a sandbox accepts the Terms of Service. We post its address here when sandboxes open. ## Links - [For AI agents](https://leagueautopilot.com/agents): what an agent can do here, how to connect, and the rules. - [For AI agents, as Markdown](https://leagueautopilot.com/agents.md) - [What ships](https://leagueautopilot.com/product): the modules, and what is built versus coming. - [Pricing](https://leagueautopilot.com/pricing) - [Privacy notice](https://leagueautopilot.com/legal/privacy) - [The CLI's brief](https://leagueautopilot.com/cli/llms.txt) - Contact: hello@leagueautopilot.com
Scroll the box for the rest, or open the whole file.
Status
League Autopilot is not open to the public yet. We are getting ready for our first test leagues. Until then, the routes above say what runs today and what comes later.
Build stage