# Dynamic Link Generation

Dynamic Link Generation describes how integrators construct UAS links that execute deterministically at the moment of intent.

A UAS link encodes everything required for execution directly in the URL. There is no session state, no custody handoff, and no dependency on listings, approvals, or negotiated routing.

These links are portable and permissionless by design, allowing execution intent to originate from any surface — wallets, bots, launchpads, explorers, or external applications — while settling locally and natively on-chain.

***

#### What This Section Covers

The following pages describe how to correctly construct UAS links:

* Link Anatomy

  Understand the structure of a UAS link and how execution context is encoded.
* Required Parameters

  Learn which parameters must be present for execution to occur.
* [Optional Attribution Parameters (UTM)](/getting-started/integrating-uas/dynamic-link-generation/optional-attribution-parameters-utm.md)

  Add execution attribution without affecting routing, pricing, or access guarantees.
* Examples

  Copy-paste reference links for common integration surfaces.

***

#### Key Principles

* All execution context is encoded in the link
* No custody, no session state, no platform control
* Attribution is optional and informational only
* Execution behavior is deterministic and surface-agnostic

***

This section is the single source of truth for generating executable UAS links.

All surface-specific integrations should reference these pages rather than redefining link behavior elsewhere.


---

# 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.onchain.money/getting-started/integrating-uas/dynamic-link-generation.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.