> For the complete documentation index, see [llms.txt](https://developers.laws.africa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers.laws.africa/get-started/manage-your-plan.md).

# Manage your plan and subscription

Manage your Laws.Africa platform plan, subscription, usage and service access.

Use [platform.laws.africa](https://platform.laws.africa/) to manage the account settings that control what your API token can access.

The developer guide explains how to integrate with the APIs. The platform is where you manage your API token, active services, selected country, usage, plan and subscription requests.

## Check your current plan

Open [Plan & billing](https://platform.laws.africa/plan-billing/) to see:

* your current plan;
* your primary API country;
* your active services;
* your API rate limits;
* pending upgrade, downgrade or cancellation requests.

Use [Usage](https://platform.laws.africa/usage/) to monitor how many calls your account has made against your current limits.

## Primary API country

Your primary API country controls the default country-scoped services on self-service plans, including country-specific Knowledge Bases.

If your plan allows country changes, you can change your primary API country from [Plan & billing](https://platform.laws.africa/plan-billing/). Changing the country can change which country-specific services are active for your account.

## Change your plan

Plan changes are managed from [Plan & billing](https://platform.laws.africa/plan-billing/).

Depending on your current plan, you may be able to:

* request an upgrade to Build;
* contact Laws.Africa about Scale;
* request a downgrade;
* request cancellation.

Some changes are handled as requests rather than instant changes, especially where they affect countries, products, billing or commercial terms. Pending requests are shown on the Plan & billing page.

For current prices and commercial plan details, use [laws.africa/platform](https://laws.africa/platform/).

## Monitor usage and handle rate limits

API calls are counted against your account's active plan limits. Limits may apply per minute and per day, depending on the product family and your plan.

Open [Usage](https://platform.laws.africa/usage/) to check current usage.

### Knowledge Base response headers

Successful Knowledge Base retrieve responses and quota-related `429` responses include `RateLimit-Policy` and `RateLimit` headers for each finite quota window. These headers use the [IETF draft format](https://www.ietf.org/archive/id/draft-ietf-httpapi-ratelimit-headers-11.html). For example:

```http
RateLimit-Policy: "minute";q=30;w=60, "day";q=100;w=86400
RateLimit: "minute";r=24;t=18, "day";r=82;t=31018
```

* `q` is the configured request limit; `w` is the window length in seconds.
* `r` is the number of remaining requests, after counting the current successful request.
* `t` is the number of seconds until the window resets, rounded up.

Windows are fixed and aligned to UTC: minute windows reset at the start of each minute, hour windows at the start of each hour, and daily windows at midnight UTC. Only finite windows configured for your subscription are returned, in minute/hour/day order. If there are no finite limits, both headers are omitted.

Quotas are shared per user and product family across countries, Knowledge Bases and API keys. Legislation and judgments Knowledge Bases draw from the same Knowledge Base quota. Headers are advisory snapshots: concurrent requests can consume the remaining capacity before your next request.

A quota-related `429 Too Many Requests` response also includes `Retry-After`, in seconds:

```http
Retry-After: 31018
```

Wait at least that long before retrying. If several windows are exhausted, the delay covers the latest reset. Throttled attempts do not consume quota. Add jitter to retries to avoid synchronising requests, and handle another `429` if concurrent activity has consumed the available quota.

These quota headers apply to the retrieve endpoint; listing, detail, validation and permission responses do not include them. They are available to browser clients from permitted CORS origins.

### Client behaviour

Your application should handle `429 Too Many Requests` responses gracefully. For production integrations:

* log API response status codes;
* respect `Retry-After` when present, and use backoff with jitter otherwise;
* avoid tight retry loops;
* cache stable Content API responses where appropriate;
* monitor daily usage trends before launch;
* request an upgrade before sustained usage reaches your plan limits.

If usage looks unexpectedly high, check for repeated polling, unbounded loops, duplicate background jobs or repeated uncached requests.

## Related account tasks

* Manage API keys at <https://platform.laws.africa/api-keys/>.
* Review [developer entry points](https://platform.laws.africa/developer-resources/).
* When logged in, manage Content API webhooks at <https://platform.laws.africa/webhooks/>.


---

# 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://developers.laws.africa/get-started/manage-your-plan.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.
