Skip to main content

Welcome

HashDit APIs help wallets, dApps, exchanges, and security products evaluate domains, addresses, tokens, approvals, typed-data signatures, and transactions before users take action. Each endpoint returns a focused decision or set of signals designed for production integrations.

Authentication

Every endpoint requires an API key in the X-API-KEY header.
Keep API keys on a trusted server. Never expose them in client-side code or public repositories.
A missing or invalid key returns HTTP 401:

Base URL

Request Field Names

HashDit-owned request fields are documented in snake_case. Equivalent camelCase spellings remain accepted for compatibility, such as chain_id / chainId and user_address / userAddress. Choose one style per request. Do not send both spellings of the same field: conflicting duplicate values are rejected, and relying on equal duplicates makes integrations harder to review. HashDit-owned response fields use snake_case, with these compatibility boundaries:
  • pollAfter is a historical async-envelope field and remains unchanged.
  • Embedded EIP-712 typed data keeps protocol and application field names such as primaryType, verifyingContract, and chainId.
  • Established Transaction Security and simulation payloads keep integration-defined fields such as gasLimit, tokenName, and tokenPriceUSD.

Getting Started

  1. Obtain an API key from the HashDit team.
  2. Choose the endpoint that matches the decision in your product flow.
  3. Send Content-Type: application/json and X-API-KEY.
  4. Follow the endpoint’s result interpretation, lifecycle, and retry guidance.

API Endpoints

Address Classification

Identify an EOA, token, proxy, or other contract type.

Address Poisoning Detection

Detect lookalike address and token poisoning, one address or a batch at a time.

Address Security v2

Assess contract, privilege, rug-pull, market, and threat-intelligence risk.

Domain Security

Assess domain risk and optionally check usable-content availability.

Token Security

Get an overall security score and risk level for tokens on supported EVM networks and TRON.

Solana Token Security

Analyze Solana token authority, concentration, market, and threat signals.

Token Approval Security

Review outstanding allowances, current exposure, and entity risk.

EIP-712 Signature Security

Evaluate typed-data intent and get an ALLOW, WARN, or BLOCK recommendation.

Transaction Security

Simulate a transaction and decide whether to allow, warn, or block it.