Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Pre-IPOs
Unlock full access to global stock IPOs
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
Anthropic launches Prompt Caching Dashboard, visualizing cache hits and costs
ME News, on April 22 (UTC+8), according to Dongcha Beating monitoring, the Claude Developer Console has launched the Prompt Caching Dashboard, accessible at platform.claude.com/usage/cache. The dashboard can be filtered by workspace, model, and time period, and mainly shows three sets of data: cache read ratio, which is the proportion of requests that hit existing cached content; cache usage composition, which breaks input tokens into four categories—uncached, 5-minute cache write, 1-hour cache write, and cache read—and displays them as stacked bar charts; and write amortization, which measures how many times a single cache write is reused in subsequent reads. In the screenshot example, Claude Opus 4.6 processed 27.4 hundred-million (2.74 billion) input tokens within 7 days, with a read ratio of 85.4% and a write amortization of 8.65x. At the bottom, there is also a time-series chart of cache read ratio with granularity ranging from 1 hour to 24 hours. Anthropic’s prompt caching mechanism allows API users to mark cacheable content such as system prompts and long contexts. The first cache write is charged an additional fee, while subsequent cache hits are billed at about one-tenth of the standard input price. By default, cache retention is 5 minutes, and paid options can extend it to 1 hour. Previously, users could only indirectly judge cache effectiveness by the token count field returned by the API, without any visualization tools. (Source: BlockBeats)