> For the complete documentation index, see [llms.txt](https://docs.slingdata.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.slingdata.io/sling-platform.md).

# Sling Platform

- [Sling Platform](https://docs.slingdata.io/sling-platform/platform.md)
- [Architecture](https://docs.slingdata.io/sling-platform/platform/architecture.md)
- [Agents](https://docs.slingdata.io/sling-platform/platform/agents.md)
- [Connections](https://docs.slingdata.io/sling-platform/platform/connections.md)
- [Editor](https://docs.slingdata.io/sling-platform/platform/editor.md)
- [API](https://docs.slingdata.io/sling-platform/platform/api.md)
- [MCP Server](https://docs.slingdata.io/sling-platform/platform/mcp-server.md): Connect AI assistants to a Sling Platform project over MCP Streamable HTTP using a project token
- [AI Assistant](https://docs.slingdata.io/sling-platform/platform/ai-assistant.md): Chat with an AI assistant that reads and edits your Sling Platform project
- [Self-Hosting](https://docs.slingdata.io/sling-platform/platform/self-hosting.md): Deploy and manage Sling Platform in your own infrastructure
- [Kubernetes](https://docs.slingdata.io/sling-platform/platform/self-hosting/kubernetes.md): Deploy Sling Platform and agents on Kubernetes
- [High-Availability Agents](https://docs.slingdata.io/sling-platform/platform/self-hosting/shared-mode.md): Run many agent replicas on one key, with failover and platform-managed scaling
- [SSO & MFA](https://docs.slingdata.io/sling-platform/platform/self-hosting/sso-mfa.md): Configure OIDC single sign-on and TOTP multi-factor authentication
- [Deploy from CLI](https://docs.slingdata.io/sling-platform/platform/cli-usage.md)
- [Metrics & Logs](https://docs.slingdata.io/sling-platform/platform/metrics-logs.md)
- [Monitors](https://docs.slingdata.io/sling-platform/platform/monitors.md): Monitor your data for schema changes, freshness, anomalies, and column-level statistics
- [Structure](https://docs.slingdata.io/sling-platform/platform/monitors/structure.md): Complete YAML structure reference for Sling monitor configuration files
- [Object Metrics & Freshness](https://docs.slingdata.io/sling-platform/platform/monitors/object-metrics.md): Object-level monitoring metrics and data freshness tracking
- [Column Metrics & Validation](https://docs.slingdata.io/sling-platform/platform/monitors/column-metrics.md): Column-level statistics, validation rules, and value monitoring
- [Anomaly Detection](https://docs.slingdata.io/sling-platform/platform/monitors/anomaly-detection.md): Automatic z-score anomaly detection for data quality monitoring
- [Schema Changes](https://docs.slingdata.io/sling-platform/platform/monitors/schema-changes.md): Schema change detection for monitoring database structural drift


---

# 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.slingdata.io/sling-platform.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.