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

# Welcome

A non-custodial Solana smart-wallet for AI agents, spend caps, allowlists, audit trails by default

**Klink is a non-custodial Solana smart-wallet for AI agents.** It pairs an on-chain policy engine (caps, allowlists, expiry, deployed-fraction) with off-chain rich rules (URL allowlist, time-of-day windows) and treats Solana transaction history as the audit trail by default.

If you build agents that spend, this is the wallet between your agent and its money.

## Three actors, three blast radii

| Actor           | Holds                               | Authority                                                       | If credential leaks                                                                   |
| --------------- | ----------------------------------- | --------------------------------------------------------------- | ------------------------------------------------------------------------------------- |
| **Human owner** | Phantom keypair on-device           | Master, configures policy, funds wallet, can revoke any session | Total loss (same as any Solana wallet)                                                |
| **Backend**     | Session keypair (encrypted at rest) | Delegated, co-signs spend txs subject to on-chain policy        | Bounded by `daily_cap` × time-to-revoke; restricted by recipient + program allowlists |
| **Agent**       | Bearer API key                      | None on-chain, talks to the backend over HTTP                   | Zero direct on-chain risk                                                             |

The agent never crosses the trust boundary. The session keypair stays in the backend, never on the agent's machine. The owner key never leaves the human's device.

## What you'll find here

* [**Introduction**](/klink-docs/getting-started/what-is-klink.md): what Klink is, who it's for, why Solana
* [**Quickstart**](/klink-docs/getting-started/quickstart.md): sign in, create a vault, hand an agent a key, audit a spend
* [**Core Concepts**](/klink-docs/core-concepts/overview.md): Vault, Sessions, Policies, Budgets, Audit Trail, Yield
* [**Architecture**](/klink-docs/core-concepts/overview-1.md): the three-layer model with diagrams
* [**Developer Resources**](/klink-docs/developer-resources/sdk.md): SDK, CLI, and the agent skill
* [**Reference**](/klink-docs/reference/glossary.md): glossary, FAQ, security disclosures, roadmap

## Status

Klink is in **beta on Solana devnet**. The on-chain program enforces every policy described in these docs. The dashboard is live at [`app.klinkdotfun.live`](https://app.klinkdotfun.live), the HTTP API at `api.klinkdotfun.live`, and the agent skill at [skill.md](/klink-docs/developer-resources/skill.md). The SDK and CLI are on the way, see [Roadmap](/klink-docs/reference/roadmap.md). For mainnet readiness, see [Risks & Disclosures](/klink-docs/reference/risks.md).


---

# 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://klink-4.gitbook.io/klink-docs/readme.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.