Pika API vs sync. labs MCP server

Pika API 10

Model reading. The API launched on 4 August 2026, per Pika's API Club post and the launch release, and the terms were updated the same day. No dated change since was found on 1 October, and the site couldn't be re-read on 5 November under Pika's terms. The launch is 93 days old (10; 20 on 1 October, cause time). Too new for a deprecation record, and no policy found (0). No changelog or public support channel found (0). No official SDK (0). Nothing to assess for package health (0).

sync. labs MCP server 75

v0.2.4 and commits on 7 November 2026 (30). Three tags in recent weeks (20). Issues not read (0). Official registry entry io.github.synchronicity-labs/mcp-server (15). CI with verify, publish and review workflows (10). 30 + 20 + 0 + 15 + 10 = 75. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.

Pika API 45

No published contract can be shown. The OpenAPI 3.1 file at dev.pika.art/openapi.json was never recorded as linked for download from a docs page, the keyless catalogue's schemas are served by the product's own API, and Pika's terms now bar us from reading the site, so the file no longer counts (0; 25 on 1 October). A detailed llms.txt (10). llms.txt walks through discovery, quote, submit, poll and webhooks, but per-model guidance on when to use which operation is thin (15). Typed input schemas per operation were read on 1 October from the catalogue, which the product's own API serves, so that reading no longer counts; llms.txt says the catalogue returns them, with prices quoted before you submit, but prints none (0; 13 on 1 October). Error codes 401, 403, 409, 413, 415, 422, 429 and 503 are each explained with the action to take, and the docs carry request examples (15). Versioned /v1 paths, but no changelog (5). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

sync. labs MCP server 81

Tools generated from the public API specification plus workflow tools, with typed schemas in the source (25). llms.txt and .md pages (10). Tool table with descriptions (14 of 20). Typed from the API spec (12 of 15). Examples and an estimates tool; errors not documented (8 of 15). Tags v0.2.2 to v0.2.4 and dated commits (12 of 15). 25 + 10 + 14 + 12 + 8 + 12 = 81.

Pika API 80

Jobs are small JSON objects with media by URL, and signed webhooks (Standard Webhooks, retried for about 55 hours) remove polling (25). Resolution and duration control output size (10). No job list endpoint found, only a list of webhook deliveries (0 of 10). Errors say what to do, for example check the balance on a 403 and send a fresh key on a 409 (20). Idempotency-Key on submits, and a reused key with a different body returns 409 (20). Few required fields, but no official SDK (5). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

sync. labs MCP server 55

A generated catalogue filtered by client profile, curated for ChatGPT (15). Project history and estimates (12 of 20). Recovery tools; errors not documented (8 of 20). Annotations not read (5 of 20). OAuth or a key, npm package and library use (15). 15 + 12 + 8 + 5 + 15 = 55.

Pika API 20

No x402, MPP or L402 (0). Live per-operation prices from a keyless catalogue, and quotes are free and need no key, $0.04 a second for Pika 2.5 at 720p (20). No free generation tier. The $10 monthly membership includes a $10 credit in the first month but needs a card (0). Browsing and quoting are keyless, but generating needs a person to sign up and pay (0). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

sync. labs MCP server 30

No machine payment protocol (0). Per-second prices published (20). A free try for short videos (10 of 20). A person signs up (0). 0 + 20 + 10 + 0 = 30.

Pika API 35

No status page. The homepage makes an uptime claim but links no status page (0). No incident history to read (5). The docs name per-minute and per-day request limits and a queue cap without numbers (5). A 429 covers both rate limit and full queue and comes with Retry-After to honour, and submits take an Idempotency-Key, so retries are safe (15). No SLA published (0). Launched on 4 August 2026 with no beta label (10). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

sync. labs MCP server 43

Status page at status.sync.so with maintenance and previous incidents (20). History not read (5). No MCP limits found (0). The source has abort-signal handling and recovery guidance for long jobs (8 of 15). No SLA found (0). Version 0.2.4, not labelled beta (10). 20 + 5 + 0 + 8 + 0 + 10 = 43.

Pika API 33

Model reading of the checklist (credential, training, retention, operator visibility, programme). API keys created at dev.pika.art/keys, sent as X-API-Key or bearer, and an inactive key is refused. No scopes found (20). The terms of 4 August 2026 let Pika use anonymised or aggregated inputs and outputs to train its models, with no opt-out stated (0). Deleting a job erases its stored media and the captured prompt (5). No retention period stated for jobs you don't delete (0). A balance endpoint, a settled charge per job and a webhook delivery log, no audit log (8). No security.txt, bug bounty or certification found (0). Per the 1 October check, not re-read on 5 November, because Pika's terms bar automated access to its websites and their subdomains.

sync. labs MCP server 38

OAuth per organisation, or an API key in the environment (22 of 30). No read-only mode (3 of 20). Media in and out, no third-party text (10). No audit log found (0). No security programme found (3 of 20). 22 + 3 + 10 + 0 + 3 = 38.