> For the complete documentation index, see [llms.txt](https://docs.sportmonks.com/v3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportmonks.com/v3/sportmonks-ai-docs/llm-tools.md).

# LLM Tools

Setup guides for using Sportmonks data with every major AI tool and LLM. Pick the one you use.

| Tool           | Integration type            | What you get                                               |
| -------------- | --------------------------- | ---------------------------------------------------------- |
| ChatGPT        | Custom GPT via GPT Actions  | A no-code Sportmonks assistant anyone can use from ChatGPT |
| GitHub Copilot | Workspace instructions file | Copilot writes accurate Sportmonks code without prompting  |
| Windsurf       | MCP server for Cascade      | Live API access inside Windsurf's AI agent                 |

Looking for Claude or Cursor? Those are covered in the MCP Server section - they use the same server.

Not sure which option fits you? If you write code, start with the tool you already use daily. If you want a no-code assistant to query live football data, go with ChatGPT.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.sportmonks.com/v3/sportmonks-ai-docs/llm-tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.