> ## Documentation Index
> Fetch the complete documentation index at: https://docs.socket.tech/llms.txt
> Use this file to discover all available pages before exploring further.

# For Agents

> Use Socket docs, APIs, and machine-readable resources from coding agents and other LLM-powered tools.

Socket is a unified routing layer for asset movement: agents can quote routes, execute swaps or bridges, create deposit addresses, and monitor completion from one API.

Start with the machine-readable docs when your agent needs to plan, select tools, or ground itself before implementation.

<Note>
  If you were looking for `skills.md`, Socket exposes this file as [`skill.md`](https://docs.socket.tech/skill.md).
</Note>

<Tabs>
  <Tab title="skill.md" icon="tools">
    **Best for agent planning and tool selection.** A structured capability summary of what Socket can do, what inputs it needs, and what constraints apply. Start here.

    ```bash theme={null}
    curl https://docs.socket.tech/skill.md
    ```
  </Tab>

  <Tab title="llms.txt" icon="list-tree">
    **Best for fast discovery.** A map of documentation pages and descriptions. Use this to find the right page before loading full docs.

    ```bash theme={null}
    curl https://docs.socket.tech/llms.txt
    ```
  </Tab>

  <Tab title="llms-full.txt" icon="file-lines">
    **Best for single-shot grounding.** The entire docs site combined into one text file for broad context in a single fetch.

    ```bash theme={null}
    curl https://docs.socket.tech/llms-full.txt
    ```
  </Tab>
</Tabs>

## Recommended order

1. Load [`skill.md`](https://docs.socket.tech/skill.md) to understand the Socket capability surface.
2. Load [`llms.txt`](https://docs.socket.tech/llms.txt) to find the most relevant integration pages.
3. Fetch the specific pages your task needs, usually the [Socket API guide](/integrate/integration-guides/socket-api), [deposit addresses](/integrate/integration-guides/deposit-addresses), or chain-specific integration guides.
4. Use [`llms-full.txt`](https://docs.socket.tech/llms-full.txt) when your tool can handle the larger context window and needs broad grounding.

## Build with Socket

Agents that can write code or operate wallets should treat the docs as implementation context, then use the API guides for exact request shapes:

* Use the [Socket API guide](/integrate/integration-guides/socket-api) when your agent needs quotes, transaction data, and execution status.
* Use [deposit addresses](/integrate/integration-guides/deposit-addresses) when your agent needs a user to send funds from a wallet, exchange, or non-EVM chain without signing a transaction in the same flow.
* Use [Get API Access](/integrate/get-api-access) before production traffic or higher limits.

## Migrate an existing integration

If you are updating an existing codebase, load the relevant migration guide and paste the LLM prompt at the top of the page into your agent:

* [Bungee API → Socket Swap V3](/integrate/migration-guide) — migrating from `dedicated-backend.bungee.exchange`
* [Socket API v2 → Socket Swap V3](/integrate/migration-guide-v2) — migrating from `api.socket.tech/v2`

## Using skills-compatible tooling

If your agent supports the Skills CLI, you can add Socket directly from the docs domain:

```bash theme={null}
npx skills add https://docs.socket.tech
```

After that, use the regular integration guides for implementation details and keep fetched docs scoped to the task your agent is performing.