# Adding Metadata

You can optionally pass metadata. In this example we add the standard MAP keys `app` and `type` along with a geotag context with `geohash` and `context` fields to tag an inscription at a specific location.

```ts

// set fee rate
const satPerByteFee = 0.05

// inscription
const inscription =  { dataB64: fireShard,  contentType: "model/gltf-binary" }

// Define MAP keys as a JSON object
const metaData = { app: "ord-demo", type: "ord", context: "geohash", geohash: "dree547h7" }

const tx = createOrdinal(utxo, ordinalDestinationAddress, paymentPk, changeAddress, satPerByteFee, inscription, metaData);
```

`app` - is publicly shown in the tx. Should be the app or platform name making the inscription.

`context` = is a standard field making the tags apply to a particular type of identifier, in this case a `geohash`.

`geohash` - is a standard geohash string referring to a location.

both `createOrdinial` and `sendOrdinal` can optionally take metadata.

###


---

# 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://js.1satordinals.com/adding-metadata.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.