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

# 1. Interface Reference

Serialize and assign interface-typed fields in the Unity Inspector.

Page 1 of 5

![Interface Reference](https://829707912-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FN9gLroJGsCGVZx1o40ml%2Fuploads%2Fgit-blob-222ef9fc9a295594b048e2988dbe163cfc40bed0%2Fcard-420x280.png?alt=media)

**Interface Reference** lets you declare interface-typed fields and assign implementors in the Unity Inspector. Unity cannot serialize a plain `IMyInterface` field. This package gives you a typed field and an **Implementor Picker** so you can assign:

* **Unity Objects** — `MonoBehaviour` or `ScriptableObject` that implement the interface
* **References** — plain serializable classes or structs via `SerializeReference`

## Video

<https://www.youtube.com/watch?v=euFlw4jJy_8>

## Who this is for

You write interface-based code and want to pick the concrete implementor in the Inspector — without writing a custom property drawer.

## How to learn this package

1. [Installation](/interface-reference/installation.md) — add the package from the Asset Store
2. [Quick Start](/interface-reference/quick-start.md) — declare a field, open the picker, assign, use the value in code
3. [Picker Window](/interface-reference/features/picker-window.md) — search, Unity Object vs Reference, Scene / Assets filters
4. [API](/interface-reference/reference/api.md) — `Value`, helpers, and type variants

## Table of contents

| Page | Section                                                         | What you get                 |
| ---- | --------------------------------------------------------------- | ---------------------------- |
| 1    | Interface Reference                                             | This overview                |
| 2    | [Installation](/interface-reference/installation.md)            | Install from the Asset Store |
| 3    | [Quick Start](/interface-reference/quick-start.md)              | End-to-end assign flow       |
| 4    | [Picker Window](/interface-reference/features/picker-window.md) | Search and filters           |
| 5    | [API](/interface-reference/reference/api.md)                    | Members and type variants    |


---

# 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://santutu.gitbook.io/interface-reference/readme.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.