What is DiscGolfAPI best for?

Disc golf apps and course finders that need worldwide course locations through a free REST API or MCP server with no key for public endpoints. Not ideal for: Projects needing scores, player stats or live data; it holds course location data only, and commercial use needs an enquiry.

How much does DiscGolfAPI cost?

DiscGolfAPI does not publish prices on the pages we checked.

Does DiscGolfAPI have a free tier?

Yes. DiscGolfAPI lists a free plan called "Public".

Does DiscGolfAPI have a WebSocket or streaming API?

No streaming is listed. DiscGolfAPI delivers data by REST, so you poll for updates.

Can I use DiscGolfAPI data commercially or for betting?

According to the public terms of DiscGolfAPI — commercial use: licence required; redistribution: not allowed.

Free / open data

DiscGolfAPI

Free public REST API and MCP server serving structured disc golf course data worldwide (search, nearby, filters) with JSON output and no API key needed for public endpoints.

Facts verified against the provider's site on 2026-11-03

Commercial use: Licence requiredBetting use: not disclosedToo little discussion

Visit official site Open API docs Compare

SportDex Score

#110 of 233 sports APIs

See the full ranking →

Popularity

Brand demand, developer discussions, GitHub repos and videos

Community & reliability

—

Tone of public discussions, liked vs criticised points, reliability complaints; not enough public discussion to judge.

Transparency

Public prices, docs, terms and coverage you can check before calling sales

Developer experience

Free access, docs, SDKs, OpenAPI, sandbox, realtime delivery, ecosystem

Computed from public data only; uptime and latency are not measured yet. Enterprise feeds that sell by contract score lower on transparency by design. How the score works

Starting price: Not public
Free access: Free tier
Sports: Not disclosed
Live data: No
Delivery: Polling only (REST)
Discussions: 0 threads
GitHub adoption: 4 repos

Best for

Disc golf apps and course finders that need worldwide course locations through a free REST API or MCP server with no key for public endpoints.

Course finder appsNearby-course searchTravel and map features

Not ideal for

Projects needing scores, player stats or live data; it holds course location data only, and commercial use needs an enquiry.

Limitations to check

− Course data only, no scores or stats
− Visible attribution required
− Republishing the full dataset as a competing service is barred
− Commercial use needs an enquiry

Written from the provider's own pages (source).

Last checked 2026-11-03

DiscGolfAPI at a glance

What is DiscGolfAPI best for?: Disc golf apps and course finders that need worldwide course locations through a free REST API or MCP server with no key for public endpoints. Not ideal for: Projects needing scores, player stats or live data; it holds course location data only, and commercial use needs an enquiry.
How much does DiscGolfAPI cost?: DiscGolfAPI does not publish prices on the pages we checked.
Does DiscGolfAPI have a free tier?: Yes. DiscGolfAPI lists a free plan called "Public".
Does DiscGolfAPI have a WebSocket or streaming API?: No streaming is listed. DiscGolfAPI delivers data by REST, so you poll for updates.
Can I use DiscGolfAPI data commercially or for betting?: According to the public terms of DiscGolfAPI — commercial use: licence required; redistribution: not allowed.
What do developers say about DiscGolfAPI?: A free, keyless disc golf course API with an MCP server. It appears only in API directories, agent-tool lists and one small student project, so adoption evidence is light and there is no user opinion on data quality or limits.

Commercial decision

Pricing & plan limits

Plan	Price	Requests	What's included
Public	Free	—	Free, no key for public endpoints; attribution requiredsource

Course location data only, no scores or stats; disc golf is not in the sports vocabulary so sports left empty. Attribution requirement is in the docs nav.

Before choosing a paid plan, confirm

• What counts as one request (per call, per market, per region?)

• What happens when you exceed the quota: blocked or billed

• Whether live and historical data are on your plan

• Whether your use (public app, betting, resale) is licensed

The critical question

Data coverage

Sports
Data types
Key competitions: Not disclosed
Competitions: Not disclosed
Live / in-play: No
Women's competitions: Not disclosed
Betting markets: Not disclosed
Bookmaker regions: Not disclosed
Bookmakers: Not disclosed
History depth: Not disclosed
Update frequency: Not disclosed
Name languages: Not disclosed
ID mapping: Not disclosed

Coverage often depends on the plan; confirm the exact league and season on your plan.

Before you build

Usage rights & access

Commercial use: Licence requiredsource
Betting products: Not disclosed
Redistribution: Not allowed
Storing data: Not disclosed
Attribution: Required
Logos & photos: Not disclosed
Who can buy: Individuals, Companiessource
Verification (KYC): Not required
Not available in: Not disclosed
Only available in: Not disclosed

Public API and JSON outputs can be used freely

Read the terms

Developer-ready evaluation

Integration & documentation

Protocols: REST
Formats: JSON
Authentication: none
SDKs: Not disclosed
OpenAPI spec: Not disclosed
Claimed latency: Not disclosed
Status page: Not disclosed
Sandbox / test keys: Not disclosed
Support: Not disclosed
SLA uptime: Not disclosed

Preview brief

# Integration brief: DiscGolfAPI

Goal: build a feature on DiscGolfAPI data. Use only the official documentation below as the source of truth.

## Known facts (from SportDex, verify before relying on them)
- Website: https://discgolfapi.com/docs/
- Docs: https://discgolfapi.com/docs/
- Sports: UNKNOWN — check the docs
- Data: UNKNOWN — check the docs
- Protocols: REST; formats: json
- Auth: none
- Free plan: Public
- Note: Course location data only, no scores or stats; disc golf is not in the sports vocabulary so sports left empty. Attribution requirement is in the docs nav.

## Verify before writing code
- live update frequency
- exact endpoint paths, parameters and response fields (read the official docs, do not guess)

## Implementation rules
- Keep the API key on the server (environment variable, backend route or edge function); never ship it to the browser.
- Cache responses and respect rate limits; count how many requests each screen triggers.
- Handle errors explicitly: invalid key, quota exceeded (429), missing fields, empty fixtures, timeouts.
- Start with one demo request and log the raw response before building UI on assumed field names.

Data quality signals

Data source & company

Official partners: Not disclosed
How data is collected: Not disclosed
Certifications: Not disclosed
Payment methods: Not disclosed
Minimum contract: Not disclosed
Country: Not disclosed
Founded: Not disclosed

Reddit · Hacker News · Stack Overflow · GitHub · YouTube

What developers say

Too little discussionfree tierdocs

A free, keyless disc golf course API with an MCP server. It appears only in API directories, agent-tool lists and one small student project, so adoption evidence is light and there is no user opinion on data quality or limits.

Praised for

No API key needed

Complaints

Nothing specific.

Our summary of public discussions, not a rating. Vendor posts are not counted as user opinion.

Open-source projects using it

Shortlist next steps

Alternatives worth comparing

No close match in the catalog yet.

Evidence & transparency

Official sources

Facts were extracted from the provider's own pages on 2026-11-03. Empty fields mean the provider does not say, not that the feature is missing. How we know