Changelog

A complete history of VIZI API updates, new features, improvements, and deprecations. Subscribe to our developer newsletter to get notified of breaking changes.

Release History

Every API version is documented below with detailed notes on new endpoints, improvements, fixes, and deprecations.

v2.3 — Batch Scoring Endpoint

March 2026
  • New: POST /v2/scores/batch endpoint for scoring up to 250 addresses in a single request. Returns results synchronously for batches under 50, asynchronously for larger batches with a batch.completed webhook event.
  • New: Score response now includes a confidence field (0.0–1.0) indicating how much on-chain data was available to compute the score.
  • Improved: All SDKs updated to v2.3 with batch scoring support and confidence field types.
  • Fixed: Resolved an edge case where wallets with only Polygon activity could return stale scores after chain reorgs.

v2.2 — Agent Score Model

January 2026
  • New: GET /v2/scores/agent/{address} endpoint for AI agent wallets. Scores autonomous agents on execution reliability, fund safety, transaction patterns, and operator reputation.
  • New: Added agent_metadata object to the response with fields for operator, framework, and deployment_date.
  • Improved: Webhook retry schedule extended from 4 attempts to 6 attempts over 10 hours. Failed events are now retained for 30 days in the dashboard.
  • New: Added X-Vizi-Delivery-Attempt header to webhook requests, indicating which retry attempt is being made (1–6).

v2.1 — Webhook Signatures

November 2025
  • New: HMAC-SHA256 webhook signature verification via X-Vizi-Signature header. All webhook endpoints now require signature validation.
  • New: POST /v2/monitoring/subscriptions endpoint to subscribe to score changes for any wallet address with configurable thresholds.
  • New: score.threshold.crossed webhook event type, fired when a monitored score crosses a user-defined boundary.
  • Improved: Score computation latency reduced by 40% through parallel chain indexing.

v2.0 — Multi-Chain Scoring

September 2025
  • New: Complete API redesign with versioned endpoints under /v2/. RESTful resource structure, consistent error codes, and pagination via cursor tokens.
  • New: Multi-chain scoring across Ethereum, Polygon, Arbitrum, Optimism, Base, Avalanche, BNB Chain, and Solana. Scores automatically aggregate cross-chain activity.
  • New: Merchant Score and Institutional Score endpoints for specialized use cases.
  • New: Official SDKs launched for Python, Node.js, Go, and Rust with full type safety and automatic retries.
  • New: Sandbox environment with simulated wallets and zero rate limits for testing.

v1.5 — Score Monitoring

July 2025
  • New: Score monitoring dashboard with real-time alerts for tracked wallet addresses.
  • New: score.updated webhook event type for receiving score change notifications.
  • Improved: Score response time reduced to under 200ms for cached addresses (previously 500ms).
  • Improved: Added Polygon and Arbitrum chain support to the scoring model.

v1.0 — Initial API Launch

March 2025
  • New: GET /v1/score/{address} endpoint for Ethereum wallet credit scoring on the 300–850 scale.
  • New: Score factors breakdown including wallet age, repayment history, collateral health, protocol diversity, and liquidation history.
  • New: API key authentication with rate limiting at 60 requests per minute.
  • New: VIZIScan free lookup tool launched alongside the API.

Deprecation Schedule

We provide at least 6 months notice before removing any endpoint or field. Currently deprecated items:

GET /v1/score

Deprecated October 2025. Removal date: June 1, 2026. Migrate to GET /v2/scores/{address}. The v2 endpoint returns the same data with additional fields and multi-chain support.

chain query parameter

Deprecated September 2025. V2 endpoints auto-detect the chain from the address format. No migration needed — simply remove the parameter from your requests.

Versioning Policy

VIZI follows semantic versioning for the API. Major versions (v1, v2, v3) may include breaking changes. Minor versions (v2.1, v2.2) are always backward-compatible and add new features or fields without removing existing ones.

When we release a new major version, the previous version remains available for at least 12 months. We will never remove an endpoint without at least 6 months of deprecation notice, and we will send email notifications to all affected API key holders.

You can specify the API version in your request URL (/v2/scores/...) or via the X-Vizi-Version header. If no version is specified, requests default to the latest stable version.

Stay Updated

Subscribe to the VIZI developer newsletter for release announcements, migration guides, and breaking change warnings delivered to your inbox.

API Documentation Contact Us