> For the complete documentation index, see [llms.txt](https://support.iafcertsearch.org/verifiers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.iafcertsearch.org/verifiers/getting-started/verification-rules/legacy-subscription-plans/verification-limit.md).

# Verification Limit

**Verification limit** refers to the maximum number of verification requests a user can make, which is determined by their subscription plan. It limits how many times a user can access verification information for certificates or certified entities.

Different subscription plans may offer varying verification limits, allowing users to choose a plan that best fits their verification needs.

<table><thead><tr><th width="190"></th><th>Certified Entity Profile Access</th><th>Certificate Verification</th></tr></thead><tbody><tr><td><strong>Free</strong></td><td>36 (3 / month)</td><td>36 (3 / month)</td></tr><tr><td><strong>Basic</strong></td><td>300 p.a.</td><td>240 p.a.</td></tr><tr><td><strong>Standard</strong></td><td>1,500 p.a.</td><td>1,200 p.a.</td></tr></tbody></table>

### **Handling Company Limits Upon Upgrade:** <a href="#handling-company-limits-upon-upgrade" id="handling-company-limits-upon-upgrade"></a>

The consumed verifications from the previous plan are deducted from the limits of the new plan.

When a user upgrades their subscription with existing verified companies:

> * **Current Consumed Verifications:** 100
> * **Upgrade Date:** January 2025
> * **New Plan Limit:** 1500 verifications
> * **New Available Verifications:** 1500 - 100 = 1400 remaining verifications
>   * 1400
>   * where the consumed company verification was deducted to the limits of the new plan.
>
> **Grace Period:**
>
> The grace period should reset upon upgrade, as the user has subscribed to a new subscription period.


---

# 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://support.iafcertsearch.org/verifiers/getting-started/verification-rules/legacy-subscription-plans/verification-limit.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.