Token Unlocks Calendar 🔓

foXLabs crypto series: Funding rates · DeFi volume & fees · Stablecoins · Hacks database

🎉 Turn token vesting into a clean, structured unlocks calendar — no login, no API key, one row per unlock, with the token, unlock date, amount and share of supply. Built for crypto traders, analysts and risk teams.

🔍 What is the Token Unlocks Calendar — and when should you use it?

Give this actor token symbols or names and it returns matching unlocks from public token vesting / unlock schedules — as clean, deduplicated rows you can filter, export or feed to an AI agent. Every run reads the source live.

Use it when you need: a token’s upcoming unlocks; supply-overhang risk; or an unlock calendar across tokens.

Use something else when: you need live price — this is unlock schedules, not market data.

🤖 Use with AI agents

Already on the Apify MCP server? Ask for this Actor by name: foxlabs/token-unlocks-calendar.

Your agent can pay for its own runs. This Actor is pay-per-event with agentic payments, so an agent can discover it, run it and settle the bill over x402 (USDC on Base) or Skyfire — no Apify account or API token of its own. Billing is the same either way: per delivered record, never for errors.

Otherwise paste this into Claude, ChatGPT, Cursor or any MCP-enabled assistant:

I want to pull token unlock company records using the Apify Actor `foxlabs/token-unlocks-calendar`.
Input: `daysAhead`, `minPctOfSupply`, `category`, `unlockType` and more — see the Input table below. `maxResults` caps how many results are returned.
Start with: {"daysAhead":90,"maxResults":1000}
Ask me what to look up, run the Actor, then summarise the rows as a table.

The machine-readable API, MCP config and OpenAPI definition live at apify.com/foxlabs/token-unlocks-calendar.md.

📋 Overview

Everything you need to turn public token vesting / unlock schedules into clean, structured data — in one actor, with no login, cookies or API key.

Why teams pick this actor:

• ✅ Whole feed, one call — name or ID in, matching unlocks out.
• 🧹 No empty-promise columns — only fields this registry actually fills; degenerate columns are removed.
• 🔗 Stable identifiers — every row carries the source's own IDs, ready to join across runs and to other Fox Labs actors.
• 💰 Per-row pricing — a minimal price per delivered row, no subscription.
• 🤖 Agent-ready — MCP + x402 agentic payments.

✨ Features

• 🔍 Name or ID lookup — relevance-ranked name search or exact registry-ID lookup.
• 🏢 Full entity profile — status, legal form, formation date, address and the registry’s own contact fields.
• 🧹 Clean schema — deduplicated camelCase rows, ready for CSV/Excel/JSON.

🎬 Quick Start

curl -X POST "https://api.apify.com/v2/acts/foxlabs~token-unlocks-calendar/runs?token=YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"daysAhead":90,"maxResults":1000}'

🚀 Getting Started (3 steps)

1. Choose your targets — token symbols or names.
2. Set the cap — maxResults limits how many results are returned.
3. Run and export — get a clean dataset as JSON, CSV or Excel.

📥 Input

{"daysAhead":90,"maxResults":1000}

Field	Type	Description
daysAhead	integer	Include unlock events happening within this many days from now. E.g. 7 = this week, 30 = this month, 90 = this quarter.
minPctOfSupply	number	Only include unlocks worth at least this percentage of the token's max supply (the metric traders watch — big % = potential sell pressure). 0 = no filter.
category	string	Keep only unlocks to this recipient group, e.g. "insiders", "privateSale", "publicSale", "noncirculating". Leave empty for all.
unlockType	string	Filter by unlock mechanics: "cliff" (one big release) or "linear" (gradual). Leave empty for both.
projects	array	Limit to specific project slugs (e.g. "aptos", "arbitrum", "celestia"). Leave empty to scan all ~326 projects.
sortBy	string	Order the calendar by soonest date, or by biggest unlock (% of supply).
maxResults	integer	Cap the number of unlock-event rows returned.

📤 Output

One row per result, saved to the dataset. Every row carries scrapedAt. Lookups that cannot be completed are reported in the run log rather than silently dropped.

