# Minimum Inputs

The query field specifies the place to be matched. Each query must have non-blank values for at least one of the following combinations to get a Placekey:

* `query.street_address` + `query.city` + `query.region` + `query.postal_code` + `query.iso_country_code`
* `query.street_address` + `query.region` + `query.postal_code` + `query.iso_country_code`
* `query.street_address` + `query.city` + `query.region` + `query.iso_country_code`
* `query.latitude` + `query.longitude`

Include as much detail as possible in the query for the best match.

## How Inputs Affect the Response

An **address** is required to get a POI or address Placekey (the What\@Where format). When you include a `location_name`, the API matches it against known POIs at that address.

**Coordinates alone** return only the Where part of a Placekey (the H3 hexagon). This can also be computed locally using the [Python](/documentation/libraries/python.md) or [JavaScript](https://www.npmjs.com/package/@placekey/placekey) libraries without an API call.

When **both address and coordinates** are provided, the address drives the match. Including coordinates alongside an address is encouraged as it helps improve match quality.


---

# 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.placekey.io/documentation/placekey-api/input-parameters/minimum-inputs.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.