Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the 2MinuteWarning DDamen API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F2minutewarning.com%2F2minutewarning" | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2F2minutewarning.com%2F2minutewarning" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with 2MinuteWarning DDamen API.
Create and rename a team's offensive formations stored as offenseIDs
Add, update, and remove receiver sets and backfields within a formation
Read and edit writable team configuration settings
Manage team fieldmaps and create scoutcard settings
Create a processing job, start it, and read its detailed status
GET STARTED
Patterns agents use 2MinuteWarning DDamen API for, with concrete tasks.
★ AI formation-building assistant
An AI assistant helping a coach build out a playbook needs to create formations and populate them without clicking through the editor. Through Jentic the assistant searches for 'create an offensive formation', loads the matching 2MinuteWarning operation with its input schema, and creates the offenseID with the account token injected at call time. It then adds receiver sets and backfields to the new formation.
Create a formation with POST /offenseIDs, then add a receiver set with POST /offenseIDs/{offenseId}/receiverSets
Bulk formation import
A team migrating an existing playbook populates many formations at once. The API lets a client list current offenseIDs, create new ones, and attach receiver sets and backfields to each. An agent can read the existing set, then create and populate the missing formations so the playbook matches a source document.
List existing formations with GET /offenseIDs, then create each missing formation and attach its backfields with POST /offenseIDs/{offenseId}/backfields
Processing job orchestration
The tool runs processing jobs the team schedules against its data. The jobs resource lets a client create a job, start the one just created, and read its detailed status by job id. An agent can kick off a job and poll its status until it completes, surfacing the result to the coach.
Create a job with POST /jobs, start it, then poll GET /jobs/{jobId} until the job reports done
37 endpoints — the 2minutewarning api is the private backend for an american-football formation and scouting tool.
METHOD
PATH
DESCRIPTION
/offenseIDs
List the team's formation offenseIDs
/offenseIDs
Create a new offensive formation
/offenseIDs/{offenseId}
Get receiver and backfield sets for a formation
/offenseIDs/{offenseId}/receiverSets
Create a receiver set for a formation
/offenseIDs/{offenseId}/backfields
Create a backfield for a formation
/settings
Return the static team config settings
/jobs
List jobs with basic info
/jobs
Create a job and generate its jobId
/offenseIDs
List the team's formation offenseIDs
/offenseIDs
Create a new offensive formation
/offenseIDs/{offenseId}
Get receiver and backfield sets for a formation
/offenseIDs/{offenseId}/receiverSets
Create a receiver set for a formation
/offenseIDs/{offenseId}/backfields
Create a backfield for a formation
/settings
Return the static team config settings
/jobs
List jobs with basic info
/jobs
Create a job and generate its jobId
What agents get from Jentic-routed access to this vendor.
Setup
Wiring 2MinuteWarning by hand means obtaining a Cognito user-pool token, sending it in the Authorization header, and threading each formation's offenseID through nested receiver-set and backfield paths. Through Jentic you install once, import 2MinuteWarning from the API Directory, store the token once, and your agent calls it.
Permission scoping
Each formation's offenseID travels in the URL path such as /offenseIDs/{offenseId}/receiverSets, so a rule can pin your agent to one formation and the operations you pick. You choose which it may call, so deleting formations or editing team settings is not included unless you add it.
Credential isolation
Your 2MinuteWarning account token is stored once, encrypted, by your own Jentic One instance and attached at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'create an offensive formation' or 'start a processing job', and Jentic returns the matching 2MinuteWarning operation with its input schema so the agent calls the right endpoint without reading the backend docs.
Alternatives and complements available in the Jentic catalogue.
Specific to using 2MinuteWarning DDamen API through Jentic.
What authentication does the 2MinuteWarning API use?
The spec declares an API key scheme that carries an Amazon Cognito user-pool token in the Authorization request header. An agent sends that token on each call, and the single public endpoint for the Hudl email check is the exception. Through Jentic the token is held by your own instance and attached per call, so the agent never handles it directly.
Can I create and populate a formation with the 2MinuteWarning API?
Yes. POST /offenseIDs creates a formation and returns its offenseID, then POST /offenseIDs/{offenseId}/receiverSets and POST /offenseIDs/{offenseId}/backfields attach receiver sets and backfields to it. GET /offenseIDs/{offenseId} returns the receiver and backfield sets for a formation.
What are the rate limits for the 2MinuteWarning API?
The OpenAPI spec does not declare numeric rate limits. Because this is a private backend, confirm the current limits with the 2MinuteWarning team before scripting bulk playbook imports, and treat processing jobs as asynchronous rather than polling them tightly.
Is there a 2MinuteWarning MCP server?
You do not need an MCP server to give your agent 2MinuteWarning. Jentic connects it directly from the API Directory: import it, store your account token once, and your agent calls the formation and job operations it needs on demand.
How do I start a processing job through Jentic?
Search Jentic for 'create and start a processing job', load the POST /jobs operation to create the job, then start it and poll GET /jobs/{jobId} for status. The token is attached by your instance. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I control what my agent is allowed to do with the 2MinuteWarning API?
Yes. Each formation's offenseID sits in the URL path, so a rule can allow the agent to read and edit one formation's receiver sets and backfields while leaving settings, scoutcards, and job creation untouched unless you add them. The agent stays bound to the operations you grant, and every call it makes is logged.
Know of an official OpenAPI document? Contribute it →
For Agents
Edit an American-football team's offensive formations, receiver sets, backfields, settings, and scoutcards, and run processing jobs, for AI agents.
Use for: List all of the team's formation offenseIDs, Create a new offensive formation, Get the receiver and backfield sets for a formation, Add a receiver set to a formation
Not supported: Does not handle game footage, live scoring, or league-wide player statistics. Use for editing a team's football formation and scouting configuration only.
The 2MinuteWarning API is the private backend for an American-football formation and scouting tool. It stores a team's offensive formations as offenseIDs, each holding named receiver sets and backfields that can be added, updated, and removed. Team configuration covers writable settings, fieldmaps, and scoutcards, and a jobs resource lets the team create a processing job, start it, and read its detailed status. A Hudl Chrome extension endpoint checks whether an email is already registered.
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
Base layer of spec validity and structural soundness.
Aggregated quality score from linter diagnostics, weighted by severity.
Percentage of `$ref` references that resolve successfully.
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
Structural correctness score based on schema issues using logarithmic dampening.
Clarity, completeness, and ingestion readiness for developers and tooling.
How richly the API is illustrated with examples.
Percentage of examples that conform to their schemas.
Percentage of operations with complete response definitions (success, client error, server error).
Health of API ingestion, bundling, and resolution within Jentic pipelines.
Semantic breadth, depth, and agent comprehension for AI systems.
Coverage of descriptions across API elements.
Coverage of RFC 9457 Problem Details for error responses.
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
Coverage of summaries across operations/tags/info.
Functional utility, complexity comfort, and AI orchestration readiness.
Agent comfort level based on API operational and structural complexity.
Trust, risk posture, and security compliance.
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
Findability, semantic richness, and reasoning readiness.
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>