Field	Description
rank	Rank
project	Project
slug	Slug
token	Token
chain	Chain
unlockDateIso	Unlock Date Iso
daysUntil	Days Until
unlockType	Unlock Type
category	Category
tokensUnlocked	Tokens Unlocked
pctOfMaxSupply	Pct Of Max Supply
description	Description
source	Source
generatedAtIso	Generated At Iso

💼 Use cases

1. Unlock risk — flag tokens with large upcoming unlocks. Input: token symbols. Output: unlock date + amount. Use: anticipate supply pressure.

2. Trading calendar — build an unlock calendar to trade around. Input: token names. Output: dated unlocks. Use: time entries/exits.

3. Portfolio risk — watch unlocks across holdings. Input: token symbols, scheduled. Output: upcoming unlocks. Use: manage exposure.

🔗 Integration

JavaScript / Node.js

import { ApifyClient } from 'apify-client';
const client = new ApifyClient({ token: 'YOUR_TOKEN' });
const run = await client.actor('foxlabs/token-unlocks-calendar').call({"daysAhead":90,"maxResults":1000});
const { items } = await client.dataset(run.defaultDatasetId).listItems();
console.log(items[0]);

Python

from apify_client import ApifyClient
client = ApifyClient('YOUR_TOKEN')
run = client.actor('foxlabs/token-unlocks-calendar').call(run_input={"daysAhead":90,"maxResults":1000})
for item in client.dataset(run['defaultDatasetId']).iterate_items():
    print(item)

Automation (n8n / Zapier / Make): schedule or webhook → HTTP request to the actor API with your input → handle the JSON dataset → push to a sheet, CRM or dashboard.

📊 Pricing

Pay-per-event: per delivered record. Empty or failed lookups are never billed. View current pricing.

❓ FAQ

Do I need an account, login or API key? No. This reads public token vesting / unlock schedules.

What do I search by? Token symbols or names.

How current is the data? Every run queries the source live, so results are as fresh as the registry.

What does each row cover? One unlock event: token, unlock date, amount and share of circulating/total supply.

Can I export to CSV / Excel / JSON? Yes — directly from the Apify dataset.

🐛 Troubleshooting

• Fewer rows than expected — raise maxResults, or refine the input.
• A name returns an unexpected entity — it matched a similar registered name; search the exact registry ID.
• No rows for a name — try the entity’s exact legal name or its registry ID.

⚖️ Is it legal to scrape this data?

This actor reads public token vesting and unlock schedules. Results can still contain personal data (e.g. a person’s name); personal data is protected by the GDPR and similar laws, so only process it with a legitimate basis. See Apify’s blog post on the legality of web scraping.

🤝 Support & contact

• 🌐 Website: data.foxlabs.com.tr
• 📧 Email: info@foxlabs.com.tr
• 🐛 Issues: open a ticket in the Actor’s Issues tab
• 🧰 More clean B2B data actors: Fox Labs on Apify

Changelog

0.1.16 — 2026-09-20 — README examples corrected against the real input schema

• The README's code examples did not match this Actor. They used queries and maxResultsPerQuery — keys that do not exist in this Actor's input schema — with a placeholder value, and the input table listed those same phantom fields. Anyone who copied the AI-agent, cURL, JavaScript or Python example got a failing run. Every example now uses the real schema and matches the Console prefill: {"daysAhead":90,"maxResults":1000}
• The input table is regenerated from input_schema.json, so it lists the fields the Actor actually accepts.
• Removed claims carried over from the same generator template where present: "formation / status monitoring", "a canonical registry record for KYB and due diligence", "every row carries query", and industry described as a NACE code.
• No code, output field or pricing change.

0.1 — 2026-09-07

• Enabled AI-agent payments (x402) + rebuilt the README to the full standard (What-is / when, AI-agents + x402 agentic payments + MCP, Overview, Features, Use cases, Integration, FAQ, Troubleshooting, Support & contact).

0.0

• Initial release: data from public token vesting / unlock schedules by name or registry ID.