> For the complete documentation index, see [llms.txt](https://lore.chainrunners.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lore.chainrunners.xyz/people-of-mega-city/gear-alpha-eddy.md).
# Gear Alpha Eddy
Eddy is a trustworthy gearhead that hustles between DVICE and Partswappers as a multi-district delivery manager.
Eddy has been in the game for ages, his pronounced augmented eyes have witnessed generations of Runners come and go through his network experiencing the highs and lows of the scene - making money, landing deals, failing hard.
His shops double as safe zones for Runners looking to move hot tech, get deals on cheap augment parts or just shoot the shit and boast about a recent successful take. He's got solid and reliable work if you prove you're useful, but nothing too risky. He's been long out of that scene for a while - too dangerous for his old bones .. but can be quite lucrative.
"I've worked with a lot of your 'type' before kid - and you can bet one thing that keeps them in my network is reliability."
---
# 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://lore.chainrunners.xyz/people-of-mega-city/gear-alpha-eddy.md?ask=&goal=
```
`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.