> For the complete documentation index, see [llms.txt](https://docs.ingestlabs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ingestlabs.com/tag-manager/providers/provider-version.md).
# Provider Version
## Overview
Every **Provider** includes a version number on the top-right corner of the screen. Once the Provider is published, the Version is set to 1. That is **Version 1**.
## Version Number Location
After subsequent edits and only after publishing, the version number keeps on updating to the latest version such as Version 2, version 3, and so on.
## Versioning Logic
When a new **Provider** is created and published for the first time, it is assigned **Version 1**.\
Every time the Provider is edited and then published again, the version number is incremented:\
Example: **Version 2**, **Version 3**, and so on.
**Note 1:** For the default Providers, the version is always set to “1” because these are populated from the template.\
**Note 2:** Until the Provider is published, the status displays **Pending Publish**. Once the Provider is published in the staging or production environment, the status updates accordingly on the Providers screen.
{% embed url="" %}
---
# 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://docs.ingestlabs.com/tag-manager/providers/provider-version.md?ask=&goal=
```
`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.