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
Promotions
AI
Gate AI
Your all-in-one conversational AI partner
Gate AI Bot
Use Gate AI directly in your social App
GateClaw
Gate Blue Lobster, ready to go
Gate for AI Agent
AI infrastructure, Gate MCP, Skills, and CLI
Gate Skills Hub
10K+ Skills
From office tasks to trading, the all-in-one skill hub makes AI even more useful.
GateRouter
Smartly choose from 40+ AI models, with 0% extra fees
Claude API supports keyless authentication: seamlessly integrate existing AWS and GCP identities, completely eliminate static API keys
Crypto news, Anthropic announces the introduction of a keyless authentication (workload identity federation, or WIF) mechanism for the Claude API. This feature allows enterprise applications to reuse cloud identities from AWS, Google Cloud, Azure, or GitHub Actions to obtain short-term tokens, replacing static API keys. Anthropic points out that API key leaks are a common security concern among customers, and traditional static keys are easily exposed in CI/CD pipelines. Under the new mechanism, workloads present a JWT token to Anthropic, which, after verification, maps it to an internal “service account” with specific permissions and returns a short-lived access token valid for a few minutes. Currently, this keyless authentication system is compatible with mainstream cloud providers and standards-compliant OIDC issuers. Developers only need to update their SDKs, as token exchange and refresh are automatically handled by the SDK, eliminating the risk of hardcoded keys.