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

# Anchorage

Anchorage is a SEP-10 authentication server for Stellar, written in Go.

SEP-10 is Stellar Web Authentication: a challenge-response protocol proving a user controls a Stellar account, without a password. The server issues an unsubmitted transaction, the client signs it, the server verifies the signatures and returns a JWT.

It is the prerequisite layer beneath SEP-6, SEP-24, and SEP-31. Every anchor, wallet backend, and on/off-ramp on Stellar depends on it.

Reference server implementations exist in Python (django-polaris), PHP (Argo Navis SDK), and Java (SDF's Anchor Platform). Go — the language of Horizon, stellar-rpc, and SDF's own SDK — has the protocol primitives and no server around them.

**Scope Boundary:** This is the authentication layer only. It is not an anchor, not KYC, and not deposit and withdrawal. Those systems are built on top of it.

## Next steps

* [What SEP-10 is](/anchorage-docs/concepts.md)
* [Architecture](/anchorage-docs/architecture.md)
* [Deployment](/anchorage-docs/deployment.md)
* [Anchorage GitHub Repository](https://github.com/0dillon/Anchorage)


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://dillon-2.gitbook.io/anchorage-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 `build a script that syncs our docs to a CMS` 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.