Skip to content

feat(ecosystem): add OpenSea skill (NFT marketplace + Seaport trades)#37

Merged
SahilAujla merged 2 commits into
mainfrom
ecosystem-opensea
May 15, 2026
Merged

feat(ecosystem): add OpenSea skill (NFT marketplace + Seaport trades)#37
SahilAujla merged 2 commits into
mainfrom
ecosystem-opensea

Conversation

@SahilAujla
Copy link
Copy Markdown
Contributor

@SahilAujla SahilAujla commented May 14, 2026

Summary

  • Adds OpenSea as an ecosystem partner skill (skills/ecosystem/opensea/), curated subset of ProjectOpenSea/opensea-skill
  • Drives the official @opensea/cli for NFT marketplace data (listings, offers, sales, drops, traits, events) and Seaport trade execution across Ethereum, Base, Arbitrum, Optimism, Polygon, and more
  • Adds the path to .claude-plugin/plugin.json so the Vercel npx skills CLI discovers it

Scope

In: marketplace data (best/all listings, offers, trait offers, collection stats, trending, top), Seaport trade execution (buy / sell fulfillment, create listings / offers), events (by collection / NFT / account, real-time streaming), drops + minting, search, account resolve.

Out (routes back to first-party Alchemy or other ecosystem skills):

  • General NFT metadata (name, image, traits, ownership outside marketplace context) → alchemy-api (NFT API). OpenSea's NFT data is marketplace-flavored and rate-limited harder; Alchemy is broader and faster for pure metadata.
  • token spot prices → Prices API · token metadata → Token API · balances → Portfolio API · transaction history → Transfers API · live RPC → JSON-RPC · simulation → Simulation API · AA / embedded wallets → Wallets / Account Kit / Bundler / Gas Manager

Test plan

  • OpenSea scope_in audited against alchemy-api — partial overlap on NFT metadata; resolved by scoping NFT reads to marketplace context (listings, offers, sales) and routing pure metadata reads to Alchemy NFT API

Notes

  • API key is required but instant -POST /api/v2/auth/keys returns one with no signup. Higher tiers need developer-portal signup.
  • Privy credentials are optional and only needed for end-to-end write flows that sign through Privy, otherwise the skill returns calldata and the app handles signing however it wants.

Adds skills/ecosystem/opensea/ — a curated subset of
projectopensea/opensea-skill exposing NFT marketplace data (listings,
offers, sales, drops, traits, events) and Seaport trade execution via
the official @opensea/cli and OpenSea REST API across Ethereum, Base,
Arbitrum, Optimism, Polygon, and more.

scope_in:
- Marketplace data: best listings, best offers, all listings / offers
  on a collection, trait offers, collection stats (floor, volume),
  trending, top, traits
- Seaport trade execution: fulfillment data for buying / selling,
  creating listings / offers via Seaport order POSTs
- Events / monitoring: events by collection / NFT / account, real-time
  streaming (websocat)
- Drops + minting: drops list / get / mint tx construction
- Search across collections / NFTs / tokens / accounts
- Account utilities (resolve ENS / username / address)

scope_out (routes back to first-party Alchemy or other ecosystem):
- general NFT metadata reads (name, image, traits, ownership) outside
  marketplace context → alchemy-api NFT API (broader, faster)
- pure cross-chain token swaps → lifi (more bridges, more chains)
- token spot prices → alchemy-api Prices API
- token metadata, balances → alchemy-api Token / Portfolio API
- transaction history → alchemy-api Transfers API
- live RPC reads → alchemy-api JSON-RPC
- simulation → alchemy-api Simulation API
- AA, embedded wallets → alchemy-api Wallets / Account Kit / Bundler

Made-with: Cursor
Records the OpenSea repo URL and the commit SHA the curated copy was
authored against, so future manual refreshes have an auditable
baseline to diff from.

Co-authored-by: Cursor <cursoragent@cursor.com>
@SahilAujla SahilAujla merged commit c0a969e into main May 15, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants