football-docs 0.5.1 → 0.5.2

package/README.md

@@ -4,7 +4,7 @@ Searchable football data provider and tooling documentation for AI coding agents
 
 **Who it's for:** Developers and analysts who use AI coding tools (Claude Code, Cursor, VS Code Copilot) to work with football data. Works with any tool that supports MCP.
 
-**What it does:** Gives your AI agent a searchable index of documentation for 15 football data providers and tools — event types, qualifier IDs, coordinate systems, API endpoints, data models, identity surfaces, and cross-provider comparisons for the data providers (StatsBomb, Opta, Wyscout, Impect, SkillCorner, and more), plus the open-source libraries people build with (kloppy, mplsoccer, socceraction, soccerdata, and more). Your agent looks up the real docs instead of guessing from training data.
+**What it does:** Gives your AI agent a searchable index of documentation for 17 football data providers and tools — event types, qualifier IDs, coordinate systems, API endpoints, data models, identity surfaces, and cross-provider comparisons for the data providers (StatsBomb, Opta, Wyscout, Impect, SkillCorner, FMDB Pro, TransferRoom, and more), plus the open-source libraries people build with (kloppy, mplsoccer, socceraction, soccerdata, and more). Your agent looks up the real docs instead of guessing from training data.
 
 **Why not just let the AI figure it out?** LLMs get football data specifics wrong constantly — Opta qualifier IDs, StatsBomb coordinate ranges, API endpoint URLs, library method signatures. These are mutable facts that change across versions. football-docs gives the agent verified, sourced documentation with provenance tracking so you know where every answer came from.
 
@@ -106,13 +106,15 @@ Add to `claude_desktop_config.json`:
 | SkillCorner | 51 | api-access, api-endpoints, data-model, physical-data, coordinate-system, concepts, identity-surfaces |
 | Free sources | 45 | overview, fbref, understat |
 | soccerdata | 40 | overview, data-sources, usage |
+| TransferRoom | 38 | api-access, api-endpoints, data-model, identity-surfaces |
 | Opta | 36 | event-types, qualifiers, coordinate-system, api-access, identity-surfaces |
+| FMDB Pro | 36 | api-access, api-endpoints, data-model, identity-surfaces |
 | socceraction | 26 | SPADL format, VAEP, Expected Threat |
 | FotMob | 7 | identity-surfaces |
 | Soccerdonna | 7 | identity-surfaces |
 | Transfermarkt | 7 | identity-surfaces |
 
-**968 searchable chunks** across 15 providers and tools.
+**1,042 searchable chunks** across 17 providers and tools.
 
 ## Contributing
 

package/docs/fmdb-pro/api-access.md

@@ -0,0 +1,120 @@
+---
+source_url: https://api.fmdb.pro/api/openapi
+source_type: crawled
+upstream_version: latest (full OpenAPI)
+crawled_at: 2026-07-09
+---
+
+# FMDB Pro API Access
+
+## Overview
+
+FMDB Pro is a commercial football database from Sports Interactive. The API exposes football entities and scouting-oriented fields for clubs, players, people, competitions, nations, countries, officials, stadiums, player appearances, historical player values, coverage, formations, and kit SVGs.
+
+- Documentation UI: `https://app.fmdb.pro/docs`
+- OpenAPI endpoint: `https://api.fmdb.pro/api/openapi`
+- Base URL: `https://api.fmdb.pro/`
+- Main API namespace: `/api/...`
+- Local OpenAPI snapshot: `specs/fmdb-pro/openapi.json`
+- OpenAPI version: `3.0.2`
+- API version in the snapshot: `latest`
+- Documentation variant in the snapshot: `full`
+
+## Authentication
+
+Requests use an API key in the `x-api-key` request header:
+
+```http
+GET /api/players?pageSize=20 HTTP/1.1
+Host: api.fmdb.pro
+x-api-key: <api-key>
+```
+
+The OpenAPI spec says API keys are issued by the FMDB Pro team. Do not put the key in query parameters or request bodies.
+
+## API versioning
+
+Data requests accept an optional `x-api-version` header. If omitted, the API returns the latest version. The documentation UI also exposes available API versions through `/api/status`, and the OpenAPI route accepts the version header when fetching a spec.
+
+```http
+GET /api/clubs HTTP/1.1
+Host: api.fmdb.pro
+x-api-key: <api-key>
+x-api-version: latest
+```
+
+## OpenAPI variants
+
+The OpenAPI route supports documentation variants:
+
+- `version=simple` gives a smaller spec.
+- `version=full` includes the full parameter lists for the data endpoints.
+- `documentationType=redoc` or `documentationType=swagger` controls the UI-oriented spec rendering.
+
+The downloaded snapshot in this repository is the `full` variant, which is useful for seeing every field-specific filter, sort, include, and exclude parameter. It is large because the player and person endpoints expose deeply nested fields.
+
+## Response envelope
+
+Search/list endpoints return JSON with a `meta` object and a `data` array. `meta` can include:
+
+| Field | Meaning |
+|---|---|
+| `calledApiUrl` | URL called by the API layer. |
+| `numTotalRecords` | Total records matching the request. |
+| `currentPageSize` | Page size for page-number pagination. |
+| `currentPage` | Current page number when using page pagination. |
+| `totalPages` | Total pages when available. |
+| `continuationToken` | Cursor token for the next continuation request. |
+| `hasMoreResults` | Whether more cursor results are available. |
+| `message` | Optional status or informational message. |
+
+## Pagination
+
+Two pagination styles are available:
+
+| Parameter | Default | Notes |
+|---|---:|---|
+| `pageSize` | `20` | Number of records per request. The documented maximum is 500. |
+| `page` | `1` | Page-number pagination. Do not combine with `continuation` or `continuationToken`. |
+| `continuation` | `false` | Enables cursor pagination for larger extracts. |
+| `continuationToken` | `null` | Cursor returned from the previous response. Requires `continuation=true`. |
+
+For large extracts, prefer `continuation=true` and repeat with `continuationToken` until the response token is `null` or `hasMoreResults` is false. The spec notes that continuation mode does not work with `pageSize`; the API chooses an optimal result size for the dataset.
+
+## Sorting and shaping
+
+Use `sortBy` and `sortOrder` for sorting. Multiple comma-separated fields are supported, and `sortOrder` can also be comma-separated:
+
+```http
+GET /api/players?sortBy=name,age&sortOrder=ASC,DESC
+```
+
+Sorting cannot be used with continuation pagination.
+
+Use `includeFields` or `excludeFields` to shape first-level response fields:
+
+```http
+GET /api/players?includeFields=id,name,dateOfBirth,fmId,externalIds
+GET /api/clubs?excludeFields=kits,finances,wageHistory
+```
+
+Field shaping applies only to first-level fields, not nested objects.
+
+## Filtering
+
+The API supports exact-match filters by field name and a family of suffix operators:
+
+| Filter form | Use |
+|---|---|
+| `<field>` | Exact match. |
+| `<field>Null`, `<field>NotNull` | Null checks. |
+| `<field>Not` | Negated exact match. |
+| `<field>In`, `<field>NotIn` | List membership. |
+| `<field>StartsWith`, `<field>EndsWith`, `<field>Contains` | String matching. |
+| `<field>Regex` | Perl-style regular expression matching. |
+| `<field>MinorThan`, `<field>MinorEqualThan` | Less-than comparisons; aliases of before-style date filters. |
+| `<field>MajorThan`, `<field>MajorEqualThan` | Greater-than comparisons; aliases of after-style date filters. |
+| `<field>Between`, `<field>BetweenIncluded` | Range comparisons using `lower|upper`. |
+
+Nested fields use dot notation where listed by the full spec, for example `country.name`, `basedClub.id`, `externalIds.hudlWyscoutId`, or `gbe.status`.
+

