> 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/pricing.md).

# Pricing and plans

Laws.Africa Legal Knowledge Platform plans are designed to support a path from free experimentation to production and multi-country integrations.

{% hint style="info" %}
Prices and limits can change. Use this page for developer guidance, and check <https://laws.africa/platform/> for current pricing before making a purchasing decision.
{% endhint %}

## Plan summary

### Sandbox

Sandbox is for prototyping and experimentation. It is free and includes one country, legislation and judgments Knowledge Bases, free access to the Cape Town by-laws Content API, and 100 calls per day.

### Build

Build is for production Knowledge Base workflows in one country. It starts at ZAR 4,200 per Knowledge Base per month and includes legislation and judgments Knowledge Bases, free access to the Cape Town by-laws Content API, and 3,000 calls per day.

### Scale

Scale is for multiple countries, higher usage and deeper integrations. It starts at ZAR 6,700 per Knowledge Base per country per month and includes legislation and judgments Knowledge Bases, 10,000 calls per day, and optional full Legislation Content API access starting at ZAR 42,000 per country per month, billed annually.

### Enterprise

Enterprise is for custom requirements, custom support and custom call limits. It supports multiple countries and content types, legislation and judgments Knowledge Bases, and optional full Legislation Content API access. Pricing is custom.

Prices exclude VAT.

## Knowledge Bases

Knowledge Bases are available on all plans.

Use Knowledge Bases for AI grounding, RAG, legal agents, semantic search and workflow tools.

## Content API

Content API access depends on the plan.

All plans include free access to the Cape Town by-laws Content API, so that you can experiment, discover how the API works, and determine if it will be useful for your application.

Use the Content API when your product needs full legislation collections inside your own systems, structured formats, historical versions, lifecycle metadata or content update webhooks.

## Choosing a plan

Start with **Sandbox** when you are evaluating results, testing prompts or building a prototype.

Move to **Build** when you need production Knowledge Base access for one country.

Move to **Scale** when you need multiple countries, higher call limits or full Content API access.

Use **Enterprise** when you need custom countries, custom call limits, support or commercial terms.

## What happens when you hit limits?

Limits protect shared infrastructure. If an application reaches its minute or daily call limit, upgrade to a plan with higher usage or contact Laws.Africa for custom limits.

Monitor current usage at <https://platform.laws.africa/usage/> and see [manage your plan and subscription](/get-started/manage-your-plan.md) for rate-limit handling guidance.

## Where to sign up

* Start or manage access at <https://platform.laws.africa/>.
* Manage your plan and subscription at <https://platform.laws.africa/plan-billing/>.
* Review current pricing at <https://laws.africa/platform/>.


---

# 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:

```
GET https://developers.laws.africa/get-started/pricing.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.