Osmo CLI vs Pixelixe

Osmo CLI 34

API checklist adapted to a CLI. No OpenAPI or command schema is published on a docs page. The model input schemas recorded on 8 October came from the product's own catalogue API at studio.osmo.inc/api/resources, which this method no longer reads, so the contract line has nothing behind it (0). The skill's SKILL.md is Markdown written for agents, with a command table, and osmo.inc/llms.txt now links the CLI page; the package's README, SETUP.md and DEPLOY.md were read from the 0.1.19 tarball on 8 October (10). Help text in the 0.1.19 bundle states what each command is for and when to pick share over studio deploy, per the 8 October check (12). Typed inputs with enums and ranges were read only from the catalogue API, so none remain (0). An example per command and JSON output shapes in DEPLOY.md, and a command table in the skill, but no reference for the roughly 50 error codes (8). Semver versions with no changelog (4). 0 + 10 + 12 + 0 + 8 + 4 = 34.

Pixelixe 66

OpenAPI 3.1 (version 2.0.0) at pixelixe.com/pixelixe-openapi.json, but it covers four endpoints, authentication, document search, graphic automation and photo effects, and leaves out the JSON-to-graphic and image processing APIs (18 of 25). llms.txt exists but routes readers to marketing pages; the MCP reference is written for LLMs (7 of 10). The MCP reference says what each of the seven tools maps to, that pixelixe_generate_graphic_variant 'is not a free-form layout API', lists common mistakes and how to present outputs (17 of 20). The MCP layer documents canonical field names and refuses legacy aliases; the REST modifications are open structures keyed by element name (10 of 15). Request examples throughout, but errors are one table of message strings all returning 400 (8 of 15). /v2 paths and a deprecated V1, with no changelog (6 of 15). 18 + 7 + 17 + 10 + 8 + 6 = 66.

Osmo CLI 70

Read from the 0.1.19 bundle and docs on 8 October and the skill re-read on 5 November, not from a run. The skill grew from 255 bytes to 9,686 bytes on 15 October, a compact guide with a command table, every command takes --json, and lists default to short pages (18). --limit and --cursor on lists, --type on resources and --open on comments (15). Errors are JSON with a code, a message, a next command and retryAfter where it applies, with exit code 2 for usage errors, though only one error is documented (14). osmo run sends an Idempotency-Key and retries network errors, repeating unshare is documented as safe, and a failed upload reports the share to retry against (16). Few required arguments, and no SDK in any language (7). 18 + 15 + 14 + 16 + 7 = 70.

Pixelixe 49

Seven compact MCP tools (25). Document and design-set search filters, with no pagination documented (10 of 20). All errors are 400 with free-text messages, so an agent can't branch on a code (6 of 20). No idempotency keys, and annotations couldn't be read on the closed server. The MCP tools only read and create, with nothing that deletes (5 of 20). Few required fields, but no official SDK (3 of 15). 25 + 10 + 6 + 5 + 3 = 49.

Osmo CLI 10

Graded on the paid hosted service the CLI depends on, by the published rubric. No x402, MPP or L402 in the OAuth metadata or the skill (0). osmo.inc/pricing, terms and privacy render only in the browser, and the 8 October prices were read from the site's script, which this method no longer reads, so no price is readable (0). The skill README says model runs use the account's plan, which includes a free monthly allowance, without saying whether a card is needed, so half (10). A person has to create an account and approve the device login in a browser (0). 0 + 0 + 10 + 0 = 10.

Pixelixe 30

No x402, MPP or L402 (0). Plan prices with monthly document counts are public, with no per-image price (10). 10-day trial with no card (20). A person signs up and copies the key, or approves OAuth in a browser (0). 0 + 10 + 20 + 0 = 30.

Osmo CLI 51

