# PlaceholderAPI

Nexo has an integration with PlaceholderAPI to let you use some parts throughout other plugins.\
**Glyphs** can be used via **%nexo\_glyphid%**, this will return the **\<glyph:glyphid>** for any Glyph not using the font *minecraft:default* in its config. If one does, the raw unicode is returned.

**%nexo\_shift\_X%** can be used to shift elements. This returns a unicode as Nexo adds it to every font.\
\
\&#xNAN;**%nexo\_pack\_hash%** returns the current hash of the Nexo ResourcePack

### PlaceholderAPI Tag

Nexo also adds a "PlaceholderAPI Tag". This can be used like most modern MiniMessage style tags.\
\&#xNAN;**\<placeholderapi:placeholder>** or **\<papi:placeholder>**. This will work in any plugin, much like the Nexo Glyph & Shift tags.

{% embed url="<https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FTAoAxayP9PrBtX9UQ5wa%2Fuploads%2FtOQPtql8QhpoYmhX2I1s%2Foutput.mp4?alt=media&token=549fa5c9-4a97-4ffb-922c-af1d0686d2f8>" %}


---

# Agent Instructions: 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://docs.nexomc.com/compatibility/placeholderapi.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.