> For the complete documentation index, see [llms.txt](https://docs.legitimate.tech/public-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.legitimate.tech/public-docs/welcome-to-legitimate.md). # Welcome to Legitimate ## What is Legitimate? Legitimate connects your physical product to digital experiences that extend your customers’ relationship with your brand. We provide an all-in-one solution for connected products including NFC tags, customized digital experiences, user accounts and ownership tracking, and analytics data.
Getting Started with Legitimatesocial banner.pngBroken link
Legitimate Tags
with NFC Technology		Tags-Window.pngTag Catalog
Verify Digital ExperienceScreenshot 2024-09-23 at 12.47.01 PM.pngVerify Experience
Product Analytics and Engagement DataScreenshot 2024-07-20 at 4.58.12 PM-front.png
APIs for Custom ExperiencesUntitled.pngWeb/HTML Implementation
Digital Product PassportIMG_1470-portrait.pngProtocol
Tag Management DashboardScreenshot 2024-07-20 at 4.57.14 PM-front.png
Tag Programmer
for macOS and Windows		image.pngProgram Tags with the Desktop Programmer
Tag Programmer
for iOS and Android		IMG_1451 2-portrait.pngProgram Tags with the Mobile Tag Programmer
--- # 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 following URL with the `ask` and `goal` query parameters: ``` GET https://docs.legitimate.tech/public-docs/welcome-to-legitimate.md?ask=&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 `build a script that syncs our docs to a CMS` 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.