Skip to main content

Sitemap

The Sitemap feature lets you define your application's navigation structure so the AI assistant can understand where users are and help them navigate. Each sitemap entry maps a URL pattern to a display name and optional placeholder resolvers.

Why Sitemap?​

Without a sitemap, the AI doesn't know your application's page structure:

User: "Take me to the premium package"
AI: "I don't have information about your application's pages."

With a sitemap configured:

Sitemap entry: /products/{productId}/details → "Product Details"
Placeholder resolver: productId → search_products tool

User: "Take me to the premium package"
AI: *calls search_products("premium package")* → navigates to /products/abc-123/details

Accessing the Sitemap​

The Sitemap is configured per assistant. Navigate to:

Assistants → Select an assistant → Settings → Sitemap tab

Sitemap List

Sitemap Entries​

Each sitemap entry defines a page in your application.

ColumnDescription
NameDisplay name for the page
Path PatternURL pattern with optional {placeholders}
DescriptionWhat this page is for
StatusActive/Inactive toggle
ResolversShows "Configured", "Needs Setup", or no placeholders
ActionsConfigure Resolvers, Edit, Delete

Filtering​

  • Search — Filter by name, path, or description
  • Category — Filter by category (e.g., "products", "admin")
  • Status — Filter by Active/Inactive

Creating a Sitemap Entry​

Click Add Entry to create a new sitemap entry.

Create Sitemap Entry

FieldDescriptionRequired
Path PatternURL pattern (e.g., /products/{productId}/details)Yes
Display NameHuman-readable page name (e.g., "Product Details")Yes
DescriptionExplains the page to the AINo
CategoryGrouping label (e.g., "products")No

Path Patterns​

Use {placeholder} syntax for dynamic URL segments:

/products                         # Static path - Products list
/products/{productId}             # Single placeholder - Product page
/products/{productId}/details     # Placeholder in middle
/orders/{orderId}/items/{itemId}  # Multiple placeholders

Auto-Parent Detection​

When you create an entry, Diosc automatically detects its parent based on the path prefix. For example:

  • /products/{productId} is automatically linked as a child of /products

The detected parent is shown in an info box before you save.

Placeholder Resolvers​

When a path pattern contains {placeholders}, you need to configure resolvers that tell the AI how to convert user queries into actual IDs.

Click Configure Resolvers (or the dropdown menu → Configure Resolvers) on any entry with placeholders.

Configure Resolvers

For each placeholder, configure:

SettingDescriptionRequired
DescriptionWhat this placeholder represents (e.g., "Product ID")No
MCP ToolThe tool to call for resolving (e.g., search_products)Yes
Input ParameterWhich tool parameter receives the user's queryYes
Output PathJSONPath to extract the ID from the tool response (e.g., results[0].id)Yes
Search HintGuidance for the AI on how to searchNo
Example QueriesSample search terms to help the AINo

How Resolvers Work​

  1. User says: "Show me the premium package"
  2. AI identifies the sitemap entry /products/{productId}/details
  3. AI calls the configured MCP tool (e.g., search_products) with the user's query
  4. AI extracts the ID from the response using the output path
  5. AI navigates the user to /products/abc-123/details

Resolver Status​

In the sitemap table, each entry shows its resolver status:

  • Configured (green badge) — All placeholders have resolvers configured
  • Needs Setup (amber badge) — Some placeholders are missing resolver configuration
  • No badge — Path has no placeholders (static path)

Hierarchy​

Sitemap entries support parent-child relationships:

/products                           → Products (parent)
  /products/{productId}             → Product Detail (child)
    /products/{productId}/details   → Product Details (grandchild)
/orders                             → Orders (parent)
  /orders/{orderId}                 → Order Detail (child)

Benefits:

  • Organized structure that the AI can understand
  • Parent paths auto-detected based on path prefixes

Sort Order​

Each entry has a Sort Order field to control display ordering within the same level of the hierarchy.

Editing and Deleting​

Editing​

Click Edit from the dropdown menu to modify a sitemap entry. You can change:

  • Path pattern
  • Display name
  • Description
  • Category

Parent detection is re-evaluated when the path pattern changes.

Deleting​

Click Delete from the dropdown menu. If the entry has children:

  • A Cascade Delete toggle appears
  • Enable it to delete the entry and all its children
  • Otherwise, only the selected entry is deleted
warning

Deleting a sitemap entry cannot be undone.

Best Practices​

Define Your Full Navigation​

Map all major pages in your application:

/dashboard                          → Dashboard
/products                           → Products
/products/{productId}               → Product Detail
/products/{productId}/edit          → Edit Product
/orders                             → Orders
/orders/{orderId}                   → Order Detail
/customers                          → Customers
/customers/{customerId}             → Customer Detail
/settings                           → Settings

Configure Resolvers for All Placeholders​

Every {placeholder} should have a resolver configured so the AI can navigate users to specific pages. Without resolvers, the AI can only navigate to static paths.

Use Descriptive Names​

Good descriptions help the AI understand what each page is for:

Path: /orders/{orderId}
Name: Order Detail
Description: Shows full order details including items, shipping status,
payment information, and customer details. Users can view and manage
individual orders from this page.

Organize with Categories​

Use categories to group related pages:

  • products — All product-related pages
  • orders — All order-related pages
  • admin — Administrative pages
  • reports — Reporting pages

Next Steps​