Plan simple, readable motion for the two Pika labels in the website catalog, while treating their unidentified app proxy as an unresolved integration boundary. Pika’s own platform and developer documentation do not establish which editing, sound or duration controls that proxy supports.
Editorial starting points, not a performance ranking. Check current app access before choosing a model.
Plan a short illustrated motion test
Use the existing guide to understand this owner-audited app label before writing a simple shot brief. Pika’s public resources cover creating and editing video, but the reviewed developer introduction does not supply a verified 2.2 contract for this app proxy.
Tradeoff: The app card’s five-second label is not an independently confirmed provider maximum. This is an editorial workflow suggestion, not a model-performance claim or a verified effects list.
Pika’s official developer introduction links a 1.5 prompting guide and describes version selection. If the audited app option is available, compare a simple physical action using the same visual requirements as another choice.
Tradeoff: The app’s three-second card label and unknown proxy contract limit what can be asserted. Do not infer current Pika platform features, retirement status or a lower price from the older version number.
Official documentation describes the named model or gateway—not every feature available in this app.
Version selection does not identify the host
Pika’s developer introduction describes modelVersion and links version-specific prompting resources. That establishes a version concept in Pika’s own API, not the exact endpoint, accepted fields or version translation used by EZ Ai Assist’s unidentified third-party proxy. The missing mapping is intentionally not filled with another host’s schema.
Pika’s help center organizes questions about video length, resolution, editing and effects, but the reviewed index does not establish those values for the audited 2.2 or 1.5 route. Resolution, reference inputs, generated sound and advanced effects therefore remain unverified for this integration rather than becoming an invented specification table.
Pika’s own developer documentation guarantees generated-video storage for only 30 days, after which files may be deleted. This is a direct-provider retention statement, not a verified EZ Ai Assist storage policy. Download useful output and confirm your app’s retention behavior separately instead of assuming any remote preview is permanent.
Every existing catalog entry for this provider is linked below. Status labels come from the individual website guides; catalog coverage is not a guarantee of current app access. Historical and snapshot pages remain references, not extra active models.
Original prompt examples, not generated-output demonstrations. They have not been generation-tested.
Workflow 1
Animate one readable story beat
Start from a short written scene with one subject and a fixed viewpoint. Do not depend on a named Pika effect, an audio switch or a reference upload unless your current app interface explicitly supports it.
In an original paper-cutout scene, a small turquoise mailbox opens slightly and one cream envelope rises just above the opening. Hold a fixed front three-quarter camera view. Preserve the mailbox shape and paper texture, use soft studio light and stop with the envelope visible. Add no letters, hands, extra mail or scene transition.
Check the result: Check that the action is understandable without sound and that the mailbox does not transform. Measure actual clip length rather than relying on the card label.
Use a low-complexity brief so failures are easy to identify. Save the same brief for any later comparison, but record the selected option rather than claiming a verified upstream benchmark.
A small cobalt pinwheel stands in a terracotta pot on an empty cream shelf. Its paper blades turn gently in a light breeze while the pot and camera remain still. Use clean illustrated shapes, consistent daylight and a plain pale-blue wall. Keep every blade attached and add no text, people, extra objects or abrupt cuts.
Check the result: Look for detached blades, changing object counts and unintended camera motion. Keep only a clip that remains coherent from its first frame to its last.
Official Pika documentation was reviewed, but it does not identify the app’s serving proxy or verify a Pika 2.2 request schema for that route. App labels and card durations come from owner audits labeled October 9, 2026, not live generation tests. Unverified controls remain unverified.
Owner audit · October 9
What the owner audit establishes
The application audit lists Pika 2.2 and Pika 1.5 choices and records five-second and three-second card labels respectively. Those are interface observations, not independently verified provider limits or guaranteed output durations.
Unidentified third-party proxy
What the audit does not establish
The serving identity, exact endpoint, final request shape and accepted version values remain unresolved. This page does not claim the app uses Pika direct, Fal or any other publicly documented reseller merely because one offers a similarly named model.
Not live-tested
What to check in a future integration review
A targeted app-side review would need to confirm model translation, input media requirements, duration and ratio forwarding, sound behavior and durable output storage. No such handler inspection or paid generation occurred in this website-only work.
Before you rely on a result
Limits, costs and tradeoffs
Pika’s current product may include tools beyond these two catalog labels. Shared branding is not evidence that a specific older model or unknown proxy exposes every current effect, editor or sound feature.
Timing, seamless loops and consistent anatomy are creative targets, not guaranteed output properties. Plan to review and edit the returned clip, especially for a public campaign or a scene involving people.
Proxy pricing is unverified. Pika subscription credits, another gateway’s rates and the amount charged inside EZ Ai Assist must not be treated as interchangeable.
Compare prompt-led video routes whose hosting identities and documented request modes are available for review.
Common questions
Pika, without the assumptions
Why does this guide avoid a resolution claim?
The owner audit does not establish the proxy’s exact output contract, and the cited general Pika resources do not resolve it. A precise-looking number borrowed from another host would be misleading.
Are the five- and three-second figures guaranteed?
No. They are the owner-audited app card labels for 2.2 and 1.5. Provider maximums, effective request settings and returned lengths were not independently verified for the unknown proxy.
Can I use current Pika effects through these choices?
That is not established. Named effects and platform tools can have their own versions and endpoints. This page offers simple original scene briefs without promising that those separate features are connected to the app.
Highlighted provider contracts reviewed . Individual model guides carry their own review dates. Sources can change; these pages do not perform live health checks.
Official Pika documentation was reviewed, but it does not identify the app’s serving proxy or verify a Pika 2.2 request schema for that route. App labels and card durations come from owner audits labeled October 9, 2026, not live generation tests. Unverified controls remain unverified.