package/docs/fmdb-pro/api-endpoints.md

@@ -0,0 +1,123 @@
+---
+source_url: https://api.fmdb.pro/api/openapi
+source_type: crawled
+upstream_version: latest (full OpenAPI)
+crawled_at: 2026-07-09
+---
+
+# FMDB Pro API Endpoints
+
+## Endpoint inventory
+
+All endpoints are under `https://api.fmdb.pro/`. Data endpoints require `x-api-key`; most data requests also accept the optional `x-api-version` header.
+
+| Method | Path | Description |
+|---|---|---|
+| `GET` | `/api/clubs` | List of clubs. |
+| `GET` | `/api/clubsCompetitions` | List of club competitions. |
+| `GET` | `/api/continents` | List of continents. |
+| `GET` | `/api/countries` | List of countries. |
+| `GET` | `/api/coverage` | Coverage information. |
+| `GET` | `/api/formations` | List of formations. |
+| `GET` | `/api/historicalValues` | Historical values of players. |
+| `GET` | `/api/kit/{encryptedKey}.svg` | Kit SVG by unique hash from a club or nation `kits` node. |
+| `GET` | `/api/nationPlayerAppearances` | Player appearances for a nation in the last 12 months. |
+| `GET` | `/api/nations` | List of nations. |
+| `GET` | `/api/nationsCompetitions` | List of national competitions. |
+| `GET` | `/api/officials` | List of officials. |
+| `GET` | `/api/openapi` | OpenAPI JSON file for the API. |
+| `GET` | `/api/persons` | List of people. |
+| `POST` | `/api/persons` | People search using a filter-group request body. |
+| `GET` | `/api/playerAppearances` | Player appearances broken down by season and team. |
+| `GET` | `/api/players` | List of players. |
+| `POST` | `/api/players` | Player search using a filter-group request body. |
+| `GET` | `/api/regions` | List of world regions. |
+| `GET` | `/api/stadiums` | List of stadiums. |
+| `GET` | `/api/status` | System status and available API versions. |
+
+## Core catalogue endpoints
+
+The broad catalogue endpoints are:
+
+- `/api/clubs`
+- `/api/clubsCompetitions`
+- `/api/nations`
+- `/api/nationsCompetitions`
+- `/api/countries`
+- `/api/continents`
+- `/api/regions`
+- `/api/stadiums`
+- `/api/officials`
+- `/api/formations`
+
+These are useful for building local dimension tables before querying player/person data. The club and nation objects include nested relationship surfaces such as competitions, countries, stadiums, captains, kits, teams, reputation, facilities, and update timestamps.
+
+## Player and person endpoints
+
+`/api/players` is the main player surface. It returns football-playing fields, attributes, values, club/nation relationships, contracts, injuries, history, preferred moves, positions, GBE fields, tags, and external IDs.
+
+`/api/persons` is broader. It includes non-playing people and staff-oriented fields such as current job, coaching, management, medical, tactics, tendencies, preferred formations, qualification, reputation, and chairperson fields, while sharing many identity and contract fields with players.
+
+Both endpoints support:
+
+- `GET` query-parameter search.
+- `POST` body search using `RequestBodyPlayersFilterGroup` or `RequestBodyPersonsFilterGroup`.
+- Page or continuation pagination.
+- Sorting, field inclusion, field exclusion, and field-specific filters.
+
+## Appearances and values
+
+`/api/playerAppearances` returns season/team appearance aggregates with:
+
+- `playerId`
+- `playerName`
+- `teamName`
+- `competitionName`
+- `competitionType`
+- `season`
+- `startDate`
+- `endDate`
+- `matches`
+- `appearances`
+- `starts`
+- `minutesPlayed`
+- `goals`
+- `assists`
+- `yellowCards`
+- `redCards`
+- `updated`
+
+`/api/nationPlayerAppearances` returns national-team appearance information for the last 12 months.
+
+`/api/historicalValues` returns historical player value records keyed by `type` and `typeId`, with `values`, `trends`, `currentTrend`, `dateOfBirth`, `lastChange`, and `updated`.
+
+## Coverage and metadata
+
+`/api/coverage` reports coverage by country/nation/club competition and includes count objects and game type. Use it to decide whether a requested country, nation, competition, or free-agent slice is covered before running wider extracts.
+
+`/api/status` exposes system status and available API versions. The documentation UI uses it to populate the API-version selector.
+
+`/api/openapi` returns the API specification. Useful query parameters include:
+
+| Parameter | Notes |
+|---|---|
+| `version` | `simple` or `full`. |
+| `documentationType` | `redoc` or `swagger`. |
+
+## Kit SVGs
+
+`/api/kit/{encryptedKey}.svg` returns a kit image by encrypted key. The key comes from a `kits` node in a Club or Nation object. Treat this as an asset endpoint rather than a searchable data endpoint.
+
+## Common errors
+
+The OpenAPI spec defines shared response references for:
+
+| Response | Meaning |
+|---|---|
+| `400 BadRequest` | Request is malformed. |
+| `401 Unauthorized` | Missing or invalid authentication. |
+| `403 Forbidden` | API key lacks access to the requested resource. |
+| `404 NotFound` | Requested resource does not exist. |
+| `409 Conflict` | Similar entity already exists and cannot be duplicated. |
+| `422 InvalidInput` | Entity constraints failed; response includes invalid fields/checks. |
+

