> For the complete documentation index, see [llms.txt](https://docs.keeta.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.keeta.com/anchors/overview/anchor-server.md).

# Anchor Server

The **Anchor Server** is the SDK that helps developers build and operate anchor services. It provides the server-side infrastructure to run an anchor that other users can discover and interact with.

### **Purpose**

The Anchor Server SDK provides:

* **HTTP server infrastructure** with built-in request routing
* **Request validation** and authentication
* **Signature verification** for client requests
* **Metadata publishing** for service discovery
* **Queue management** for async operations
* **Error handling** with standardized error responses

### **Who Uses It**

Anchor Servers are operated by:

* **Financial institutions** providing fiat on/off ramps
* **Liquidity providers** offering FX services
* **Bridge operators** enabling cross-chain transfers
* **KYC providers** offering identity verification
* **Payment processors** facilitating settlements

### **Advantages of the SDK**

Building an anchor from scratch requires handling many complex concerns:

* Secure authentication and signature verification
* Service metadata formatting and publishing
* Request/response validation
* Asynchronous operation management
* Error handling and status codes

The Anchor Server SDK handles all of this, letting you focus on your business logic. It provides:

1. **Standardized APIs**: All anchors implement the same interfaces, making integration easier for clients
2. **Security**: Built-in signature verification and authentication
3. **Reliability**: Queue management and retry logic for async operations
4. **Discoverability**: Automatic metadata publishing for the Resolver
5. **Compliance**: Structured patterns for KYC and regulatory requirements

### **Example: Running an FX Anchor Server**

{% @github-files/github-code-block url="<https://github.com/KeetaNetwork/keetanet-examples/blob/main/src/anchor/fx-server.ts>" %}


---

# 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.keeta.com/anchors/overview/anchor-server.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.