Install Jentic One Beta

Connect the OpenSea API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the OpenSea API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopensea.io%2Fopensea" | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fopensea.io%2Fopensea" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with OpenSea API.

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

GET STARTED

Start building with OpenSea API

Explore with Jentic One

View OpenAPI Document

Use Cases

Patterns agents use OpenSea API for, with concrete tasks.

★ 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.

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.

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.

Call GET /api/v2/chain/{chain}/account/{address}/nfts to list the NFTs held by a wallet

Key Endpoints

50 endpoints — the opensea api reads and writes nft marketplace data across supported blockchains.

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

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}

Why Jentic?

What agents get from Jentic-routed access to this vendor.

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 isolation

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.

Intent-based discovery

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.

FAQs

Specific to using OpenSea API through Jentic.

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.

OpenSea API

AI ReadinessAI-Aware (B)64/100

See full scorecard

Official vendor OpenAPI document · agent-readyE CommerceStorefrontapiKey50 EndpointsREST

For Agents

Read NFT collections, items, listings, offers, and marketplace events across chains, and create listings and offers. Authenticates with an API key.

Use for: Get the floor price for a given NFT collection, List all NFTs owned by a wallet address, Find the best listing for a specific NFT, Create a listing to sell an NFT I own

Not supported: Does not handle fiat payment processing, private key or wallet custody, or token price charting. Use for NFT marketplace listings, offers, and data only.

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.

Jentic One on Github View OpenAPI Document

Show dimension breakdown

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: ASignals: 4

96%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

100%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

42%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

Developer Experience & Jentic Compatibility

Clarity, completeness, and ingestion readiness for developers and tooling.

Grade: BSignals: 4

Example Density

How richly the API is illustrated with examples.

79%

Example Validity

Percentage of examples that conform to their schemas.

75%

Response Coverage

Percentage of operations with complete response definitions (success, client error, server error).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: DSignals: 4

39%

Description Coverage

Coverage of descriptions across API elements.

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

98%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

50%

Summary Coverage

Coverage of summaries across operations/tags/info.

Agent Usability

Functional utility, complexity comfort, and AI orchestration readiness.

Grade: A+Signals: 1

94%

Complexity Comfort

Agent comfort level based on API operational and structural complexity.

Security

Trust, risk posture, and security compliance.

Grade: C-Signals: 1

50%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: A-Signals: 1

76%

Descriptive Richness

Clarity and depth of descriptions across API elements.

Connect the OpenSea API to your agent

Capabilities

Start building with OpenSea API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs

OpenSea API

Jentic AI Readiness Score

OpenSea API

Foundational Compliance

Lint Results

Resolution Completeness

Specification Validity

Structural Integrity

Developer Experience & Jentic Compatibility

Example Density

Example Validity

Response Coverage

Tooling Readiness

AI-Readiness & Agent Experience

Description Coverage

Error Standardization

OperationId Quality

Summary Coverage

Agent Usability

Complexity Comfort

Security

Authentication Strength

AI Discoverability

Descriptive Richness