Golf data for developers

Golf course data,
without the legwork.

Build course discovery into your app, website or AI agent. A structured UK catalogue, a straightforward REST API, and an MCP connection that speaks the same language.

Get started Explore Course Data

Scoped accessREST & MCPSource-aware data

Find your next coursev1

curl --get "$COURSE_DATA_API_BASE/v1/courses" \
  -H "Authorization: Bearer $COURSE_DATA_KEY" \
  --data-urlencode "courseName=St Andrews" \
  --data-urlencode "countryCode=GB" \
  --data-urlencode "limit=10"

const url = new URL("/v1/courses", apiBase);
url.searchParams.set("courseName", "St Andrews");

const response = await fetch(url, {
  headers: { Authorization: `Bearer ${apiKey}` }
});

{
  "name": "search_courses",
  "arguments": {
    "courseName": "St Andrews",
    "countryCode": "GB", "limit": 10
  }
}

One catalogue. Two ways in.Search course names · Explore layouts · Keep source context

UK firstGrowing course catalogue

REST APIPredictable JSON contracts

MCP nativeConnect your AI tools

Traceable sourcesAvailability made explicit

One useful foundation

Less time collecting data.
More time building.

Start with course discovery. Go deeper where the catalogue has the evidence your product needs.

Course & club discovery

Search names, browse the catalogue, find nearby clubs and follow stable identities across your product.

Explore course search

Layouts & scorecards

Discover available layouts, tees and hole-level scoring data. Readiness tells you when a record can support scoring.

Understand scoring data

Geometry with context

Explore source-backed geometry with explicit readiness. Current observations are unvalidated and unsuitable for distance guidance.

Read the geometry guide

Clear data availability

Missing values, source evidence and rights status stay visible. Your app can handle uncertainty deliberately.

Explore the data model

Help the catalogue grow

Authorised contributors can submit evidence-backed changes through a private proposal and review workflow.

How enrichment works

Built for developers

Code you can copy, documented errors, scoped credentials and the same catalogue through REST and MCP.

Open the documentation

Canonical API: https://api.teem.golf. MCP: https://api.teem.golf/mcp. Production endpoint activation and acceptance are pending. Development testing uses a separate approved environment.

A short path to your first request

Create an account. Start building.

Create your account, request access, then connect your integration to the available course data.

01 / ACCOUNT

Create your Teem account

Enter the shared Teem account flow to create your account or sign in. Then continue to your Course Data workspace.

Get started

02 / CONNECT

Set up your access

Complete onboarding and request developer preview access. Once approved, create a scoped key and keep it on your server.

Authentication guide

03 / BUILD

Make your first request

Search the catalogue, fetch a course, and check which capabilities are available for that record.

Follow the quick start

Bring your agents along

The same course data.
A conversation away.

Connect an MCP-compatible client to search courses, inspect available data and prepare enrichment proposals with permission-aware tools.

Connect with MCP

MCP · tool callsearch_courses

{
  "name": "search_courses",
  "arguments": {
    "courseName": "St Andrews",
    "countryCode": "GB",
    "limit": 10
  }
}

Coverage that tells you more

UK first.
Evidence at every step.

A broad imported starting point for discovery, with deeper data made available as it is reviewed and cleared for use.

Coverage is a count of source records, not a promise that every course has a complete scorecard. Check readiness before using a record for scoring or maps.

See the coverage guide

Catalogue snapshotChecked 1 Oct 2026

2,975imported UK source records in the catalogue

United KingdomPreview

Nation classificationIn progress

EuropePlanned

Availability varies by record and capability. Source attribution travels with the data.

Simple launch plans

Start free.
Build at your pace.

One catalogue, four ways to grow. Choose the monthly allowance that fits your product.

Free

Explore the catalogue and try your first integration.

£0 / month

200 requests per month

Course & club discovery
REST API and MCP access
Scoped project credentials
Available source & data context
Developer documentation

Get started

Starter

Give a small project a useful data foundation.

£9.99 / month

5,000 requests per month

Course & club discovery
REST API and MCP access
Scoped project credentials
Available source & data context
Developer documentation

Request Starter access

FOR GROWING PRODUCTS

Pro

More room for a growing golf product.

£29.99 / month

25,000 requests per month

Course & club discovery
REST API and MCP access
Scoped project credentials
Available source & data context
Developer documentation

Request Pro access

Business

For established products with higher request volumes.

£99.99 / month

100,000 requests per month

Course & club discovery
REST API and MCP access
Scoped project credentials
Available source & data context
Developer documentation

Request Business access

Launch pricing in GBP. Create your account through the shared Teem flow, then request access in your dashboard. Developer preview access requires approval; paid checkout is not yet active. Need a larger allowance? Talk to Teem.

A few useful answers

Before you build.

Get the essentials here, then go deeper in the developer guides.

Browse the documentation

What can I build with Course Data?

Course discovery, location-based browsing and agent-assisted research are natural starting points. Scorecards and mapping depend on record-level readiness and the permissions attached to the source data.

Does every course have a scorecard?

No. Imported records can support discovery without having a reviewed layout or complete scoring data. The API makes missing information and readiness explicit so you can build a useful fallback.

Can I connect an AI agent?

Yes. Use the MCP endpoint with an authorised scoped key or the supported OAuth connection. Read tools and contribution tools have different permissions. Ordinary contributions go to a reviewer; publisher permissions are separate.

Where does the data come from?

The baseline catalogue uses OpenGolfAPI and OpenStreetMap-derived records. Additional facts need their own evidence and rights assessment. The source and data guide explains attribution and what is available.

What happens when I reach a limit?

The service returns a documented 429 response. Check retry guidance and your usage window rather than retrying continuously. Your dashboard shows the allowance for your account.

Make your next idea playable.

Explore the catalogue. Find your starting point.