> For the complete documentation index, see [llms.txt](https://praxxas.gitbook.io/killswitch/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://praxxas.gitbook.io/killswitch/technicals/protocol-integrations.md).

# Protocol Integrations

Protocols can benefit greatly leveraged using the services of KillSwitch.  Security implementations, no matter the potential inconvenience they carry, are hardly ever perceived as anything less than necessary.

* Custom monitoring/verification's can be stood up at the protocols request.  Such as:
  * Contract ownership protection - monitoring with parameters and auto-transferring ownership of contracts to prevent unwanted 3rd party access.
  * Unique functionality that requires monitoring and/or reactions.
    * For example a lending protocol that wants to ensure if a stablecoin depegs on-chain or off-chain, can auto lock deposits and borrowing minimizing the impact sustained by the protocol.
* Wallet interaction KS identification.  If your protocol would benefit from encouraging transacting wallets have KillSwitch active, we can provide that integration assistance.


---

# 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://praxxas.gitbook.io/killswitch/technicals/protocol-integrations.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.