package/docs/fmdb-pro/data-model.md

@@ -0,0 +1,124 @@
+---
+source_url: https://api.fmdb.pro/api/openapi
+source_type: crawled
+upstream_version: latest (full OpenAPI)
+crawled_at: 2026-07-09
+---
+
+# FMDB Pro Data Model
+
+## Entity families
+
+FMDB Pro is entity-first rather than match-event-first. The OpenAPI spec exposes these major families:
+
+| Family | Main endpoints | Notes |
+|---|---|---|
+| Players and people | `/api/players`, `/api/persons` | Player/person identity, attributes, contracts, career history, values, availability, GBE fields, and external IDs. |
+| Clubs and competitions | `/api/clubs`, `/api/clubsCompetitions` | Club metadata, competitions, stadiums, kits, reputation, facilities, finances, rules, and squad constraints. |
+| Nations and geography | `/api/nations`, `/api/nationsCompetitions`, `/api/countries`, `/api/continents`, `/api/regions` | International-team, country, continent, region, and competition geography. |
+| Staff and officials | `/api/persons`, `/api/officials` | Non-playing people, staff attributes, officials, categories, and reputation fields. |
+| Performance summaries | `/api/playerAppearances`, `/api/nationPlayerAppearances` | Season/team aggregates, national appearances, and last-12-month nation appearance data. |
+| Values | `/api/historicalValues` | Historical player value trends. |
+| Coverage and docs | `/api/coverage`, `/api/status`, `/api/openapi` | Coverage discovery, version discovery, and machine-readable documentation. |
+| Assets | `/api/kit/{encryptedKey}.svg` | Kit SVG retrieval from encrypted kit keys. |
+
+## Player object
+
+The `Players` response is the richest entity surface. Important first-level fields include:
+
+| Area | Fields |
+|---|---|
+| Identity | `id`, `faId`, `fmId`, `externalIds`, `name`, `firstName`, `secondName`, `commonName`, `fullName`, `kitName`, `nickName`, `dateOfBirth`, `latestDateOfBirth`, `yearOfBirth`, `sex`. |
+| Nationality and place | `country`, `nationalityInfo`, `secondCountry`, `thirdCountry`, `declaredNation`, `residentNation`, `cityOfBirth`, `regionOfBirth`. |
+| Club state | `basedClub`, `permanentClub`, `loanClub`, `clubCompetition`, `clubNation`, `contractedNation`, `inBasedClubFirstTeam`. |
+| Contracts | `permanentClubContractId`, `loanClubContractId`, `permanentClubContract`, `loanClubContract`, `clubContracts`, `nationContracts`. |
+| Ability and roles | `currentAbility`, `recommendedCurrentAbility`, `potentialAbility`, `expectedPotentialAbility`, `position`, `positions`, `bestPosition`, `bestPositions`, `bestRole`. |
+| Attributes | `mentalTraits`, `mentalAttributes`, `physicalAttributes`, `technicalAttributes`, `goalkeeperAttributes`, plus percentile groups for each. |
+| Value and availability | `estimatedPlayerValues`, `availabilityIntelligence`, `injuries`, `unavailabilities`, `history`, `moves`, `retirements`. |
+| Regulatory/scouting | `gbe`, `tags`, `homegrownStatus`, `clubCompetitionExperience`, `reputation`. |
+
+Use `includeFields` aggressively when fetching players, because a full player object can be wide and deeply nested.
+
+## Person object
+
+The `Persons` response overlaps with players but is broader for staff and non-playing people. It includes identity, nationality, club/nation relationships, contracts, histories, GBE fields, and reputation, plus staff-specific fields:
+
+- `currentJob`
+- `coaching`
+- `coachingStyle`
+- `dataAnalyst`
+- `knowledge`
+- `management`
+- `medical`
+- `qualification`
+- `preferredFormations`
+- `preferredRolesInPossession`
+- `preferredRolesOutOfPossession`
+- `preferredTactics`
+- `tacticalTendencies`
+- `tactics`
+- `tendencies`
+- `chairperson`
+
+Use `/api/persons` when the target can be a coach, scout, official-like staff member, director, or other non-playing football person. Use `/api/players` when the target should have player-specific fields such as positions, playing attributes, preferred moves, player values, and playing career history.
+
+## Club object
+
+The `Clubs` response includes:
+
+- Identity fields: `id`, `faId`, `fmId`, `name`, `officialName`, `nameShort`, `officialThreeLetterName`, `city`, `country`.
+- Competition and squad state: `competition`, `lastCompetition`, `regionalDivision`, `teams`, `playerCount`.
+- Facilities and stadiums: `stadium`, `reserveStadium`, `youthStadium`, `trainingGround`, `trainingFacilities`.
+- People relationships: `captain`, `viceCaptain`, `chairmanTitle`.
+- Commercial and operational fields: `finances`, `income`, `wageHistory`, `reputation`, `potentialReputation`, `professionalStatus`.
+- Presentation and assets: `kits`, `currentKit`, `genericLogoId`, colours, hashtags, and nicknames.
+
+## Nation and competition objects
+
+Nations include national-team and football-governance fields such as:
+
+- `id`, `fmId`, `name`, `nameThreeLetter`, `internationalCode`
+- `country`, `continent`, `footballingContinent`, `footballingRegion`, `worldRegion`
+- `nationalTeamStadium`, `captain`, `viceCaptain`, `kits`
+- `fifaCoefficient`, `fifaFullMember`, `reputation`, `youthRating`
+- `gameImportance`, `leagueStandard`, `seasonTypeId`
+
+Club and nation competition endpoints expose competition identity, host/geography, colours, age limits, trophy and pitch flags, reputation, VAR/goal-line flags, squads/teams, rules, and GBE-related bands where applicable.
+
+## Attribute and percentile groups
+
+Player technical, mental, physical, goalkeeper, and mental-trait attributes use Football Manager-style names such as:
+
+- Technical: `corners`, `crossing`, `dribbling`, `finishing`, `firstTouch`, `freeKicks`, `heading`, `longShots`, `longThrows`, `marking`, `passing`, `penalties`, `tackling`, `technique`, `versatility`.
+- Mental: `aggression`, `anticipation`, `bravery`, `composure`, `concentration`, `consistency`, `decisions`, `flair`, `importantMatches`, `leadership`, `offTheBall`, `positioning`, `teamWork`, `vision`, `workRate`.
+- Physical: `acceleration`, `agility`, `balance`, `jumpingReach`, `naturalFitness`, `pace`, `stamina`, `strength`.
+- Goalkeeper: `aerialAbility`, `commandOfArea`, `communication`, `gkEccentricity`, `handling`, `kicking`, `oneOnOnes`, `reflexes`, `rushingOut`, `tendencyToPunch`, `throwing`.
+
+Percentile groups repeat many of these names with comparison scopes such as absolute, by age, by role, by league, and by league role.
+
+## GBE fields
+
+Player and person surfaces can include a `gbe` object. The player full spec exposes fields such as:
+
+- `gbe.status`
+- `gbe.exemptionReason`
+- `gbe.qualified`
+- `gbe.qualifiedOrPanel`
+- `gbe.accuracy.level`
+- `gbe.accuracy.percentage`
+- `gbe.detail.status.totalPoints`
+- `gbe.detail.status.maxPoints`
+- `gbe.detail.status.outcome`
+- `gbe.detail.status.pointsBreakdown.*`
+- `gbe.detail.internationalAppearances.*`
+- `gbe.detail.domesticMinutes.*`
+- `gbe.detail.continentalMinutes.*`
+- `gbe.detail.lastClub.*`
+- `gbe.detail.currentClub.*`
+
+These fields are useful for UK Governing Body Endorsement checks and scouting workflows. Treat them as derived policy/scouting fields rather than raw match-event data.
+
+## Update timestamps
+
+Most response objects include an `updated` field. The OpenAPI spec documents field-level filters for `updated`, so local mirrors can query changed entities by date/time comparison. There is no separate update-feed endpoint in the current spec; use endpoint-level `updated` filters plus continuation pagination for synchronisation.
+

