Skip to main content
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.
If you were looking for skills.md, Socket exposes this file as skill.md.
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.
curl https://docs.socket.tech/skill.md
  1. Load skill.md to understand the Socket capability surface.
  2. Load llms.txt to find the most relevant integration pages.
  3. Fetch the specific pages your task needs, usually the Socket API guide, deposit addresses, or chain-specific integration guides.
  4. Use 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 when your agent needs quotes, transaction data, and execution status.
  • Use 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 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:

​
Using skills-compatible tooling

If your agent supports the Skills CLI, you can add Socket directly from the docs domain: 
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.