Changelog & Versioning

Versioning Policy

The API is versioned with a URL prefix (/v1/). All breaking changes require a new version prefix.

What is a breaking change

  • Removing or renaming a field in a request or response schema
  • Changing the type or semantics of an existing field
  • Removing an endpoint
  • Changing authentication requirements
  • Removing a design_mode or output_format value

What is NOT a breaking change

  • Adding new optional request fields with defaults
  • Adding new fields to response objects
  • Adding new design_mode or output_format values
  • Improvements to generation quality with no schema changes
  • Changes to internal pipeline behavior that don't affect the API contract

Deprecation Process

  1. Deprecated fields are flagged in documentation at least 6 months before removal
  2. The API response may include a deprecation warning in error_message for affected requests
  3. Removal is announced via email to all active API key holders and posted to the status page
  4. A new version prefix is introduced if the change is breaking

Changelog

v1.0.0 — 2026-05-30

Initial public API release.

Endpoints:

  • POST /v1/text-to-cad — Generate CAD from a text prompt
  • POST /v1/image-to-cad — Generate CAD from reference images
  • GET /v1/jobs/{job_id} — Poll a job for status and result
  • GET /v1/jobs — List jobs with cursor pagination
  • GET /v1/healthz — Liveness probe

Supported design modes: standard, pro, assembly (text); standard, assembly (image)

Supported output formats: STEP, STL, GLB, 3MF

Features:

  • Async job lifecycle with status polling and optional HMAC-signed webhooks
  • callback_url optional — use polling or dashboard as alternatives
  • Idempotency key support on POST requests
  • brainstorm object returned with every successful job
  • Cursor-paginated job list
  • output_expired error code on 410 responses for expired files (>30 days)

Status Page

status.makistry.ai — real-time uptime, incident history, and maintenance windows.

Support

For API questions, integration help, or to report a bug: parthm@utexas.edu