> For the complete documentation index, see [llms.txt](https://docs.1kosmos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.1kosmos.com/integrations/identity-verification/microsoft-entra-vid-partner/plans-and-pricing.md).
# Plans & pricing
Identity Verification by 1Kosmos is available through the Microsoft Security Store at pay-as-you-go pricing.
Enjoy a free trial for your first 100 transactions. This is ideal for validating the integration and user experience. Once you reach 101 transactions, standard pay-as-you-go pricing applies for that transaction and all subsequent transactions at $1.00 USD.
| Tier | Transactions | Price |
| ---------- | ------------ | ------------------------- |
| Free Trial | First 100 | $0.00 |
| Standard | 101+ | $1.00 USD per transaction |
For new customers who have requirements outside of what is available within the standard pay-as-you-go offer, 1Kosmos supports private plans at competitive pricing. [Reach out to a member of the 1Kosmos sales team for more information](https://www.1kosmos.com/talk-to-sales).
For existing customers, 1Kosmos supports the native Entra integration at no additional cost. Please reach out to your Customer Success manager.
---
# 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.1kosmos.com/integrations/identity-verification/microsoft-entra-vid-partner/plans-and-pricing.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 `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.
