# Pathfinding

In the Lightning Network, a payer decides on the route they want their payment to take. Ideally they find a direct and cheap path quickly, but, in some cases, they might have to attempt multiple available routes with varying fees.

Nodes may employ different strategies for how to most efficiently find the most economical route to their destination quickly. In some implementations, nodes may outsource pathfinding to an external party.

Routes are onion encrypted, meaning only the sender sees the full route. All nodes along the route will only see what channel a payment is coming from and going to. The recipient does not learn the origin of the payment, only of its final hop.

{% content-ref url="/pages/P1F6Wv2GhEAxHlAeKzXi" %}
[Finding routes in the Lightning Network](/the-lightning-network/pathfinding/finding-routes-in-the-lightning-network.md)
{% endcontent-ref %}

{% content-ref url="/pages/fan1H0z8wv0KZH0b9Mwb" %}
[Channel Fees](/the-lightning-network/pathfinding/channel-fees.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MXpZnYg2Xxx\_jg24veU" %}
[Multipath Payments (MPP)](/the-lightning-network/pathfinding/multipath-payments-mpp.md)
{% endcontent-ref %}


---

# 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.lightning.engineering/the-lightning-network/pathfinding.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.