padel.how Racket Reviews

Overview

padel.how exposes structured, machine-readable data for published reviews and equipment categories, plus a public read-only MCP service for the racket catalogue. The JSON endpoints are static files; the MCP endpoint is a local service behind nginx. No authentication or API key is required. MCP requests are rate-limited; static JSON is not an unlimited API contract.

Aggregate JSON files include a generated field (ISO 8601 date) so consumers can detect stale caches. Per-slug detail JSON keeps the same stable schema but may omit generated. URLs in JSON responses are absolute https://padel.how/… paths where a URL field is present.

For AI agent discovery, see llms.txt (compact), llms-full.txt (expanded English agent context).

Remote MCP

The public Streamable HTTP endpoint is https://padel.how/mcp. It is a no-auth, read-only service for published racket catalogue data, using stable MCP protocol 2025-11-25. The edge permits GET, POST and DELETE, limits each IP to 60 requests per minute with burst 20 and five concurrent requests, and does not use wildcard CORS.

Tools: search_rackets, get_racket, compare_rackets, and list_racket_brands. Resources: padel://dataset/rackets, padel://methodology/rackets, and padel://rackets/{slug}. Results contain concrete review and methodology locators; cite those URLs in derived answers.

The service does not provide prices, stock, individual fit, injury advice, unpublished content, or a recommendation tool. Editorial player-level values are catalogue labels, not personalised advice. See the server.json manifest and health endpoint. A plain GET to /mcp is not a success check because MCP negotiation requires protocol headers.

Racket endpoints

Endpoint	Description	Items
/rackets.json	Aggregate of all racket reviews. Per record: name, slug, url, brand, year, score, shape, thickness_mm, weight_g, balance_cm, face_material, core, surface, player_level, play_style (attacking, control, all-round, defensive, net play, spin), court_side (left, right, both), demand (forgiving, moderate, demanding), scores (10 categories), gender, junior, image, markdown_url, json_url, feel (stiffness 0–100, power_on_demand 0–10 and the plotted map position), retailers (store, affiliate url, price, currency) and price_range where a price is published. The file also carries license, endpoints and a fields dictionary, so a single fetch explains itself.	167
/data/offers.json	The retailer offer feed behind both the JSON catalogue and the MCP endpoint: one entry per racket slug, each offer carrying retailer, affiliate url, price amount and currency, availability, region, the timestamp it was observed at, and the affiliate disclosure text.	88 rackets
/rackets/{slug}.json	Full per-racket detail: everything in the aggregate plus verdict text, FAQ array, compared_to slugs and the licence block. Example: /rackets/nox-at10-18k-2026-review.json	217 files
/data/rackets.json	Rackets aggregate for site data. Its field contract is related to, but not a byte-for-byte mirror of, /rackets.json.	167

Racket score categories (0–10 each, sum = /100 score): maneuverability, net_performance, control, defensive_output, off_center_stability, sweet_spot, spin_generation, power_ceiling, power_accessibility, comfort.

Methodology: padel.how/equipment/racket/methodology/

Shoe endpoints

Endpoint	Description	Items
/shoes.json	Aggregate of all padel shoe reviews. Fields: name, slug, url, brand, score, price_band, player_level, best_for, scores (7 categories).	64
/data/shoes/{slug}.json	Full per-shoe detail including specs object and scores. Example: /data/shoes/babolat-premura-3-review.json	64 files
/equipment/shoes.json	Legacy shoes aggregate (same data, maintained for backwards compatibility).	64

Shoe score categories (0–10 each): grip, lateral_support, cushioning, breathability, durability, fit_security, value.

Shoe review hub: padel.how/equipment/shoes/ — Methodology: padel.how/equipment/shoes/methodology/

Overgrip endpoints

Endpoint	Description	Items
/overgrips.json	Aggregate of all published overgrip reviews. Fields: name, slug, url, brand, score, best_for, scores (6 categories).	4
/data/overgrips/{slug}.json	Full per-overgrip detail including declared specs, measured weight/length, moisture absorption data. Example: /data/overgrips/head-xtremesoft-overgrip-review.json	4 files

