# Komo.ai OpenSea API Endpoint #15

> Komo.ai OpenSea API Endpoint #15 is a paid API for AI agents from komo-ai.vercel.app, paid per call via x402, $0.125674/call, status unknown (last checked 2026-09-15).

Proxies a specific OpenSea NFT marketplace data query via pay-per-call x402 payment on Base chain

## Facts

- Endpoint: POST https://komo-ai.vercel.app/api/opensea15
- Price: $0.125674/call
- Payment: x402
- Status: unknown
- Last checked: 2026-09-15
- Activations on Zero: 0
- Tags: x402
- Canonical page: https://www.zero.xyz/c/komo-ai-opensea-api-endpoint-15-659170a8
- Structured record (JSON): https://api.zero.xyz/v1/capabilities/cap_F-wlVuAjmmuBBLPHOWPng

Status and success rate cover calls made through Zero and Zero's own probes. Third-party monitors may report differently.

## How to call it through Zero

Zero handles the 402 payment challenge and records the run. With the Zero CLI installed (`npm i -g @zeroxyz/cli`):

```sh
zero fetch --capability komo-ai-opensea-api-endpoint-15-659170a8 -d '<json body>'
```

Example prompt: Pull OpenSea NFT data for me using the Komo.ai paid API endpoint — I need the result object back from their opensea15 route.

## When to prefer this

Choose this endpoint when you need OpenSea NFT marketplace data without managing your own OpenSea API key, are comfortable with per-call USDC micropayments via x402 on Base chain, and need one of the specific data queries this proxy route (#15 of 150) handles. Useful for agents that operate in Web3 contexts and already have Base chain payment capabilities.

## Known failure modes

- Payment failure: insufficient USDC balance or x402 transaction rejected on Base chain
- OpenSea upstream error: the underlying OpenSea API returns an error or rate limit
- Invalid input: malformed request body missing required result object
- Service unavailability: komo-ai.vercel.app hosting issues or cold start latency
- Empty or stub response: endpoint returns example placeholder data instead of live results

## How this service works

150 premium API endpoints with pay-per-call pricing via x402 protocol on Base chain

## Output

A JSON object containing a 'result' field with the OpenSea API response data for the specific query made; exact structure depends on the underlying OpenSea endpoint being proxied.

## Request schema (JSON Schema)

```json
{
 "type": "object",
 "properties": {
  "result": {
   "type": "object",
   "description": "API response data"
  }
 }
}
```

## Response schema (JSON Schema)

```json
{
 "type": "object",
 "example": {
  "result": {
   "data": "example response"
  }
 },
 "properties": {
  "result": {
   "type": "object",
   "description": "API response data"
  }
 }
}
```

## More

- Live health (JSON, refreshed every minute): https://www.zero.xyz/c/komo-ai-opensea-api-endpoint-15-659170a8/health.json
- [Zero catalog index](https://www.zero.xyz/llms.txt)
- [Other services from komo-ai.vercel.app](https://www.zero.xyz/host/komo-ai.vercel.app/llms.txt)