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. A general Public API, public token-issuance flow, and complete remote execution workflow are not available yet.
Start Here#
Download the signed CLI archive from the official Downloads page.
Verify the archive before extracting it.
Run the executable from the extracted directory; there is no system installer in this release.
Inspect the shipped action manifest with
alti commands.Complete the offline CLI First Success preflight and stop at its non-submission receipt.
Continue with CLI for installation and limitations, and Command Reference for discovery.
Current Interfaces#
Interface |
Current use |
Availability |
|---|---|---|
CLI Preview |
Action-manifest inspection and the documented offline job preflight |
Signed Linux x86_64 archive; no system installer or successful installed-capability report |
Packaged |
Stdio process on the user’s machine |
Requires CLI environment configuration and dispatches tool calls through the Cloud client; not local engine execution |
Hosted MCP |
OAuth and discovery edge |
Protected runtime does not currently complete MCP initialization or tool listing |
Desktop browser sign-in |
Licence access for SystemVerilog IDE and ISA Design Studio |
Separate from CLI credentials and automation |
General Public API |
Not available |
No public route, schema, or token-issuance flow is published |
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.