# How to connect OpenSea to OpenClaw (paste one key, 24 tools) > Connect OpenSea to OpenClaw with ClawLink: paste your OpenSea key once and 24 tools work from chat. No MCP server to run, nothing stored on your machine. Web version: https://claw-link.dev/openclaw/open-sea The usual route to OpenSea access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical OpenSea setup: install one ClawHub skill, connect OpenSea in the browser, and OpenClaw can call real OpenSea actions from any chat surface with no auth, token refresh, or tool wiring to build yourself. ## Setup It takes three steps to connect OpenClaw to OpenSea. 1. **Install ClawLink** — add the plugin to OpenClaw once. 2. **Connect OpenSea** — one-click OAuth in the ClawLink dashboard. 3. **Use it from chat** — ask OpenClaw in plain English. **Paste this into OpenClaw to set up ClawLink:** > I want to connect my apps to OpenClaw through ClawLink. > Please install the ClawLink plugin from ClawHub and enable it: `openclaw plugins install clawhub:clawlink-plugin` > When it is installed, tell me and stop. After I reply, give me the ClawLink pairing link. Setup notes, if you need them: https://claw-link.dev/skill.md **Alternative for any agent (no plugin needed):** if the OpenClaw plugin route isn't available or doesn't work, any AI agent with shell access can use the ClawLink CLI instead: ```bash npx -y @useclawlink/cli login # sign in via browser — no API key to paste npx -y @useclawlink/cli connect open-sea # connect OpenSea (browser OAuth) npx -y @useclawlink/cli actions open-sea # list available actions npx -y @useclawlink/cli run open-sea --input '' # execute (add --confirm for writes) ``` ### Install by command The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval: ```bash openclaw plugins install clawhub:clawlink-plugin ``` Then ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say `done`. Finally, connect OpenSea in the [ClawLink dashboard](https://claw-link.dev/dashboard) — paste your OpenSea API key once. Verify the connection by asking OpenClaw: > Use OpenSea to build criteria offer and walk me through the result in plain English. ### Using a different agent? The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI: ```bash npx -y @useclawlink/cli login ``` `login` opens the same browser approval and stores a credential locally. Once OpenSea is connected in the dashboard, that agent calls the same 24 OpenSea tools over MCP. Full setup for MCP clients and shell agents: [connect apps to any AI agent](https://claw-link.dev/learn/connect-apps-to-any-ai-agent). ## OpenSea MCP for OpenClaw Looking for a OpenSea MCP server for OpenClaw? ClawLink connects OpenSea to OpenClaw and exposes 24 OpenSea tools your agent can call over [MCP](https://claw-link.dev/learn/what-is-an-mcp-server), with [hosted auth](https://claw-link.dev/learn/oauth-for-ai-agents) and nothing to run or maintain yourself. Using Hermes instead? The [Hermes OpenSea integration](https://claw-link.dev/hermes/open-sea) works the same way. ## What the OpenClaw OpenSea integration can do 24 OpenSea tools are ready for OpenClaw once the account is connected. ### All 24 OpenSea tools for OpenClaw | Tool | What it does | |---|---| | **Build criteria offer** `open_sea_build_criteria_offer` | Build a portion of a criteria offer including the merkle tree needed to post an offer | | **Fulfill listing** `open_sea_fulfill_listing` | Retrieve all the information, including signatures, needed to fulfill a listing directly onchain | | **Fulfill offer** `open_sea_fulfill_offer` | Retrieve all the information, including signatures, needed to fulfill an offer directly onchain | | **Get account** `open_sea_get_account` | Get an OpenSea Account Profile including details such as bio, social media usernames, and | | **Get all listings by collection** `open_sea_get_all_listings_by_collection` | Get all active, valid listings for a single collection | | **Get all offers by collection** `open_sea_get_all_offers_by_collection` | Get all active, valid offers for the specified collection | | **Get best listing by nft** `open_sea_get_best_listing_by_nft` | Get the best listing for an NFT | | **Get best listings by collection** `open_sea_get_best_listings_by_collection` | Get the cheapest priced active, valid listings on a single collection | | **Get best offer by nft** `open_sea_get_best_offer_by_nft` | Get the best offers for an NFT | | **Get collection** `open_sea_get_collection` | Get a single collection including details such as fees, traits, and links | | **Get collection stats** `open_sea_get_collection_stats` | Get stats for a single collection on OpenSea | | **Get collections** `open_sea_get_collections` | Get a list of OpenSea collections with optional filtering and pagination | | **Get contract** `open_sea_get_contract` | Get a smart contract for a given chain and address | | **Get events** `open_sea_get_events` | Get a list of events from OpenSea based on various filters like timestamps and event types | | **Get listings** `open_sea_get_listings` | Get the complete set of active, valid listings | | **Get nft** `open_sea_get_nft` | Get metadata, traits, ownership information, and rarity for a single NFT | | **Get order** `open_sea_get_order` | Get a single order, offer or listing, by its order hash | | **Get payment token** `open_sea_get_payment_token` | Get a smart contract for a given chain and address | | **Get traits** `open_sea_get_traits` | Get the traits in a collection | | **Create criteria offer** `open_sea_create_criteria_offer` | Create a criteria offer to purchase any NFT in a collection or which matches the specified trait | | **Create item offer** `open_sea_create_item_offer` | Create an offer to purchase a single NFT (ERC721 or ERC1155) | | **Create listing** `open_sea_create_listing` | List a single NFT (ERC721 or ERC1155) for sale on the OpenSea marketplace | | **Refresh nft metadata** `open_sea_refresh_nft_metadata` | Refresh metadata for a single NFT | | **Cancel order** `open_sea_cancel_order` | Offchain cancel a single order, offer or listing, by its order hash when protected by the | ## Example prompts **Build Criteria Offer** > Use OpenSea to build criteria offer and walk me through the result in plain English. **Fulfill Listing** > Use OpenSea to fulfill listing and walk me through the result in plain English. **Fulfill Offer** > Use OpenSea to fulfill offer and walk me through the result in plain English. **Get Account** > Pull the relevant data from OpenSea, summarize it in plain English, and point out anything that needs attention. ## ClawLink vs. building it yourself The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want OpenSea working from chat. | | Manual | ClawLink | |---|---|---| | **Credential handling** | Collect, validate, store, and rotate the OpenSea API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected OpenSea account becomes available to the agent without you building credential management. | | **Ongoing maintenance** | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for OpenSea. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. | | **Agent usability** | You still need to expose the right OpenSea actions to the runtime in a format your agent can reliably use. | 24 tools for OpenSea are already exposed through ClawLink, so the agent can read and act from chat immediately. | ## ClawLink vs. Composio Composio also exposes OpenSea to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect OpenSea in the browser, and the 24 tools above work from chat. There is no SDK and no config file, and the OpenSea key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full [Composio alternatives](https://claw-link.dev/hub/composio-alternatives) comparison. ### OpenClaw installed the OpenSea skill but can't call the tools The ClawHub skill teaches OpenClaw about OpenSea, but the calls run through the ClawLink plugin and your connected account. Make sure OpenSea is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ### Connection succeeds but no tools appear Reconnect OpenSea from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded. ### "Tool schema not loaded yet" error when calling OpenSea tools OpenSea tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every OpenSea call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again. ### OpenSea returns 403 or "permission denied" on one action while others work Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs. ### API key setup works but results look incomplete Double-check that the API key for OpenSea has the right scopes or account access. A valid key can still be too limited for some reads or writes. ### Is there a OpenClaw OpenSea integration? Yes. ClawLink is the fastest way to connect OpenClaw to OpenSea: link your OpenSea account once in the browser and OpenClaw can call the OpenSea API through 24 ready-made tools — no custom code or token handling. ### How do I add OpenSea to OpenClaw with ClawLink? Paste the setup prompt from this page into OpenClaw. It installs the ClawLink OpenSea skill from ClawHub, then you click Connect in the dashboard to authorize OpenSea. OpenClaw calls the tools from the next message — no config files, and the OpenSea key you paste is stored server-side instead of in your environment. ### How long does it take to connect OpenSea to OpenClaw? About two minutes. Sign in, click Connect next to OpenSea in the dashboard, authenticate, and OpenClaw can use it from the next chat message. ### Why use ClawLink instead of wiring OpenSea up myself? The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want OpenSea working from chat. ### OpenClaw installed the OpenSea skill but can't call the tools The ClawHub skill teaches OpenClaw about OpenSea, but the calls run through the ClawLink plugin and your connected account. Make sure OpenSea is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register. ## Related - [Connect Stripe](https://claw-link.dev/openclaw/stripe) — Manage payments, customers, and invoices - [Zoho Books tools](https://claw-link.dev/openclaw/zoho-books) — Organize finances, invoices, bills, and accounting - [Ramp](https://claw-link.dev/openclaw/ramp) — Read cards, transactions, bills, and reimbursements, and file receipts