# Ltx — API Agent Score

> Score: 57/100 (Grade: D) | Domain: ltx.io | Rubric: 1.0.0 | Checked: July 29, 2026

Ltx scored 57/100 (D), classified "not-ai-ready".

[View full report](https://www.postman.com/ai/ai-ready-apis/company/ltx)
[All organizations](https://www.postman.com/ai/ai-ready-apis/llms.txt)

## Summary

- Overall: 57/100 (D)
- Classification: not-ai-ready

## Category Scores

- API Design: 45/100 (F)
- Developer Experience: 72/100 (B)
- Agent Discovery: 91/100 (A+)
- Agent Understanding: 61/100 (C)
- Agent Usability: 40/100 (F)

## Check Results

### API Design

- [pass] Example coverage — Code samples in 3 language(s) across docs (top: shell, python, javascript); 1/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%, sdk 0%.
- [fail] Schema coverage & depth — no .d.ts found. Investigated: sdk 0%.
- [fail] Security & governance hygiene — No security.txt at /.well-known/security.txt or /security.txt. Investigated: wellknown 0%.
- [skip] Machine-readable, versioned contract — No surface produced evidence for this capability in this run.
- [skip] Auth declared & discoverable — No surface produced evidence for this capability in this run.

### Developer Experience

- [pass] Quickstart present — Quickstart at https://docs.ltx.io/quickstart with a runnable first-call sample. Investigated: docs 100%.
- [pass] Code samples in docs — Code samples in 3 language(s) across docs (top: shell, python, javascript); 1/20 pages have ≥ 2 languages on the same page. Investigated: docs 100%.
- [pass] Changelog published — Newest official SDK activity 21 day(s) ago. Investigated: sdk 100%.
- [fail] Self-service developer portal — Signup page is sales-gated (contact-sales/request-access language detected). Investigated: docs 0%.
- [skip] Description completeness — No surface produced evidence for this capability in this run.

### Agent Discovery

- [pass] Docs reachable, not hard auth-gated — All 1 pages are publicly accessible. Investigated: docs 100%.
- [pass] Registry & SDK presence — Indexed on Context7 (lightricks/ltx-2, 550 snippets). Investigated: docs 100%, sdk 63%, cli 0%.
- [warn] llms.txt present, valid & comprehensive — llms.txt covers 0/1 sitemap doc pages (0%); 1 missing. Investigated: docs 75%.
- [warn] Crawlable / AEO — Sitemap lastmod coverage 56% or newest entry older than 90 days. Investigated: wellknown 75%.

### Agent Understanding

- [warn] Agent-navigable, token-efficient docs — 2 of 4 endpoints have aggressive caching or missing cache headers. Investigated: docs 90%.
- [fail] Agent instructions file (AGENTS.md) — No AGENTS.md at the site root or /.well-known/. Investigated: wellknown 0%.
- [fail] Docs structured data — Neither JSON-LD nor OpenGraph/meta tags detected across 3 assessed pages (3 JS-rendered). Investigated: docs 0%.
- [skip] Machine-readable errors (RFC 9457) — No surface produced evidence for this capability in this run.
- [skip] Operation purpose clarity — No surface produced evidence for this capability in this run.
- [skip] Description consistency across surfaces — Only 1 surface description(s) with ≥6 tokens available; need at least 2 to compare.

### Agent Usability

- [fail] Runnable collection with test scripts — No public Postman workspace discovered for the org. Investigated: platform 0%.
- [skip] Idempotency documented — No surface produced evidence for this capability in this run.
- [skip] Rate-limit signaling — No surface produced evidence for this capability in this run.
- [skip] Pagination documented & consistent — No surface produced evidence for this capability in this run.
- [skip] Sandbox separation — No surface produced evidence for this capability in this run.

## Executive Summary

Ltx's API discovery is a genuine strength — partners and agents can find your APIs without friction. However, the program has two critical gaps that will stall partners before they write a line of integration code: the API contract lacks the schema depth and security definitions that both human developers and AI agents need to build confidently, and there is no runnable, test-backed collection giving agents or partners executable proof of how the API actually behaves. Closing these two gaps, alongside adding structured agent context and a self-service portal, will move the program from a discoverable-but-hard-to-adopt state to one where partners and their agents can go from discovery to working integration without any manual hand-holding.