# Viper Execution

**Stealth execution infrastructure for Hyperliquid.**

Hyperliquid's orderbook is fully transparent. Every order, every cancel, every fill — recorded with your wallet address, visible to anyone running L4 data. Viper exists because trading meaningful size on a transparent DEX without execution infrastructure means broadcasting your intent to the entire market.

Six algorithms. Five trade monitor types. Automated position management. Real-time execution analytics. All built for one exchange, one problem: executing with stealth, cost control, and zero information leakage on the most transparent orderbook in crypto.

→ [Why Viper Exists](/why-viper/why-viper-exists.md)

***

## How It Works

You execute through algorithms that place passive limit orders, control your market footprint, and optimize for maker fills — instead of placing raw market orders that sweep the book and pay full taker fees. Trade monitors detect market conditions and trigger execution automatically. Execution baskets coordinate multiple algorithms across a price range in a single action — entries, exits, and stops launched together.

Everything runs on dedicated server infrastructure, not in your browser. Your funds never leave Hyperliquid.

→ [Execution Algorithms](/algorithms/overview.md)\
→ [Execution Baskets](/features/execution-baskets.md)\
→ [Trade Monitors](/features/trade-monitors.md)\
→ [Security Model](/under-the-hood/security.md)

***

## Get Started

Reach out, connect your wallet, and start trading. No forms, no waiting lists.

**Telegram:** [@ViperExecution](https://t.me/ViperExecution)\
**Email:** <support@viperexecution.com>

→ [Get Started](/getting-started/get-started.md)


---

# 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.viperexecution.com/readme.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.