> For the complete documentation index, see [llms.txt](https://docs.nansen.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nansen.ai/api/changelog/06-11-2026-prediction-market-retirement.md).

# 06-11-2026: Prediction Market retirement

All Prediction Market API endpoints retire on December 4, 2026.

On **December 4, 2026**, Nansen will retire every Prediction Market endpoint under `/api/v1/prediction-market/` across the API, MCP and CLI. After that date, requests will return an error instead of Polymarket data.

| API endpoint                                       | MCP tool                            |
| -------------------------------------------------- | ----------------------------------- |
| `POST /api/v1/prediction-market/categories`        | `prediction_market_screener`        |
| `POST /api/v1/prediction-market/market-screener`   | `prediction_market_screener`        |
| `POST /api/v1/prediction-market/event-screener`    | `prediction_market_screener`        |
| `POST /api/v1/prediction-market/ohlcv`             | `prediction_market_ohlcv`           |
| `POST /api/v1/prediction-market/orderbook`         | `prediction_market_orderbook`       |
| `POST /api/v1/prediction-market/trades-by-market`  | `prediction_market_trades`          |
| `POST /api/v1/prediction-market/top-holders`       | `prediction_market_top_holders`     |
| `POST /api/v1/prediction-market/pnl-by-market`     | `prediction_market_pnl_leaderboard` |
| `POST /api/v1/prediction-market/position-detail`   | `prediction_market_position_detail` |
| `POST /api/v1/prediction-market/trades-by-address` | `prediction_market_address_trades`  |
| `POST /api/v1/prediction-market/address-summary`   | `prediction_market_address_summary` |
| `POST /api/v1/prediction-market/pnl-by-address`    | `prediction_market_address_pnl`     |

The notice period begins November 6, 2026. Existing requests keep working, with the same data and credit cost, until December 4. Until then, responses carry `Deprecation`, `Sunset` and `Warning` headers.

## Prepare your integration

* Remove calls to `/api/v1/prediction-market/` endpoints from scheduled jobs and integrations before December 4. No replacement endpoint is planned.
* Update MCP prompts and tool calls that use the `prediction_market_*` tools listed above.
* Update CLI jobs that use `nansen research prediction-market` commands. Changing clients or using an older client will not preserve access after retirement.

For help updating an integration, [contact Nansen support](https://support.nansen.ai/hc/en-us/requests/new).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nansen.ai/api/changelog/06-11-2026-prediction-market-retirement.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