package/docs/fmdb-pro/identity-surfaces.md

@@ -0,0 +1,123 @@
+---
+source_url: https://api.fmdb.pro/api/openapi
+source_type: crawled
+upstream_version: latest (full OpenAPI)
+crawled_at: 2026-07-09
+---
+
+# FMDB Pro Identity Surfaces
+
+## Primary entity IDs
+
+FMDB Pro entities expose an `id` field. Treat it as the FMDB Pro primary key for the returned entity type:
+
+- `/api/players` -> player `id`
+- `/api/persons` -> person `id`
+- `/api/clubs` -> club `id`
+- `/api/nations` -> nation `id`
+- `/api/clubsCompetitions` and `/api/nationsCompetitions` -> competition `id`
+- `/api/stadiums` -> stadium `id`
+- `/api/officials` -> official `id`
+
+Do not assume IDs are globally unique across entity types unless FMDB Pro explicitly confirms that. Store provider keys with an entity-type namespace, for example `fmdb-pro:player:<id>` and `fmdb-pro:club:<id>`.
+
+## Football Manager IDs
+
+Many entities include `fmId`. This is an important bridge field because FMDB Pro is built around Sports Interactive's football database. Ingest it separately from the FMDB Pro API `id`:
+
+| Field | Use |
+|---|---|
+| `id` | FMDB Pro API entity key. |
+| `fmId` | Football Manager database identity where present. |
+
+For person matching, prefer a composite candidate set using `fmId`, name fields, date/year of birth, nationality, and club context. Do not collapse `id` and `fmId` into one namespace.
+
+## FA IDs
+
+The player, person, and club surfaces can include `faId`. This can be useful for England/FA-facing workflows, but coverage and semantics may vary by entity type. Treat it as an external identifier with nullable/partial coverage.
+
+## External IDs
+
+The player full spec exposes `externalIds`, including `externalIds.hudlWyscoutId` as a filterable nested field. This is the clearest documented cross-provider bridge in the current OpenAPI snapshot.
+
+Use external IDs as high-confidence links only when the field is present and the target provider namespace is explicit. For example:
+
+```text
+FMDB Pro player id -> externalIds.hudlWyscoutId -> Hudl/Wyscout player id
+```
+
+## Name and birth fields
+
+Player/person identity includes multiple name and birth-date fields:
+
+- `name`
+- `firstName`
+- `secondName`
+- `commonName`
+- `fullName`
+- `kitName`
+- `nickName`
+- `dateOfBirth`
+- `latestDateOfBirth`
+- `yearOfBirth`
+- `cityOfBirth`
+- `regionOfBirth`
+
+Use `dateOfBirth` when available. `latestDateOfBirth` and `yearOfBirth` are useful for uncertain or partial birth-date cases, but they should not be treated as equivalent to a confirmed date of birth.
+
+## Nationality and country context
+
+Player/person nationality and country context includes:
+
+- `country`
+- `nationalityInfo`
+- `secondCountry`
+- `secondNationalityInfo`
+- `thirdCountry`
+- `thirdNationalityInfo`
+- `declaredNation`
+- `residentNation`
+- `basedCountry`
+- `clubNation`
+- `contractedNation`
+
+For matching, distinguish legal nationality/country fields from declared sporting nation and current football location. `declaredNation`, `clubNation`, and `contractedNation` can be especially useful disambiguators, but they answer different questions.
+
+## Club context
+
+Current and historical club context appears through:
+
+- `basedClub`
+- `permanentClub`
+- `loanClub`
+- `lastPlayingClub`
+- `lastNonPlayingClub`
+- `clubCompetition`
+- `permanentClubContract`
+- `loanClubContract`
+- `clubContracts`
+- `history`
+- `moves`
+
+Use club context as supporting evidence, not as a durable identity key. Players and staff move, and loan/permanent relationships can coexist.
+
+## Recommended matching approach
+
+For players:
+
+1. Match exact `fmId` or explicit external IDs first.
+2. Then compare `id` within the FMDB Pro namespace.
+3. Use `dateOfBirth`, `latestDateOfBirth`, or `yearOfBirth` as birth evidence.
+4. Use `fullName`, `commonName`, `firstName`, `secondName`, and `kitName` as name evidence.
+5. Use country/nation and club fields as disambiguators.
+
+For staff/persons:
+
+1. Match exact `fmId` first where present.
+2. Use `id` in the person namespace.
+3. Use name and birth evidence.
+4. Use `currentJob`, club/nation relationships, coaching/tactics fields, and career history as context.
+
+## Public-safe provenance
+
+These identity notes are derived from the public FMDB Pro OpenAPI schema and documentation UI. They describe field surfaces and matching strategy only; they do not imply access to private FMDB Pro data, credentials, or a complete mapping table.

package/docs/transferroom/api-access.md

