Not a screenshot. Not a description. The actual section - resolved from the live CSS and handed back as code you can paste.
You saw a hero, a pricing table, or a feature grid that does exactly what you need, and you do not want to spend an afternoon in devtools reverse-engineering it.
The usual process: open devtools, click through the element tree, copy a class, check the computed styles, notice the color came from a CSS variable three levels up, chase it, find a media query overriding it, start again. Half an hour later you have most of a section and are not sure what you missed. It is tedious work that produces an approximation.
Copying the raw CSS gives you rules, not results. Those rules interact - specificity, cascade order, media queries, inherited resets, custom properties defined elsewhere. What renders is the *outcome* of all that, and it is not something you can read off any single rule. Getting to the outcome means computing it the way a browser does.
/v1/code takes a URL and a section, resolves the full cascade, and returns a self-contained component - Tailwind, HTML+CSS, JSX or Vue, your choice - along with the design tokens that section uses and the assets it references. It is paste-ready, and it is what the page actually renders, not a best guess at it.
/v1/code25 creditsPass a URL and a selector - or let hero auto-detect find the main section for you.
tailwind, html, jsx or vue. The output is self-contained, not a fragment that depends on their stylesheet.
The response includes the colors and fonts that section uses, and the images and SVGs it references.
Swap their tokens for yours. You started from the real structure instead of a blank file.
curl "https://miromiro.app/api/v1/code?url=stripe.com&framework=tailwind" \
-H "Authorization: Bearer $MIROMIRO_API_KEY"
# → {
# "code": "<section class=\"relative w-full bg-[#0a2540] py-24\">…",
# "tokens": { "colors": ["#0a2540", "#635bff"], "fontFamilies": ["Sohne"] },
# "assets": { "images": [...], "fonts": [...] }
# }What you get: A working component in your framework, with the real tokens and assets, in one call instead of an afternoon.
Tailwind, plain HTML + CSS, React (JSX), and Vue. The component comes back self-contained - it does not depend on the source site's stylesheet, so it works when you paste it.
No, and deliberately not. It works at the section level - a hero, a pricing table, a feature grid. Whole-page cloning produces a tangle nobody wants to maintain. A clean section you can actually restyle is more useful than a page you have to unpick.
You are looking at publicly-served CSS - the same thing devtools shows any visitor. What you do with it is on you: taking a layout pattern as a starting point is normal engineering practice, and passing off someone's brand as your own is not. Use judgment.
They come back in the response - /v1/code returns the assets the section references, so you get the icons and images alongside the markup rather than a component full of broken links.
100 free credits, no credit card. Point it at a URL and see what comes back.
Get a free API key