Launch Video Library · Devtools · Feature · 2026

Resend Account Usage API

Resend introduced an Account Usage API that allows developers to programmatically monitor email sending limits and remaining quotas.

What Resend shipped

Resend introduced their new Account Usage API, giving developers programmatic access to their email sending quotas. Instead of relying on a dashboard, engineering teams can now query how many emails they have sent, monitor remaining limits, and track reset dates directly from their own code.

The release focuses on practical automation, highlighting integrations with Claude through the Resend MCP and demonstrating how to build usage alerts into a signup flow. This allows teams to trigger Slack or email notifications before hitting a hard limit, preventing dropped messages during traffic spikes.

How the motion works

When showcasing a technical feature like an API, motion designers should consider how to make code blocks visually engaging. A hard-cut approach between terminal outputs and the corresponding code editor keeps the pacing tight and prevents the viewer from getting bogged down in boilerplate syntax. Rather than slowly scrolling through a script, highlighting the specific lines where the Usage API is called draws the eye exactly where it needs to be.

To illustrate the Slack and email notifications mentioned in the release, a punch-in technique works well. By scaling up the notification UI over the code background, the relationship between the backend trigger and the frontend result becomes immediately clear. Easing the scale with a slight overshoot adds a tactile, physical feel to the digital alert.

Kinetic typography can be used to emphasize the core metrics retrieved by the API, such as emails sent versus the remaining quota. Animating these numbers counting up or down alongside the code execution grounds the abstract API call in a tangible result. Cutting on the beat of a subtle background track during these transitions helps maintain momentum throughout a technical walkthrough.

What to steal from it

  • Use a punch-in to visually connect backend code execution with frontend notification results.
  • Employ hard cuts between code blocks and terminal outputs to maintain a brisk pace during technical demonstrations.
  • Animate key data points like quota limits with kinetic typography to make abstract API responses feel tangible.
  • Highlight only the specific lines of code being discussed rather than showing a static, full-screen editor.

Want a video like this for your product?

Impractical cuts one from a single prompt — the same motion craft, in about twenty minutes.