Wallet authentication for REST and MCP

Wallet authentication is now available for OpenSea's public REST API and hosted MCP server. With scoped access, agents can check eligibility, manage favorites, follow accounts, or create and cancel orders without receiving broader wallet permissions.

OpenSea API keys still provide API access and quota. Wallet-scoped operations also require a short-lived wallet JWT in Authorization: Bearer. The JWT carries the wallet identity and the scopes granted for the task.

You can create and manage scoped personal access tokens (PATs) from Developer Settings. Exchange the PAT for a wallet JWT before calling REST or MCP. Do not send a PAT in the Authorization header. Creating, listing, rotating, and revoking PATs requires the wallet-authenticated session.

Server-side agents that control an EVM signing key can authenticate headlessly with SIWE through the OpenSea CLI or TypeScript SDK. OAuth-capable MCP clients discover wallet sign-in from https://mcp.opensea.io/mcp.

Start with the wallet authentication guide. Wallet auth is also covered in the MCP guide and OpenSea API skill.