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

# Introduction to SeahorseFi.xyz

SeahorseFi aims to be the leading unstoppable permissionless lending and borrowing money market on DeFiChain EVM layer first before other cross-chain ambitions.

Any user who owns a non-custodial wallet that can connect to a decentralized application (Dapp) can use SeahorseFi without any restrictions provided that there is sufficient network gas on the chains SeahorseFi choose to deploy on.

Seahorse aim to simplify the user experience and provide core capabilities that enabled decentralized finance to flourish in a single application especially in the area of lending and borrowing.

SeahorseFi pays homage to leading money markets on other chains such as Venus, Compound and many more.

This document will be a living document and will continue to evolve across time.


---

# 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://seahorsefi.gitbook.io/seahorsefi/introduction/introduction-to-seahorsefi.xyz.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.