> For the complete documentation index, see [llms.txt](https://docs.oisy.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.oisy.com/for-developers/how-to-connect-with-oisy.md).

# How to "Connect with OISY"

## Connect with OISY to your app

For the OISY Wallet integration, here are a few options to explore:

* For React frontends, the [IdentityKit](https://nfid-identity-kit.webflow.io/) ([npm](https://www.npmjs.com/package/@nfid/identitykit), [documentation](https://qzjsg-qiaaa-aaaam-acupa-cai.icp0.io/docs)) and related [demo](https://qzjsg-qiaaa-aaaam-acupa-cai.icp0.io/demo) would be a great place to start. It’s like a WalletConnect for the Internet Computer.
* For Typescript, take a look at [@icp-sdk/signer](https://www.npmjs.com/package/@icp-sdk/signer) (which is the underlying library for IdentityKit).
  * Note: This library used to be at [@slide-computer/signer](https://www.npmjs.com/package/@slide-computer/signer) and was moved to the new repo under direct Dfinity maintenance early 2026
* We also provide a reference implementation, [@dfinity/oisy-wallet-signer](https://www.npmjs.com/package/@dfinity/oisy-wallet-signer). Its features are more opinionated and limited to transfers or approvals with ICP or ICRC ledgers, so for a more general-purpose solution, the above two options might be a better fit.
  * Demo app is here: <https://shsda-3aaaa-aaaal-amg6q-cai.icp0.io/> (link is also available in the github repo)

**Note**: OISY implements a default handler for `icrc2_approve` and `icrc2_transfer_from` messages and can display a consent message for these two methods in case the ledger does not implement the ICRC-21 standard.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.oisy.com/for-developers/how-to-connect-with-oisy.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