@@ -0,0 +1,91 @@
+---
+source_url: https://www.transferroom.com/api-docs
+source_type: crawled
+upstream_version: null
+crawled_at: 2026-07-09
+---
+
+# TransferRoom API Access
+
+## Overview
+
+TransferRoom exposes a commercial club API for integrating transfer-market and recruitment data into internal club systems. The public documentation describes JSON endpoints for players, competitions, head coaches, teams, transfers, received pitches, requirements, and injury data.
+
+- Public docs page: `https://www.transferroom.com/api-docs`
+- Embedded docs app: `https://v0-simple-api-documentation-templat.vercel.app/`
+- Contact/access page linked by the docs: `https://www.transferroom.com/features/club-api`
+- Production API host shown in examples: `https://apiprod.transferroom.com`
+- API namespace shown in examples: `/api/external/...`
+
+The docs page says the API is intended to let clubs "extract TransferRoom's unique transfer market data" in JSON format for integration into internal databases.
+
+## Access levels
+
+Access is subscription-tier dependent and can also be bought standalone. The public docs describe three access groupings:
+
+| Access level | Publicly documented data |
+|---|---|
+| Lite API | Basic player identifiers, xTV (Expected Transfer Value), agency information, and player rating. |
+| Advanced API | All Lite features plus advanced player data, estimated salaries, contract information, GBE scores, head coach data, team data, transfer data, and pitches received on TransferRoom. |
+| Advanced Injury Data | Injury data across 50 leagues, injury records across 25 data points, historical data back to 2017, recurrence risk, player injury risk rating, and fatigue/workload style metrics. |
+
+Endpoint availability is tied to these access levels. For example, the public docs mark requirements and pitches as Advanced API endpoints, and injury endpoints as Advanced Injury Data endpoints.
+
+## Authentication
+
+The docs show a login call that returns a bearer token:
+
+```python
+import requests
+
+email = "example@transferroom.com"
+password = "example_p4ssW0rd"
+
+auth_url = "https://apiprod.transferroom.com/api/external/login?email=" + email + "&password=" + password
+response = requests.post(auth_url)
+token = response.json()["token"]
+```
+
+Subsequent requests send the token in the `Authorization` header:
+
+```python
+headers = {"Authorization": "Bearer " + token}
+response = requests.get(
+    "https://apiprod.transferroom.com/api/external/players?position=0&amount=100",
+    headers=headers,
+)
+```
+
+Operational note: because the public example passes credentials as query parameters, avoid logging request URLs, reverse-proxy access logs, shell history, or monitoring traces that could capture the full login URL.
+
+## Rate limits
+
+The public docs state that requests are rate limited to **300 requests per minute across all endpoints**.
+
+## Pagination
+
+List endpoints shown in the docs use offset-style pagination:
+
+| Parameter | Meaning |
+|---|---|
+| `position` | Starting point in the list. Defaults to `0` where documented. |
+| `amount` | Number of results to return. Defaults to `1000` and maxes at `10000` where documented. |
+
+The examples use `position=0&amount=100` or `position=0&amount=1000` for list extracts.
+
+## Common request pattern
+
+```python
+import requests
+
+headers = {"Authorization": "Bearer " + token}
+
+request_url = "https://apiprod.transferroom.com/api/external/players?position=0&amount=100"
+response = requests.get(request_url, headers=headers)
+data = response.json()
+```
+
+## Public documentation limits
+
+The public docs do not expose a downloadable OpenAPI/Swagger specification. Endpoint paths, examples, permissions, query parameters, rate limit, and sample response fields are visible, but exact error schemas, status codes, and full authentication contract are not described in the public page.
+

package/docs/transferroom/api-endpoints.md