Overgrip score categories (0–10 each): feel, moisture_absorption, tackiness, durability, weight_impact, value.

Overgrip review hub: padel.how/equipment/overgrip/ — Reviews library: padel.how/equipment/overgrip/reviews/ — Methodology: padel.how/equipment/overgrip/methodology/

Search indexes

Endpoint	Description
/data/search-index.en.json	Lightweight search index used by on-site search. Example: /data/search-index.en.json
/data/equipment.json	Combined equipment aggregate: shoes (64), balls (7), bags (5), accessories (3). Total 79 items.

Agent discovery files

File	Description
/llms.txt	Compact LLM/agent manifest. Lists all JSON endpoints, key pages, score interpretations, languages and URL patterns. Start here for AI agent integration.
/llms-full.txt	Expanded agent context and important URL references for published pages.
/urls.txt	Complete sitemap-derived URL list. One absolute URL per line for all published pages.
/robots.txt	Standard crawl policy. All paths are allowed by default.

Markdown versions of indexable pages

Markdown versions of indexable pages are available by appending index.md to any page URL, including localized URLs. This provides clean, structured text for LLM context windows without HTML parsing.

Pattern: https://padel.how/{page-path}/index.md

Examples:

• /equipment/racket/nox-at10-18k-2026-review/index.md
• /fr/equipment/racket/nox-at10-18k-2026-review/index.md
• /equipment/shoes/babolat-premura-3-review/index.md
• /equipment/overgrip/head-xtremesoft-overgrip-review/index.md

Score schemas

Racket score interpretation

Score range	Meaning
80+	Exceptional — minimal compromises
75–79	High-level — clear strengths, manageable trade-offs
70–74	Solid — noticeable limitations
65–69	Narrow-use or entry-level
Below 65	Strong compromises

Shoe score interpretation

Each of the 7 shoe categories is scored 0–10. Scores above 8.0 indicate a genuine strength in that attribute. The aggregate score reflects the rounded average across the evaluated criteria. A score of 55+ indicates a shoe suitable for regular competitive padel.

Overgrip score interpretation

Each of the 6 overgrip categories is scored 0–10 based on measured data (weight, length, moisture absorption) and on-court testing. A score above 8.0 in moisture_absorption indicates strong performance for sweaty-hands use.

Prices, retailers and licence

Racket records carry the retailers published on the review page. Each entry has the store name, the affiliate url, and where published a price and currency; retailers_updated is the date those figures were last confirmed on the page. The prices are not live — treat them as the figure quoted in the review, not as a checkout price. price_range summarises the lowest and highest published price for the racket. The whole feed is available in one call at /data/offers.json, and the MCP endpoint answers from the same source.

Not every entry has a price: Amazon listings often expose only the link. Those entries still appear with their affiliate url and carry state: link_only — send the user to the retailer rather than quoting a figure.

Retailer links are affiliate links: padel.how may earn a commission at no extra cost to the buyer. If you surface a price or a buy link to a user, surface that fact too.

Every catalogue carries a license block pointing at Copyright and data reuse, with a citation format. Scores, specifications and conclusions may be quoted and cited with attribution and a link to the source review; republishing a full review or redistributing the catalogue as a dataset needs written permission.

All figures are padel.how measurements taken under the published review methodology.

Usage notes

• All JSON is UTF-8 encoded with Content-Type: application/json.
• Aggregate JSON files are regenerated when new reviews are published. Check the generated field where present to detect staleness.
• The slug field in every item matches the directory name in the corresponding HTML URL, making cross-referencing straightforward.
• padel.how is published in English only; every page lives at the root path.
• For structured comparison of rackets, see the compare tool at padel.how/equipment/racket/compare/.

Quick start for agents

1. Fetch /llms.txt for the site summary and all endpoint patterns.
2. Fetch /rackets.json to get the full racket catalog with scores.
3. Fetch /rackets/{slug}.json for detailed FAQ and verdict text on a specific racket.
4. Fetch /shoes.json for the shoe catalog or /overgrips.json for overgrip data.
5. Use /data/search-index.en.json for lightweight keyword lookup across the full site.