Aevum Zenth SDK

A unified, type-safe developer toolkit for interacting with the Aevum Zenth enterprise ecosystem. Access cross-divisional data, automate workflows, and integrate with 400+ subsidiaries using a single interface.

Installation

Install the SDK using your preferred package manager. The SDK supports Node.js 18+, Python 3.9+, and Go 1.21+.

npm
pip
go get
# Node.js / TypeScript npm install @aevumzenth/sdk-js
# Python pip install aevumzenth-sdk
# Go go get github.com/aevumzenth/sdk-go

Configuration & Authentication

Authentication is handled via API keys or OAuth 2.0 service tokens. Configure the client using environment variables or direct injection.

// .env.local AEVUM_API_KEY="ak_live_8xK9mP2vQ7wR5tY3nB1cD4eF6gH0jL" AEVUM_REGION="us-east-1"
⚠️ Security Notice Never commit API keys to version control. Use secret management tools or environment variables in production environments.

Quick Start

Initialize the client and fetch real-time telemetry from the Aerospace division.

import { AevumClient } from "@aevumzenth/sdk-js"; const client = new AevumClient({ apiKey: process.env.AEVUM_API_KEY, timeout: 5000, retries: 3 }); // Fetch satellite constellation status const telemetry = await client.aerospace.getConstellationStatus({ orbit: "LEO", metrics: ["signal_strength", "power_draw"] }); console.log(telemetry.active_nodes); // Output: 142

API Reference

Client Initialization

The main entry point for all SDK interactions. Supports cross-divisional routing, automatic retries, and request logging.

Parameter Type Required Description
apiKey string Yes Production or sandbox API key from the developer portal
region string No Data residency region (defaults to auto)
timeout number No Request timeout in milliseconds (default: 3000)
retries number No Automatic retry attempts on 5xx errors (default: 2)

Division Endpoints

The SDK exposes dedicated namespaces for each major division. All methods return typed promises and support streaming responses where applicable.

  • client.energy.grid() - Smart grid load balancing & metering
  • client.healthcare.pharma() - Clinical trial data & supply chain
  • client.aerospace.defense() - Orbital telemetry & defense contracts
  • client.logistics.freight() - Autonomous routing & warehouse IoT
  • client.capital.wealth() - Institutional trading & portfolio analytics

Real-time Data Streams

Subscribe to WebSocket feeds for live telemetry, market data, and industrial IoT events across all divisions.

const stream = client.subscribe("energy:solar:output", { regions: ["NA", "EU"], frequency: "1s" }); stream.on("data", (packet) => { console.log(`Node ${packet.id}: ${packet.mwh} output`); }); stream.on("error", (err) => { console.error("Stream disconnected:", err); });

Error Handling

The SDK throws typed error classes for predictable failure handling. All network errors include retry metadata and correlation IDs.

🔍 Debugging Tip Enable verbose logging by setting DEBUG=aevumzenth:* in your environment to trace request/response cycles.
Error Code Status Description
AUTH_INVALID 401 API key missing, expired, or lacks division scope
RATE_LIMITED 429 Exceeded division-specific request quota
STREAM_TERMINATED 410 Requested data feed has been deprecated or rotated
GATEWAY_TIMEOUT 504 Downstream division service unresponsive
try { await client.energy.deploySmartContract(payload); } catch (err) { if (err instanceof AevumRateLimitError) { console.warn(`Retrying in ${err.retryAfter}ms`); } else if (err instanceof AevumAuthError) { console.error("Token scope mismatch. Check dashboard."); } }

Rate Limits & Quotas

Requests are rate-limited per API key and division tier. Limits reset on a rolling window basis. Webhook events do not count against standard quotas.

  • Free Tier: 100 req/min, 10k req/day
  • Pro Tier: 2,000 req/min, unlimited
  • Enterprise: Custom limits, dedicated instances, SLA-backed
💡 Best Practice Implement exponential backoff with jitter when handling 429 responses. The SDK includes a built-in retry queue for most methods.

Changelog

v2.4.1 (2026-03-18)

  • Fixed WebSocket reconnection logic for high-latency regions
  • Added TypeScript 5.3 support and strict mode compliance
  • Optimized pagination cursors for logistics.freight()

v2.4.0 (2026-02-22)

  • Introduced client.capital.wealth() namespace
  • Added streaming support for real-time market data
  • Bumped minimum Node.js requirement to 18