@@ -0,0 +1,257 @@
+---
+source_url: https://v0-simple-api-documentation-templat.vercel.app/
+source_type: crawled
+upstream_version: null
+crawled_at: 2026-07-09
+---
+
+# TransferRoom API Endpoints
+
+## Endpoint inventory
+
+All endpoint examples use the base path `https://apiprod.transferroom.com/api/external`.
+
+| Method | Path | Access | Description |
+|---|---|---|---|
+| `POST` | `/login` | API credentials | Returns a bearer token. |
+| `GET` | `/competitions` | Documented API access | Returns competitions and team membership. |
+| `GET` | `/players` | Lite API / Advanced API | Returns player identity, club, agency, value, rating, contract, GBE, and availability fields depending on access tier. |
+| `GET` | `/coaches` | Advanced API | Returns head coach identity, career, contract, agency, rating, tactical, and team-impact fields. |
+| `GET` | `/teams` | Advanced API | Returns team identity, competition, head coach, squad value, rating, and predicted requirement fields. |
+| `GET` | `/transfers` | Advanced API | Returns player transfer movements and value-at-date fields. |
+| `GET` | `/pitches` | Advanced API, club users only | Returns pitches and plus pitches received on TransferRoom. |
+| `GET` | `/requirements` | Advanced API | Returns club recruitment requirements posted on TransferRoom. |
+| `GET` | `/injuries/competitions` | Advanced Injury Data | Returns injury records by competition. |
+| `GET` | `/injuries/players` | Advanced Injury Data | Returns player injury and predictive availability data. |
+
+## Authentication endpoint
+
+`POST /login`
+
+Query parameters shown in the public example:
+
+| Parameter | Type | Notes |
+|---|---|---|
+| `email` | string | TransferRoom account email. |
+| `password` | string | TransferRoom account password. |
+
+Sample success response:
+
+```json
+{
+  "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6Ik..."
+}
+```
+
+## Competitions
+
+`GET /competitions`
+
+Returns competition records. The public sample includes:
+
+| Field | Meaning |
+|---|---|
+| `Id` | TransferRoom competition ID. |
+| `CompetitionName` | Competition name. |
+| `Country` | Competition country. |
+| `DivisionLevel` | League/division level. |
+| `Teams` | Team IDs in the competition. |
+| `AvgTeamRating` | Average team rating. |
+| `AvgStarterRating` | Average starter rating. |
+
+## Players
+
+`GET /players`
+
+Common query parameters:
+
+| Parameter | Type | Notes |
+|---|---|---|
+| `position` | integer | Starting point in list for pagination. |
+| `amount` | integer | Number of results to return. |
+| `playerid` | integer | Filter by TransferRoom player ID where available. |
+| `myshortlist` | bit/string | Filter to players on your TransferRoom shortlists; docs show `true`. |
+| `mysquad` | bit/string | Filter to players in your team; docs show `true`. |
+
+Sample response fields include:
+
+- `TR_ID`, `Name`, `BirthDate`
+- `ParentTeamId`, `CurrentTeamId`, `ParentTeam`, `CurrentTeam`, `TeamHistory`
+- `Country`, `CompetitionId`, `Competition`, `DivisionLevel`
+- `Nationality1`, `Nationality2`
+- `FirstPosition`, `SecondPosition`, `PlayingStyle`, `PreferredFoot`
+- `ContractExpiry`
+- `Agency`, `AgencyVerified`
+- `Shortlisted`
+- `CurrentClubRecentMinsPerc`
+- `GBEScore`, `GBEResult`, `GBEIntAppPts`, `GBEDomMinsPts`, `GBEContMinsPts`, `GBELeaguePosPts`, `GBEContProgPts`, `GBELeagueStdPts`
+- `xTV`, `xTVChange6mPerc`, `xTVChange12mPerc`, `xTVHistory`
+- `BaseValue`, `BaseValueHistory`
+- `EstimatedSalary`
+- `Rating`, `Potential`
+- `AvailableSale`, `AvailableAskingPrice`, `AvailableSellOn`, `AvailableLoan`, `AvailableMonthlyLoanFee`, `AvailableCurrency`
+
+## Head coaches
+
+`GET /coaches`
+
+Common query parameters follow the same list pattern as players: `position`, `amount`, and coach-specific filters where enabled by account access.
+
+Sample response fields include:
+
+- `TR_ID`, `Name`, `BirthDate`
+- `Nationality1`, `Nationality2`
+- `CurrentTeam`, `CurrentRole`
+- `CareerHistory`
+- `Country`, `Competition`, `DivisionLevel`
+- `PreviousTeam`, `ContractExpiry`
+- `Agency`, `AgencyVerified`
+- `Rating`, `RatingChange12m`
+- `TacticalStyle`, `Suitability`, `TeamRatingImpact`
+- `TrustInYouth`, `PreferredFormation`, `SquadRotation`
+- `ThreeSeasonAvgSpend`
+
+## Teams
+
+`GET /teams`
+
+Documented query parameter:
+
+| Parameter | Type | Notes |
+|---|---|---|
+| `competitionid` | integer | Filter teams by competition ID. |
+
+Sample response fields include:
+
+- `TR_ID`
+- `Team`
+- `Country`
+- `CompetitionId`
+- `Competition`
+- `CompetitionDivisionLevel`
+- `HeadCoachID`
+- `TotalxTV`
+- `TotalBaseValue`
+- `AverageStarterRating`
+- `TeamRating`
+- `TeamRatingHistory`
+- `PredictedRequirements`
+
+## Transfers
+
+`GET /transfers`
+
+Documented query parameter:
+
+| Parameter | Type | Notes |
+|---|---|---|
+| `competitionid` | integer | Filter transfers by competition ID. |
+
+Sample response fields include:
+
+- `PlayerId`, `Player`
+- `FromTeamId`, `FromTeam`
+- `ToTeamId`, `ToTeam`
+- `Date`
+- `TransferType`
+- `TransferFee`
+- `xTVatDate`
+- `xTVatEnd`
+
+## Pitches
+
+`GET /pitches`
+
+The public docs describe this as a club-user endpoint that returns pitches and plus pitches received on TransferRoom.
+
+Sample response fields include:
+
+- `PitchType`
+- `RequirementID`
+- `Player`, `PlayerId`
+- `HeadCoach`, `HeadCoachId`
+- `PitchDate`
+- `PitchedByTeam`, `PitchedByTeamID`
+- `PitchedByAgency`, `PitchedByAgencyID`
+- `PitchCurrency`
+- `PitchTransferFee`
+- `PitchGrossAnnualSalary`
+- `PitchLoanFee`
+- `PitchSellOnPerc`
+- `PitchMessage`
+- `PitchStatus`
+
+## Requirements
+
+`GET /requirements`
+
+Returns recruitment requirements posted on TransferRoom.
+
+Sample response fields include:
+
+- `TR_ID`
+- `Active`
+- `UpdatedAt`
+- `TransferType`
+- `Position`
+- `Foot`
+- `PlayingStyle`
+- `PreferredNationality`
+- `FromAge`, `ToAge`
+- `MinHeight`
+- `TransferFee`
+- `GrossAnnualSalary`
+- `MonthlyLoanFee`
+
+## Injuries by competition
+
+`GET /injuries/competitions`
+
+Query parameters:
+
+| Parameter | Type | Required | Notes |
+|---|---|---|---|
+| `competitionid` | integer | yes | Filter by competition ID. |
+| `seasonstartyear` | integer | no | Filter to a specific season. |
+
+Sample response fields include:
+
+- `TR_ID`, `Name`
+- `TeamId`, `Team`
+- `CompetitionId`, `Competition`, `DivisionLevel`, `Country`
+- `Injury`, `BodyPart`, `InjuryType`
+- `StartDate`, `ReturnDate`, `DaysOut`, `MatchesMissed`, `ExpectedReturnDate`
+- `Training`, `SurgeryRequired`, `Recurrence`
+- `EventDescription`, `PrognosisDescription`
+- `Source_1`, `Source_2`, `Source_3`
+- `InjuryAverageLengthDays`, `InjuryMedianLength`, `InjuryLowerQuartileLength`, `InjuryUpperQuartileLength`
+- `TwoYearOccurenceRate`, `TwoYearRecurrenceRate`, `IncreasedTwoYearRecurranceRisk`
+
+The field names above preserve the public documentation spelling, including `Occurence` and `Recurrance`.
+
+## Injuries by player
+
+`GET /injuries/players`
+
+Query parameters:
+
+| Parameter | Type | Notes |
+|---|---|---|
+| `position` | integer | Starting point in list for pagination. |
+| `amount` | integer | Number of results to return. |
+| `playerid` | integer | Filter by player ID. |
+| `myshortlist` | bit/string | Filter to players on your TransferRoom shortlists; docs show `true`. |
+| `mysquad` | bit/string | Filter to players in your team; docs show `true`. |
+
+Sample response fields include:
+
+- `TR_ID`, `Name`, `BirthDate`
+- `MatchesMissed5yrsPercentage`
+- `TotalMins3Months`, `MinsPlayed3MonthsPercentile`
+- `TotalMins6Months`, `MinsPlayed6MonthsPercentile`
+- `TotalMins12Months`, `MinsPlayed12MonthsPercentile`
+- `InjuryRiskRating`
+- `xAvailability`
+- `CurrentWorkload`
+- `PlayerInjuries`
+

package/docs/transferroom/data-model.md

