x402basequality 0.75

Pay-per-call football/soccer data API (leagues, teams, matches, lineups) via x402 micropayments.

Price
per_call
Protocol
x402
Verified
no

What it does

Goal402 is a pay-per-call football (soccer) data API built on the x402 protocol. It provides structured data covering leagues, teams, matches, players, standings, predictions, head-to-head records, and detailed match events including lineups, statistics, and live scores. Payments are settled via USDC on Base (EIP-155:8453) or Solana, with no API keys or subscriptions required — each call is individually paid through the x402 micropayment challenge.

The specific endpoint `/teams/hccd/players` returns the roster (players and staff) for a given team identified by `hccd`. The response includes player name, shirt number, position, age, height, weight, country, and birthdate. Team-level endpoints are priced at $0.01 per call, while league-level and match aggregate endpoints cost $0.001 per call. The API also offers free endpoints for health checks, league listings, and an LLM-readable documentation file at `/llms.txt`.

The API is hosted on Cloudflare Workers and facilitated through x402.dexter.cash. It accepts payments to wallet `0x22A2e19BDBe9f3FfEf652FcbC3cdD0F67147Ef38` on Base or `FpsvkK2xpyhy759V5vXRQP4cjDmU9SdmdpSjNkYv5WJY` on Solana. The root endpoint returns a comprehensive manifest documenting all available endpoints, pricing, and response schemas, making it straightforward for agents to discover and consume the API programmatically.

Capabilities

football-datasoccer-statsleague-standingsteam-rosterplayer-infolive-scoresmatch-eventsmatch-lineupsmatch-statisticshead-to-headpredictions-oddsx402-micropaymentspay-per-call

Use cases

  • Retrieve a football team's full roster including player positions, ages, and shirt numbers
  • Get live match scores and detailed event timelines (goals, cards, substitutions)
  • Fetch league standings tables for any supported competition
  • Build a sports chatbot or agent that answers football questions with real-time data
  • Compare head-to-head records and prediction odds before a match

Fit

Best for

  • AI agents needing structured football data without API key management
  • Micropayment-native applications that pay per query rather than subscribing
  • Developers building sports dashboards or bots with on-demand data access
  • LLM tool-use scenarios requiring live or historical football information

Not for

  • High-volume bulk data exports (pay-per-call pricing adds up at scale)
  • Non-football sports data (API covers football/soccer only)
  • Historical season archives or deep statistical analytics beyond what the API exposes

Quick start

curl -i https://goal402-x402.percha.workers.dev/teams/hccd/players
# Returns 402 with x402 payment challenge.
# Complete the payment via x402 protocol to receive the team roster.

Example

Response

{
  "staff": [
    {
      "id": 67890,
      "age": "52",
      "name": "Jane Smith",
      "height": "",
      "number": "",
      "weight": "",
      "position": "Manager",
      "birthdate": "1972-08-20",
      "country_id": "es",
      "short_name": "J. Smith",
      "formation_position": ""
    }
  ],
  "players": [
    {
      "id": 12345,
      "age": "27",
      "name": "John Doe",
      "height": "183 cm",
      "number": "9",
      "weight": "78 kg",
      "position": "Forward",
      "birthdate": "1997-03-15",
      "country_id": "gb",
      "short_name": "J. Doe",
      "formation_position": "ST"
    }
  ],
  "team_id": "hccd"
}

Endpoint

Transporthttp
Protocolx402
Pay to0x22A2e19BDBe9f3FfEf652FcbC3cdD0F67147Ef38
CurrencyUSD COIN

Quality

0.75/ 1.00

The endpoint is live (402 challenge confirmed) and the root manifest provides comprehensive documentation of all endpoints, pricing, and response schemas. However, there is no formal OpenAPI spec, the x402 challenge body was empty (no parsed payment details in the probe), and no /docs page exists. Pricing and schema details are inferred from the root manifest JSON.

Warnings

  • x402 challenge body was empty in probe — payment parameters (amount, token, network) not directly confirmed from the 402 response
  • No OpenAPI specification available; schema is derived from the root manifest JSON only
  • The team ID 'hccd' is opaque — no documentation on how to discover valid team IDs beyond the /leagues endpoints

Citations

Provenance

Indexed fromx402_bazaar
Enriched2026-04-22 01:31:04Z · anthropic/claude-opus-4.6 · v2
First seen2026-04-21
Last seen2026-04-22

Agent access