> For the complete documentation index, see [llms.txt](https://wiki.playgama.com/playgama/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.playgama.com/playgama/bridge-sdk/saas/leaderboards.md).

# Leaderboards

SaaS leaderboards provide a shared leaderboard service for platforms that do not have their own suitable leaderboard API.

To enable SaaS leaderboards, use the [config editor](https://playgama.github.io/bridge-config-editor/) to add your SaaS token and list the platforms where the service should be active. No game-code changes are required: Bridge loads the SaaS leaderboard adapter automatically.

{% code title="playgama-bridge-config.json" %}

```json
{
  ...
  "saas": {
     "publicToken": "<YOUR_APP_PUBLIC_TOKEN>",
     "leaderboards": {
       "platforms": ["playgama", "qa_tool"]
     }
  },
  ...
}
```

{% endcode %}

Create the SaaS leaderboard in your game's card in the [developer dashboard](https://developer.playgama.com/), on the **Leaderboards** tab — the same place where you get the public token.

In the root `leaderboards` section, only the game-facing ID is required. Add it in the config editor:

{% code title="playgama-bridge-config.json" %}

```json
{
  ...
  "leaderboards": [
    {
      "id": "top_score"
    }
  ],
  ...
}
```

{% endcode %}


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://wiki.playgama.com/playgama/bridge-sdk/saas/leaderboards.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.