Token unlock calendar: upcoming vesting unlocks in the next N days, sized vs supply
Token unlock calendar: upcoming vesting unlocks in the next N days, sized vs supply. Every curated token unlock in the next N days (default 30, max 365) with date, amount, precision flags (exact / estimated date / upper bound), label and primary source link.…
by UnlockBot Onchain Intel (x402) · verified provider · updated 2026-10-14
What it does
Token unlock calendar: upcoming vesting unlocks in the next N days, sized vs supply. Every curated token unlock in the next N days (default 30, max 365) with date, amount, precision flags (exact / estimated date / upper bound), label and primary source link. Keywords: token unlocks calendar, upcoming unlocks, vesting schedule, tokenomics, cliff unlock, supply events.
Tags: crypto · defi · onchain · x402 · base · Unlocks · Calendar
Call contract
- Method
- HTTP
- Input
- HTTP request
- Output
- json
Use with an agent
- Discover. Agents find this listing with
GET https://bazaar.saylorinnovations.com/discovery/search?query=…, the MCP toolsearch_resources, or/discovery/resources. - Inspect. Fetch
/resources/61891.jsonfor the price and payment options. - Pay. Call
GET https://5fm7hu2rbzd3.hostc.app/unlocks/upcoming. The provider answers402with its payment requirements. An x402 client signs one of the options below and retries withPAYMENT-SIGNATURE. - Execute. The provider returns
200with 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 | Network | Asset | Amount | Pay to | Timeout |
|---|---|---|---|---|---|
| exact | Base eip155:8453 | USDC | $0.02 | 0x21e4F3c6EcDb0F0CADC59511BF675B9BcBbeD304 | 120s |
accepts[] (raw JSON)
[
{
"scheme": "exact",
"network": "eip155:8453",
"payTo": "0x21e4F3c6EcDb0F0CADC59511BF675B9BcBbeD304",
"asset": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
"amount": "20000",
"amountUsd": 0.02,
"maxTimeoutSeconds": 120
}
]Examples
curl "https://5fm7hu2rbzd3.hostc.app/unlocks/upcoming"
# -> 402 Payment Required, accepts[] lists how to pay
# retry with a PAYMENT-SIGNATURE (or PAYMENT header) once paidconst res = await fetch("https://5fm7hu2rbzd3.hostc.app/unlocks/upcoming");
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://5fm7hu2rbzd3.hostc.app/unlocks/upcoming")
if res.status_code == 402:
accepts = res.json()["accepts"]
# pay one of accepts[] via an x402 client, then retry with the payment headerDetails
- Provider
- UnlockBot Onchain Intel (x402)
- Endpoint
- https://5fm7hu2rbzd3.hostc.app/unlocks/upcoming
- Machine-readable
/resources/61891.json