A-share share-lockup expiry calendar (限售股解禁): which listed companies have restricted sh…

What it does

A-share share-lockup expiry calendar (限售股解禁): which listed companies have restricted shares becoming tradable over the coming window, with the exact expiry date, days until expiry, number of shares released, estimated release value in yuan at the latest close, the released stake as a percent of total shares, the release type (IPO original shareholders, private placement institutions, equity incentive, additional commitments) and the latest price. Defaults to the next 30 days sorted by expiry date, so the first rows are the nearest supply overhangs; pass ?days=90 for a longer window, ?symbol=002594 for one stock, ?type=定向增发 to filter by release type, or ?sort=size to rank by release value. Lockup expiries are a scheduled, date-known supply event that traders and risk systems screen for, and the raw source is a paginated web table. 中文：A股限售股解禁日历——解禁日、距今天数、解禁股数、解禁市值、占总股本比例、解禁类型。 No API key and no signup: call the endpoint, it answers HTTP 402 with the payment terms, pay per request in USDC on Base with any x402-compatible client or wallet, then retry the same request to get the data.

Tags: china · a-shares · lockup · unlock · 解禁 · risk

Use with an agent

1. Discover. Agents find this listing with GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP tool search_resources, or /discovery/resources.
2. Inspect. Fetch /resources/74990.json for the price and payment options.
3. Pay. Call GET https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/lockup. The provider answers 402 with its payment requirements. An x402 client signs one of the options below and retries with PAYMENT-SIGNATURE.
4. Execute. The provider returns 200 with the data. Agent Bazaar is not in the request path and never sees your payment.

For humans

You don't need an account or an API key; you need a wallet holding a small amount of USDC on Base, and an x402-capable client (see the examples below). Call the endpoint unpaid first to see exactly what it asks for.

Pricing & payment

Price

$0.02 / request

Protocol

x402 v2

Auth

No account or API key. Pay per request.

Networks

Base

x402 payment requirements

[
  {
    "scheme": "exact",
    "network": "eip155:8453",
    "payTo": "0xE69507F3e6F57A63e90a638E59C47d1b48dc3229",
    "asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
    "amount": "20000",
    "amountUsd": 0.02,
    "maxTimeoutSeconds": 300
  }
]

Examples

curl "https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/lockup"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paid

const res = await fetch("https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/lockup");
if (res.status === 402) {
  const { accepts } = await res.json();
  // pay one of accepts[] via an x402 client, then retry with the payment header
}

import httpx
res = httpx.get("https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/lockup")
if res.status_code == 402:
    accepts = res.json()["accepts"]
    # pay one of accepts[] via an x402 client, then retry with the payment header

Details

Provider

CN Data

Endpoint

https://cn-data-x402.cn-data-x402-worker.workers.dev/cn/lockup

Machine-readable

/resources/74990.json