@@ -0,0 +1,143 @@
+---
+source_url: https://v0-simple-api-documentation-templat.vercel.app/
+source_type: crawled
+upstream_version: null
+crawled_at: 2026-07-09
+---
+
+# TransferRoom Data Model
+
+## Entity families
+
+TransferRoom's public API docs show a recruitment and transfer-market data model rather than an event-data or tracking-data model.
+
+| Family | Endpoint | Main use |
+|---|---|---|
+| Competitions | `/competitions` | Competition IDs, country, division level, team membership, and average ratings. |
+| Players | `/players` | Player identity, team context, market value, agency, contract, availability, GBE, ratings, and shortlisting/squad flags. |
+| Head coaches | `/coaches` | Coach identity, career history, tactical profile, ratings, contract, agency, and team-impact fields. |
+| Teams | `/teams` | Team identity, competition context, head coach, squad value, team rating, and predicted requirements. |
+| Transfers | `/transfers` | Player movement records with from/to teams, date, type, fee, and xTV at date/end. |
+| Pitches | `/pitches` | Pitches and plus pitches received by a club on TransferRoom. |
+| Requirements | `/requirements` | Club recruitment requirements, including position, age, height, foot, style, fee, and salary ranges. |
+| Injuries | `/injuries/competitions`, `/injuries/players` | Injury histories, sources, return dates, recurrence/occurrence rates, workload, and risk/availability metrics. |
+
+## Player model
+
+The player object centres on recruitment decision support. Public sample fields include:
+
+| Area | Fields |
+|---|---|
+| Identity | `TR_ID`, `Name`, `BirthDate`. |
+| Club context | `ParentTeamId`, `CurrentTeamId`, `ParentTeam`, `CurrentTeam`, `TeamHistory`. |
+| Competition context | `Country`, `CompetitionId`, `Competition`, `DivisionLevel`, `ParentCountry`, `ParentCompetition`, `ParentDivisionLevel`. |
+| Nationality and role | `Nationality1`, `Nationality2`, `FirstPosition`, `SecondPosition`, `PlayingStyle`, `PreferredFoot`. |
+| Contract and agency | `ContractExpiry`, `Agency`, `AgencyVerified`. |
+| Workflow flags | `Shortlisted`, `AvailableSale`, `AvailableLoan`, asking-price and loan-fee fields. |
+| GBE | `GBEScore`, `GBEResult`, and point-breakdown fields such as international appearances, domestic minutes, continental minutes, league position, continental progression, and league standard. |
+| Value and rating | `xTV`, xTV change/history fields, `BaseValue`, `EstimatedSalary`, `Rating`, `Potential`. |
+
+`TeamHistory`, `xTVHistory`, and `BaseValueHistory` are shown as JSON-encoded history strings in the public samples.
+
+## Coach model
+
+Head coach data includes:
+
+- `TR_ID`, `Name`, `BirthDate`
+- `Nationality1`, `Nationality2`
+- `CurrentTeam`, `CurrentRole`
+- `CareerHistory`
+- `Country`, `Competition`, `DivisionLevel`
+- `PreviousTeam`
+- `ContractExpiry`
+- `Agency`, `AgencyVerified`
+- `Rating`, `RatingChange12m`
+- `TacticalStyle`
+- `Suitability`
+- `TeamRatingImpact`
+- `TrustInYouth`
+- `PreferredFormation`
+- `SquadRotation`
+- `ThreeSeasonAvgSpend`
+
+This makes TransferRoom useful for both player recruitment and head-coach succession/replacement workflows.
+
+## Team model
+
+Team data includes:
+
+- `TR_ID`
+- `Team`
+- `Country`
+- `CompetitionId`
+- `Competition`
+- `CompetitionDivisionLevel`
+- `HeadCoachID`
+- `TotalxTV`
+- `TotalBaseValue`
+- `AverageStarterRating`
+- `TeamRating`
+- `TeamRatingHistory`
+- `PredictedRequirements`
+
+`TeamRatingHistory` is shown as a JSON-encoded time series in the public sample.
+
+## Transfer model
+
+Transfer records include:
+
+- `PlayerId`
+- `Player`
+- `FromTeamId`, `FromTeam`
+- `ToTeamId`, `ToTeam`
+- `Date`
+- `TransferType`
+- `TransferFee`
+- `xTVatDate`
+- `xTVatEnd`
+
+This is a historical movement surface rather than a live rumour feed.
+
+## Pitch and requirement model
+
+`/pitches` describes inbound market activity to a club:
+
+- Pitch subject: `Player`, `PlayerId`, `HeadCoach`, `HeadCoachId`
+- Sender: `PitchedByTeam`, `PitchedByTeamID`, `PitchedByAgency`, `PitchedByAgencyID`
+- Commercial terms: `PitchCurrency`, `PitchTransferFee`, `PitchGrossAnnualSalary`, `PitchLoanFee`, `PitchSellOnPerc`
+- Workflow: `PitchType`, `RequirementID`, `PitchDate`, `PitchMessage`, `PitchStatus`
+
+`/requirements` describes the club's posted recruitment need:
+
+- `Active`, `UpdatedAt`
+- `TransferType`
+- `Position`, `Foot`, `PlayingStyle`, `PreferredNationality`
+- `FromAge`, `ToAge`, `MinHeight`
+- `TransferFee`, `GrossAnnualSalary`, `MonthlyLoanFee`
+
+Together, pitches and requirements represent a club-specific workflow surface. They are not general public market data.
+
+## Injury model
+
+The injury products have two levels:
+
+- Competition-level injury records: individual injury events with injury type, body part, start/return dates, sources, recurrence, surgery/training flags, and cohort recurrence/occurrence benchmarks.
+- Player-level injury and availability records: recent minutes, minutes percentiles, match-missed percentage, injury risk rating, xAvailability, workload, and embedded player injury history.
+
+The public docs say Advanced Injury Data covers 50 leagues, has historical data back to 2017, and includes recurrence risk, player injury risk rating, and fatigue/workload-style predictive metrics.
+
+## Values and ratings
+
+Important proprietary/derived metrics in the public docs:
+
+| Field | Meaning |
+|---|---|
+| `xTV` | Expected Transfer Value. |
+| `xTVChange6mPerc`, `xTVChange12mPerc` | Recent xTV percentage movement. |
+| `xTVHistory` | xTV history time series. |
+| `BaseValue`, `BaseValueHistory` | Base value and history. |
+| `EstimatedSalary` | Salary estimate range. |
+| `Rating`, `Potential` | Player/coach evaluation fields. |
+| `TeamRating`, `AverageStarterRating` | Team-level rating fields. |
+| `xAvailability` | Predicted future injury availability percentage. |
+

