> For the complete documentation index, see [llms.txt](https://mrcscripts.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mrcscripts.gitbook.io/docs/scripts/metermaid.md).

# Metermaid

NPC + player ticketing, wheel clamping, and dispute workflow for FiveM.

## MRC Metermaid

### Quick links

* [Install Instructions](/docs/scripts/metermaid/install-instructions.md)
* [Exports](/docs/scripts/metermaid/exports.md)

### What is MRC Metermaid?

MRC Metermaid is a ticketing and wheel-clamp system for NPC and player vehicles.

It’s built for police-style parking enforcement and citations.

### Main features

* Ticket or clamp vehicles.
* NPC infractions with visual signs (ex: handicapped / no-parking).
* Player-only infractions with predefined text + fine amounts.
* Optional custom notes when ticketing players.
* Ticket expiry flow.
  * Past expiry can trigger auto-clamping.
  * Tickets can be removed after a configured retention period.
* Dispute workflow.
  * Players can dispute a ticket.
  * Police can review disputes if their grade allows it.
* 3 UIs.
  * Ticket UI
  * PDA UI
  * Disputes UI

### Dependencies

* [community\_bridge](https://github.com/TheOrderFivem/community_bridge)

### TL;DR

* Use it for parking enforcement.
* Ticket or clamp cars.
* Review disputes inside the police menu.


---

# 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://mrcscripts.gitbook.io/docs/scripts/metermaid.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.