When will Martini have a public API?

The planned public API surface covers the core operations on the platform: create and manage projects, list and retrieve canvas state, trigger generations programmatically, retrieve outputs, and receive webhook callbacks for async jobs. The shape will look like other modern AI APIs — REST, JSON request and response bodies, signed URLs for assets, idempotency keys on mutations, and standard rate-limit headers. Authentication via API keys scoped to a workspace.

Out of scope for the first release: real-time canvas collaboration over the wire (those primitives are internal), workspace billing administration, and direct access to the underlying provider keys (BYOK is a separate roadmap item). The first release prioritizes the use cases that justify pulling automation into the platform: scheduled generation runs, integration with content management systems, downstream pipelines for delivery.

Public API design is hard to undo. The team is being deliberate about request and response shapes, error semantics, and rate limit policy because once those ship, breaking changes become extremely expensive. Recent platform work — credit accounting, async job orchestration, webhook delivery, workspace billing — is the foundation that the public API sits on top of, and several pieces are still being hardened in production.

The other reason is sequencing. Martini's first wave of users is the canvas-driven creative workflow, where the GUI is the value. API-first use cases are the next wave — automating delivery, integrating with downstream tools, scheduled runs at scale. Shipping the API before the core canvas product hardens would split team focus on a smaller user surface. The roadmap is sequenced to ship the API once the underlying primitives are stable.

Enterprise contracts can include API access today as part of a bespoke arrangement. The available endpoints today are smaller than what the public API will eventually offer, but they cover the most common use cases: triggering generations programmatically with webhook callbacks, listing recent jobs by project, downloading outputs via signed URLs, and managing workspace credit pools. The exact endpoint set is documented in the enterprise contract.

Enterprise API access typically pairs with priority queue access on flagship video models, custom rate limits, and dedicated support during integration. If your team is building a downstream pipeline that depends on Martini, enterprise is the path to a contract that survives the consumer-API roadmap timeline. Email enterprise@martini.art with your use case to scope what is available.

For consumer API early access, watch the changelog and the product announcements via the help icon notifications. When an early-access program opens, it will be announced there and through email to opted-in users. There is no separate waitlist URL today; the team prefers to talk directly with the first cohort of integrators rather than batch-process applications.

For enterprise API access today, email enterprise@martini.art with your use case, expected monthly volume, and integration timeline. The team responds within one business day. The conversation usually involves a demo, a scoping call to align on which endpoints your integration actually needs, and a custom contract that includes the API and any other features required (SSO, SLA, regional routing).