Exa · Launch Video Breakdown: Hook, Pacing & Motion Design

Scene-by-scene timeline & spoken transcript

1. 0:00 – 0:03

   The Hook

   Exa Integrates with Codex

   “(No spoken dialogue — Driving electronic pulse with evolving synth pads.)”

   On screen

   Exa is now in Codex

   Camera

   Static, centered text on a light background.

   Motion

   Text typing animation, followed by a highlight and pixelated cursor interaction.

2. 0:03 – 0:06

   Problem Agitation

   Complex API Research Query

   “(No spoken dialogue — Electronic pulse continues, building subtle tension.)”

   On screen

   Exa Find companies that launched an API and later substantially redesigned it based on developer feedback. Show me what changed.

   Camera

   Close-up on a UI text input field, with a subtle background pattern.

   Motion

   Typing animation within a search bar, simulating user input.

3. 0:06 – 0:17

   Product Reveal

   Exa's Web Search and Analysis

   “(No spoken dialogue — Rhythmic electronic pulse with evolving synth pads, maintaining energy.)”

   On screen

   Web search Exa... Thinking... 12 subagents reviewed companies fro... https://aws.amazon.com/blogs/compute/configuring-cors-on-amazon-api-gateway-apis/ ... Find API redesign case studi... Worked for 2m 49s > I used Exa to review 291 returned sources across four search workstreams. After deduplication, I kept eight cases where the evidence explicitly connects developer feedback to a material redesign. Company Feedback signal What changed Webflow Developers reported inconsistent errors, webhook payloads, permissions, naming, and surprising behaviors. Webflow consolidated complaints from Slack, X, and internal teams into an "API papercuts" audit. The Data API moved from fragmented, team-specific conventions to standardized naming, errors, status codes, pagination, webhooks, and OpenAPI definitions. V2 also introduced granular scopes and new tokens, replacing wholesale site authorization. ZITADEL Customers repeatedly struggled to determine whether a task belonged in the Auth, Management, Admin, or System API. V2 reorganized the API around resources—Users, Organizations, instances—rather than user personas. The same endpoint now returns data scoped by the caller's permissions, removing duplicate role-specific operations (migration guide). HubSpot Surveys and direct comments identified the API as a major developer pain point. Nearly 500 endpoints had accumulated incompatible naming, models, parameters, and interaction patterns. The v3 APIs imposed common conventions for URL and object structure, pagination, batch operations, archive/restore behavior, CMS revisions, and CRM properties and associations. CRM API v3 became the first GA component in March 2020. Twitch Developers complained about reliability, silent breakin changes, polling-heavy access patterns, and inconsi cy caused by the old API's tight coupling to Twitch's website. Twitch started from a blank slate: universal cursor pagination, query-string parameters, bulk GET operations, consistent data models, public release stages, and a visible roadmap. It later requested Plaid Developers using Transactions overwhelmingly maintained The new /Transactions /sync interface replaced date-window fetching and manual reconciliation with a cursor-based change feed of added, modified, and removed transactions. Plaid and a new API sure compared that changing rollout percentage unnecessarily triggered a new review. status, cancellation or pending submissions, staged publishing, rollout changes without resubmission, clearer resource models, and a discovery document for generated tooling. AWS After operating API Gateway's REST APIs since 2015, AWS applied usage lessons and customer feedback to a ground-up alternative. HTTP APIs simplified routes, integrations, JWT authorization, CORS, and deployment. AWS reported up to 60% lower latency and at least 71% lower cost than REST APIs. This was a streamlined replacement option rather than a forced REST API v2. Exa X said the previous "one-size-fits-all" platform did not scale with developers' projects and had withheld important product capabilities. API v2 rebuilt the foundation, unified previously separate products under tiered access, and added product tracks for standard apps, research, and businesses. It exposed conversation threads, polls, pinned tweets, real-time streams, spam filtering, and stronger search/filtering (contemporary corroboration). The recurring pattern is that feedback rarely produced isolated endpoints. It exposed a faulty underlying abstraction: Role-specific APIs became resource-oriented APIs. Snapshot retrieval became change feeds. Product-internal schemas became stable public contracts. Global versioning became resource-level or explicitly tiered evolution. Broad authorization became granular scopes. I excluded examples such as Dropbox API v2 where the redesign was clearly substantial but the surviving first-party material mostly solicits feedback during the beta rather than clearly demonstrating that prior developer feedback caused the redesign. Do anything Full access 5.6 Sol High

   Camera

   Zoom out from the search bar to reveal a full application window, then a vertical scroll through detailed search results.

   Motion

   Rapid text generation, sequential list item reveal, and smooth vertical scrolling to showcase extensive data processing.

4. 0:17 – 0:23

   Call to Action

   Exa: Available Now

   “(No spoken dialogue — High-energy audio transition/riser from 00:20 to 00:22, culminating in a sub-bass drop/impact at 00:22. Electronic drum beat and deep sub-bass.)”

   On screen

   Exa is available in Codex exa

   Camera

   Static, centered text on a dark background, transitioning to a static logo reveal.

   Motion

   Color change on text, followed by a hard cut to a clean, white logo on a black background, timed with the audio impact.