MiroMiroMiroMiroAPI
Key
Use case

The animation is on their site. It should be in your project.

Lottie files are the assets nobody can find the source for and nobody remembers to migrate - until the new build is missing them. One call pulls them off any URL.

Get a free API key Try it live
This is for you if

You need a Lottie animation off a live site - to migrate it, to reference it, or to feed it to an agent building something similar.

Lottie files hide

A Lottie animation is a JSON file loaded by a player at runtime, often from a CDN, often with a hashed filename, sometimes assembled by the bundler. There is nothing to right-click. It does not appear in the network tab as anything obviously named. If you did not build the site, finding the file means reading minified JavaScript and hoping.

Which is why they get lost

Every migration has the same moment: the new site is up, and someone notices the little animated checkmark is gone. The source file was in a designer's After Effects project, or an agency's Dropbox, and it is not coming back. The only copy that still exists is the one the old site is serving - right up until the old site goes away.

One call finds them

MiroMiro detects Lottie files on any URL and returns them - the actual JSON, ready to drop into a player. It is our differentiated endpoint: general scrapers do not do it, and brand APIs do not either. It costs 3 credits, and it is the cheapest insurance you will buy on a migration.

How it works

  1. 1

    Point at the URL

    /v1/lottie3 credits

    Any page running a Lottie animation, however it is loaded.

  2. 2

    Get the JSON back

    The actual animation files, not links to hunt down.

  3. 3

    Drop into your player

    lottie-web, lottie-react, dotLottie - it is standard Lottie JSON.

  4. 4

    Or hand it to an agent

    Give a coding agent the real animation instead of a description of one.

bash
curl "https://miromiro.app/api/v1/lottie?url=$SITE" \
  -H "Authorization: Bearer $MIROMIRO_API_KEY"

# → { "lottie": [
#       { "url": "https://cdn…/hero-anim.json", "name": "hero-anim" },
#       { "url": "https://cdn…/checkmark.json", "name": "checkmark" }
#     ] }
#
# 3 credits. The files exist now; after the migration they will not.

What you get: The animation files themselves - recovered from a live site rather than reconstructed from memory.

Common questions

Does it find Lottie files loaded by JavaScript?

Yes. Extraction runs against the rendered page, so animations injected at runtime or pulled from a CDN are detected - which is the whole point, since those are exactly the ones you cannot right-click.

Can Firecrawl or a scraper do this?

No. A scraper returns the page's text or HTML; a Lottie animation is a JSON asset loaded by a player. This is the endpoint no general scraping API has, and it is genuinely the one thing here nobody else offers.

What format do I get?

Standard Lottie JSON - the same thing you would feed lottie-web, lottie-react or a dotLottie player. Nothing proprietary.

Use caseRecover every asset from a site you are about to replaceUse caseRebuild a section of a site you like, in your own stackEndpointLottie Extraction APIEndpointSVG Extraction API

Try it in a minute

100 free credits, no credit card. Point it at a URL and see what comes back.

Get a free API key