> For the complete documentation index, see [llms.txt](https://apidocs.akinon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://apidocs.akinon.com/commerce-openapis/pretty-urls/introduction/query-behavior.md).

# Query Behavior

The endpoint follows a **two-phase resolution strategy**:

**Phase 1: Database Lookup**

* Searches stored URL mappings matching the provided path
* Returns paginated results with full routing metadata

**Phase 2: Dynamic Resolution (Fallback)**

* Activates when no stored mapping exists (count = 0). Analyzes the URL path through the routing engine
* Constructs a virtual mapping with view information, parameters, and query data
* Returns a single-item response representing the resolved route

This approach ensures **zero dead-ends**: every valid application URL can be resolved, whether pre-stored or dynamically discovered.


---

# 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://apidocs.akinon.com/commerce-openapis/pretty-urls/introduction/query-behavior.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.