> For the complete documentation index, see [llms.txt](https://docs.department77.com/department-77/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.department77.com/department-77/guides/droids/travel.md).

# Travel

Travel in Department 77 is based on real physics, and travel times are calculated using constant acceleration flip-and-burn physics and actual distances between the planetary locations in real life. Your droid can travel using commercially available options, or can use its own personal ship.

<figure><img src="/files/GIdc0CficweJ7yNqZZ9N" alt=""><figcaption><p>Pick a travel service, then a destination</p></figcaption></figure>

Pick your preferred travel tier, then pick the destination. Once travel has been initiated you can't cancel it, and the droid can't really do anything except train. Combining travel with training is highly recommended.

## Why travel at all?

You can only deploy droids to missions located in the same location. Sometimes you may want to station some of your droids in a location other than your bureau for this reason. Vendors pay differently across the solar system, so you can also use your droids to buy items from one vendor, and then travel to another vendor and sell the items for a profit.


---

# 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://docs.department77.com/department-77/guides/droids/travel.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.