package/docs/transferroom/identity-surfaces.md

@@ -0,0 +1,132 @@
+---
+source_url: https://v0-simple-api-documentation-templat.vercel.app/
+source_type: crawled
+upstream_version: null
+crawled_at: 2026-07-09
+---
+
+# TransferRoom Identity Surfaces
+
+## Primary IDs
+
+The public docs use `TR_ID` as the primary TransferRoom identifier on several entity types:
+
+- Players: `TR_ID`
+- Head coaches: `TR_ID`
+- Teams: `TR_ID`
+- Requirements: `TR_ID`
+
+Some endpoint-specific fields use entity-specific names:
+
+- `CompetitionId` or `Id` for competitions.
+- `PlayerId` for player references in transfers, pitches, and injury records.
+- `HeadCoachID` or `HeadCoachId` for coach references.
+- `TeamId`, `FromTeamId`, `ToTeamId`, `PitchedByTeamID`, and similar fields for team references.
+- `RequirementID` for linking a pitch to a posted recruitment requirement.
+
+Store IDs with entity namespaces. For example, do not assume that player `TR_ID=123` and team `TR_ID=123` refer to the same object.
+
+## Player identity fields
+
+The player surface includes:
+
+- `TR_ID`
+- `Name`
+- `BirthDate`
+- `Nationality1`
+- `Nationality2`
+- `ParentTeamId`, `ParentTeam`
+- `CurrentTeamId`, `CurrentTeam`
+- `TeamHistory`
+- `CompetitionId`, `Competition`
+- `FirstPosition`, `SecondPosition`
+- `PreferredFoot`
+
+For matching players to another provider, use `TR_ID` as the TransferRoom key and combine name, birth date, nationality, current/parent teams, positions, and team history as disambiguation evidence.
+
+## Coach identity fields
+
+The coach surface includes:
+
+- `TR_ID`
+- `Name`
+- `BirthDate`
+- `Nationality1`
+- `Nationality2`
+- `CurrentTeam`
+- `CurrentRole`
+- `CareerHistory`
+- `PreviousTeam`
+- `ContractExpiry`
+- `Agency`
+
+Coach identity should be treated separately from player identity even if the person is historically both a former player and a coach.
+
+## Team and competition identity fields
+
+Team fields include:
+
+- `TR_ID`
+- `Team`
+- `Country`
+- `CompetitionId`
+- `Competition`
+- `CompetitionDivisionLevel`
+- `HeadCoachID`
+
+Competition fields include:
+
+- `Id`
+- `CompetitionName`
+- `Country`
+- `DivisionLevel`
+- `Teams`
+
+For local mirrors, store a stable competition table before consuming team, transfer, and injury feeds. Several endpoints use `competitionid` as a query parameter.
+
+## Transfer linkage fields
+
+The transfer surface links players and clubs through:
+
+- `PlayerId`
+- `Player`
+- `FromTeamId`, `FromTeam`
+- `ToTeamId`, `ToTeam`
+- `Date`
+- `TransferType`
+
+Use `PlayerId`, `FromTeamId`, and `ToTeamId` for identity joins. Team and player names should be treated as display or fallback matching fields.
+
+## Pitch and requirement linkage
+
+Pitches can link back to requirements and to the pitched subject:
+
+- `RequirementID`
+- `PlayerId`
+- `HeadCoachId`
+- `PitchedByTeamID`
+- `PitchedByAgencyID`
+
+If `RequirementID` is null, the pitch was not tied to a posted requirement in the public sample. A pitch may concern either a player or a head coach, so code should tolerate one subject being null.
+
+## Injury identity fields
+
+Competition injury records use:
+
+- `TR_ID` for the player
+- `Name`
+- `TeamId`, `Team`
+- `CompetitionId`, `Competition`
+
+Player injury records use:
+
+- `TR_ID`
+- `Name`
+- `BirthDate`
+- `PlayerInjuries`
+
+For injury joins, prefer `TR_ID`/`PlayerId` over names. Injury records include current team context at the time of injury, which can differ from current club context in `/players`.
+
+## Cross-provider caveat
+
+The public docs do not show explicit third-party IDs such as Wyscout, StatsBomb, Transfermarkt, or Football Manager IDs. Treat TransferRoom identity as its own namespace and build cross-provider matches from names, birth dates, team history, nationality, competition context, and dates unless TransferRoom provides additional private mapping fields under contract.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "football-docs",
-  "version": "0.5.1",
+  "version": "0.5.2",
   "description": "Searchable football data provider documentation for AI coding agents. Like Context7 for football data.",
   "type": "module",
   "mcpName": "io.github.withqwerty/football-docs",

package/providers.json

@@ -61,6 +61,17 @@
       ],
       "last_crawled": null
     },
+    "transferroom": {
+      "description": "Commercial football transfer-market and recruitment API for player, coach, team, transfer, pitch, requirement, and injury data",
+      "version": null,
+      "package": null,
+      "sources": [
+        { "url": "https://www.transferroom.com/api-docs", "type": "api_docs", "note": "Public API documentation page; embeds the current docs application" },
+        { "url": "https://v0-simple-api-documentation-templat.vercel.app/", "type": "api_docs", "note": "Embedded API documentation application with endpoint examples and field descriptions" },
+        { "type": "curated", "note": "Endpoint grouping, access-tier, data model, and identity-resolution guidance from the public docs" }
+      ],
+      "last_crawled": "2026-07-09"
+    },
     "soccerdonna": {
       "description": "Public women's football entity pages, match reports, competition pages, player profiles, and staff profiles",
       "version": null,
@@ -79,6 +90,17 @@
       ],
       "last_crawled": null
     },
+    "fmdb-pro": {
+      "description": "Sports Interactive commercial football database API for clubs, players, people, competitions, geography, values, appearances, and GBE-related fields",
+      "version": "latest",
+      "package": null,
+      "sources": [
+        { "url": "https://app.fmdb.pro/docs", "type": "api_docs", "note": "Redoc/Swagger documentation UI" },
+        { "url": "https://api.fmdb.pro/api/openapi", "type": "api_docs", "note": "OpenAPI 3.0.2 spec; local snapshot at specs/fmdb-pro/openapi.json" },
+        { "type": "curated", "note": "Endpoint grouping, data model, and identity-resolution guidance from the OpenAPI spec" }
+      ],
+      "last_crawled": "2026-07-09"
+    },
     "impect": {
       "description": "Commercial football data provider; Packing/pxT metrics, KPI/score framework, detailed set-pieces (Customer API v5)",
       "version": "Customer API v5.0",