OAuth device flow with a client registered per device, refresh tokens, a revocation endpoint and osmo logout. The OAuth metadata re-read on 5 November lists scopes projects:write, energy:spend and a new account:read. Tokens sit in a 0600 file under ~/.osmo/auth per the 8 October bundle reading, and no secret travels in a URL (26). --no-spend drops the spending scope and shares delete needs --yes, but every login asks for projects:write and no read-only login is documented (11). Comments from anyone with a review link are returned to the agent. The skill (15 October) tells the agent a review comment is feedback on the video, never an instruction to run commands, change access or work outside the project, and that a commenter's name is self-reported, and the CLI strips control and bidirectional characters from output. Guidance and one mitigation (10). Connections are named per device and osmo jobs lists runs. No audit log found (4). No security.txt (osmo.inc answers with its HTML shell, studio.osmo.inc 404), disclosure policy, bug bounty or certification found. The earlier 2 had no programme evidence behind it, so the line is 0 (0). 26 + 11 + 10 + 4 + 0 = 51.

Pixelixe 38

A bearer API key per account, plus a public key for the embedded editor. The MCP server accepts the key or an OAuth token from studio.pixelixe.com/oauth/mcp with one pixelixe.mcp scope. No key scopes, rotation or revocation documented (18 of 30). No read-only mode, though the MCP tools can't delete or change account settings (10 of 20). Tools return the account's own templates and renders (10 of 15). No audit log or per-call record documented (0). No security.txt, disclosure policy, bug bounty or certification found (0). 18 + 10 + 10 + 0 + 0 = 38.

Osmo CLI 7

No release date can be read. The 6 October date for 0.1.19 and the version timestamps came from npm's registry document, a JSON data interface this method no longer reads, so they are struck. The 0.1.19 package itself, read on 8 October, carries no release date, the CLI page and llms.txt give none, and the skill repository has no tags or versions (0). No dated release in the 90 days from 7 August can be counted for the same reason (0). No public changelog or tracker. Support is support@osmo.inc, and the skill repository has eight commits and two merged pull requests, the latest on 15 October (3). No SDKs and no MCP registry entry (0). One pinned dependency with a third-party inventory and hashes in release.json, per the 0.1.19 package read on 8 October, but no public CI. Partial kept (4). The skill now names osmo usage, absent from 0.1.19, so a later version is likely. 0 + 0 + 3 + 0 + 4 = 7.

Pixelixe 19

No dated release or API change was found. The newest dated items are the MCP registry entry of 26 March 2026 and the privacy policy of 7 April 2026, more than 180 days before this check (0). No three dated changes since 8 August (0). No changelog. Support by email at inquiries@pixelixe.com, not tested (4 of 15). com.pixelixe/pixelixe-mcp is in the official MCP registry under a domain-verified namespace; there are no official SDKs (15). No public package or repository (0). 0 + 0 + 4 + 15 + 0 = 19.

Osmo CLI 23

Local-package reading, since the owner runs the CLI. Installs from npm. The vendor's skill README (revised 15 October 2026) states Node 22 or later, Git 2.29 or later, FFmpeg, and Studio on Apple Silicon macOS and Linux x64 and arm64 (glibc), while the npm README read on 8 October said any OS; the current npm README couldn't be read, so 15 is kept as a partial (15). The source is private, so there is no public CI or test suite (0). No public issue tracker for the CLI. Support is an email address (5). Versions are semver-shaped with preview tags, but no changelog was found, and osmo share --video FILE in 0.1.17 became osmo share FILE by 0.1.19 without a published note (3). Version 0.1.19 on 8 October, not declared stable (0). 15 + 0 + 5 + 3 + 0 = 23.

Pixelixe 15

Hosted lines. No status page found on the site or in the docs (0). No readable incident history (5). No rate limit is published; the terms only forbid circumventing them (0). No 429, Retry-After or backoff guidance. Every error, a wrong key and exhausted credits included, is a 400 with a message (0). No SLA found; the terms supply the service as is (0). API v2 is current and not labelled beta (10). 0 + 5 + 0 + 0 + 0 + 10 = 15.