> For the complete documentation index, see [llms.txt](https://waad-mawlood.gitbook.io/model-metadata/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://waad-mawlood.gitbook.io/model-metadata/readme.md).

# Introduction V3

Laravel Model Metadata is a package designed to manage metadata with JSON support for multiple data types. It allows you to attach, manage easily, and query metadata on your Laravel models using the `HasManyMetadata` or `HasOneMetadata` traits.

{% embed url="<https://github.com/waadmawlood/laravel-model-metadata>" %}
Metadata in Github
{% endembed %}

### Contributions

Contributions to this package are welcome. If you have ideas, suggestions, or issues, feel free to submit pull requests or open issues on the [GitHub repository](https://github.com/waadmawlood/laravel-model-metadata).

### Main Features

* Allow one model to **have many** metadata records
* Allow one model to **have one** metadata record
* Create, update, delete, and search metadata
* JSON casting using the package's built-in trait
* A polymorphic table design to attach metadata to any model


---

# 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://waad-mawlood.gitbook.io/model-metadata/readme.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.