Developer interfaces

Start with the signed CLI Preview and check which developer interfaces are available today.

Overview

The public developer entry point is Altifigence CLI Preview for Linux x86_64. The 0.1.9 interface includes native XLS/CUDA and DDS operations, a verified installation bootstrap, and explicitly scoped Cloud/service connections. Check the download page for release availability before following versioned examples.

Start Here

  1. Download the signed CLI archive from the official Downloads page.

  2. Verify the Ed25519 signatures and pinned key before extracting or executing the download.

  3. Complete Linux installation using the embedded bootstrap.

  4. Check the installed capabilities and use leaf command help.

  5. Follow CLI First Success for CPU XLS execution and the separate offline preflight receipt.

Continue with CLI for installation and limitations, and Command Reference for discovery.

Current Interfaces

Interface

Current use

Availability

CLI Preview

Native XLS, bounded CUDA/RTL, DDS files/Git/settings/authoring/search, and offline preflight

Linux x86_64; authenticated installed layout required for protected local runners

Packaged alti-mcp

Stdio process on the user’s machine

Default customer Cloud mode, or explicit ALTI_MCP_MODE=local-xls for fixed local tools

Native DDS Cloud CLI

Browser PKCE, verified identity, scoped workspace operations/search/terminal

ide cloud; server permissions and operation availability apply

Hosted MCP

Published ChatGPT read tools and scoped Cloud MCP contracts

Five read tools in plugin v1.0.0; expanded tools require release, policy and fresh consent

Desktop browser sign-in

Account and protected-tool access for Digital Design Studio, including ISA

Separate from CLI credentials and automation

General Public API

Use documented typed CLI contracts

Native CLI routes do not imply an unrestricted raw-request API or enable every service operation

A command can still need an installed engine, account permission, or remote service. Check the command page before adding it to automation. The local stdio and hosted HTTP MCP transports also have separate setup and availability.

Choose your first task

Goal

Guide

Evaluate a small function locally without credentials

CLI first success

Automate saved local files, Git or settings

Native engine commands

Access Cloud through the CLI

Authentication and Cloud commands

Let an assistant read a saved project

MCP connection

Add a reproducible CI check

Automation and CI

DDS Plugin Development

Install the SDK and build your first diagnostics plugin with DDS Plugin SDK. Check Marketplace integrations for tool-specific installation, licensing and security information.