canonical: https://jentic.com/apis/opensea.io/opensea # OpenSea API The OpenSea API reads and writes NFT marketplace data across supported blockchains. It returns collections with their floor-price and volume stats, individual NFTs with traits and ownership, and the active listings and offers on a collection or a single item. Write operations create listings and item offers per chain and marketplace protocol, and event endpoints stream sales, transfers, and new listings for a collection, NFT, or account. ## For AI agents Read NFT collections, items, listings, offers, and marketplace events across chains, and create listings and offers. Authenticates with an API key. ## Scope Does not handle fiat payment processing, private key or wallet custody, or token price charting. Use for NFT marketplace listings, offers, and data only. ## Capabilities - Browse NFT collections and read their floor price and volume stats - Fetch individual NFTs, their traits, and ownership by contract or account - Retrieve active listings and offers for a collection or a single NFT - Create listings and item offers on supported chains and marketplaces - Track marketplace events such as sales, transfers, and new listings - Look up token, contract, and payment-token details across supported chains ## Use cases ### AI Agent NFT Market Research An AI agent tracking NFT markets can pull a collection's floor price, recent sales, and best listings through Jentic. The agent searches for the stats or events operation, passes the collection slug, and receives structured market data it can summarize, without the developer wiring the API key header or paging through the OpenSea reference docs. Example prompt: Call GET `/api/v2/collections/{slug}/stats` to read the floor price and volume for a collection ### Listing and Offer Automation Trading tools create listings and submit offers programmatically. OpenSea exposes listing and offer creation per chain and marketplace protocol, along with fulfillment-data operations, so an agent can post a sell listing or a bid once the order parameters are prepared and signed. Example prompt: Call POST `/api/v2/orders/{chain}/{protocol}/listings` to create a listing for an NFT the user owns ### Wallet and Collection Discovery Portfolio dashboards show the NFTs and token balances held by a wallet and resolve account identifiers to profiles. The account operations return NFTs and token balances by address, and the search operation finds collections and items across OpenSea. Example prompt: Call GET `/api/v2/chain/{chain}/account/{address}/nfts` to list the NFTs held by a wallet ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/api/v2/collections` | Get multiple collections | | GET | `/api/v2/collections/{slug}/stats` | Get collection floor and volume stats | | GET | `/api/v2/chain/{chain}/contract/{address}/nfts/{identifier}` | Get a single NFT | | GET | `/api/v2/listings/collection/{slug}/best` | Get best listings by collection | | GET | `/api/v2/offers/collection/{slug}` | Get offers by collection | | POST | `/api/v2/orders/{chain}/{protocol}/listings` | Create a listing | | POST | `/api/v2/orders/{chain}/{protocol}/offers` | Create an item offer | | GET | `/api/v2/events/collection/{slug}` | Get marketplace events by collection | ## Key resources - **Collections** — Collection metadata, floor and volume stats, and trait listings - **NFTs** — NFT details, metadata, traits, and ownership by contract or account - **Orders** — Listings, offers, and order fulfillment across chains and protocols - **Events** — Marketplace events such as sales, transfers, and new listings ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 64 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 84 / 100 - Developer Experience & Jentic Compatibility: 66 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 76 / 100 - **View full report:** https://jentic.com/apis/opensea.io/opensea/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring OpenSea by hand means sending its API key in the x-api-key header, matching the right chain and marketplace protocol in each path, and handling pagination yourself. Through Jentic you install once, import OpenSea from the API Directory, store the key once, and your agent calls it. - **Permission scoping:** OpenSea carries the collection slug and chain in the URL path, so a rule can keep your agent on specific read operations such as collection stats and NFT lookups. You choose the operation set, so order-creation operations like creating a listing or an offer are not included unless you add them. - **Credential handling:** Your OpenSea API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get an NFT collection floor price' or 'list NFTs in a wallet', and Jentic returns the matching OpenSea operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Alchemy** — Web3 and NFT data APIs across multiple chains - **Moralis** — Cross-chain NFT ownership, metadata, and transfer data ## FAQ ### What authentication does the OpenSea API use? The OpenSea API authenticates with an API key sent in the `x-api-key` header, per its OpenAPI spec. Through Jentic the key is stored encrypted by your own Jentic One instance and injected at call time, so it never enters the agent's prompt, logs, or context. ### Can I read a collection's floor price with the OpenSea API? Yes. The collection stats operation returns the floor price, total volume, and sales counts for a collection by its slug. You can combine it with the events operations to see the recent sales that moved the floor. ### What are the rate limits for the OpenSea API? The OpenAPI spec does not specify rate limits; OpenSea enforces per-key limits that depend on your access tier. Current limits are published in the vendor documentation at https://docs.opensea.io/. ### How do I read NFT market data with the OpenSea API through Jentic? Install Jentic One with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, import OpenSea from the API Directory, and store your API key once. Your agent then searches for an intent such as 'get an NFT collection floor price', and Jentic returns the matching operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo. ### Is there an OpenSea MCP server? You do not need an MCP server to give your agent the OpenSea API. Jentic connects it directly from the API Directory: import the API, store your key once, and your agent calls the collection, NFT, and order operations on demand, which keeps your agent's context free of an extra server's tool definitions. ### Can I limit what my agent is allowed to do with the OpenSea API? Yes. OpenSea separates read operations from order creation, so you can allow your agent to read collections, NFTs, and listings while leaving out creating a listing or submitting an offer. Because you run Jentic One yourself, the agent can research the market but cannot place orders unless you add those operations, and every call is logged.