Skip to main content

Authentication

All programmatic requests to the CrypTech API require an API key passed via the X-API-Key HTTP header.
Requests submitted without a valid key, or with an expired or unauthorized key, return an HTTP 401 Unauthorized status code.

Obtaining an API Key

CrypTech operates an institutional and developer onboarding program. To obtain an API key for your project, trading bot, or application:

Request Developer Credentials

Email [email protected] with your project details, planned request volume, and primary chain requirements.
When requesting a key, please specify:
  1. Organization or Project Name
  2. Intended Use Case (e.g. Wallet security integration, Telegram scam alert bot, Algorithmic DEX trading desk, Academic research)
  3. Estimated Request Volume (Requests per day / month)
  4. Primary Blockchains (Ethereum, BSC, Solana, Polygon, Arbitrum, Base)

Using Your Key

Include the header in every HTTP request:

Security Best Practices

Never expose your API key in client-side code!Do not include your API key in mobile apps, React/Vue frontends, or public GitHub repositories. Anyone with access to your client bundle can extract your key and consume your quota.
  • Use an Environment Variable: Store your key in an environment variable such as CRYPTECH_API_KEY.
  • Route via a Backend Proxy (BFF): If building a web application, call the CrypTech API from your server-side API routes (e.g. Next.js Route Handlers, Node.js Express, Python FastAPI) and forward sanitized results to the browser.
  • Key Rotation: If you suspect your key has been compromised, email [email protected] immediately to request key revocation and issuance of a new credential.