Every typeface,
detected.
Find what font any website uses — family names, fallback stacks, usage percentages, and catalog matches when they exist.
Detect font families in use on a domain.
Start free, no card required, most teams ship a first integration in under ten minutes.
Not another JSON page.
A production workflow in one call
One call in. Font telemetry out.
Before Orsa
- A browser worker, proxy account, parser, retry queue, and schema contract for one endpoint.
- Product teams wait while platform teams debug website-specific failures.
- Every new data field becomes another brittle scraper branch.
After Orsa
- One call in. Font telemetry out. With retries, rendering, and validation handled behind the API.
- The response shape is typed, documented, and ready for product code.
- Teams combine it with adjacent Orsa endpoints without adding vendors.
Teach the workflow,
then show the endpoint
Point Orsa at a domain, let the platform handle the web work, and receive a response your product can trust.
Send a domain
figma.com
Render, retry, enrich
Orsa handles browser execution, proxy escalation, parsing, validation, caching, and typed response shaping behind the API.
One call in. Font telemetry out.
Use the result in creative tooling without owning the extraction stack.
- REST path
- /api/v1/brand/styleguideSame endpoint used by the SDK examples below.
- Input shape
- domainfigma.com
- SDKs
- TypeScript, Python, cURLStart with TypeScript, Python, or direct cURL.
- Best first use
- Creative toolingPreload the right faces before designers open Figma.
Performance your product
can actually plan around
Every endpoint page should answer the practical buying question: will this hold up once it leaves the demo?
More than the response.
The operating layer behind it
Stripe pages teach the system around the API: inputs, retries, observability, adjacent products, and the code path. This section does the same for Orsa endpoints.
- Typed response contracts for product code and AI tools.
- Browser, proxy, cache, and validation logic handled by Orsa.
- Direct fit for creative tooling and email templates.
Endpoint
/api/v1/brand/styleguide
Example input
figma.com
Promise
One call in. Font telemetry out.
Pairs with
Company Styleguide, Company Colors, Website Screenshot
What teams ship with
every typeface, detected.
Each product page now speaks to the real workflow behind the endpoint, with concrete jobs instead of a generic feature list.
Creative tooling
Preload the right faces before designers open Figma.
Email templates
Match typography across web and outbound comms.
Compliance reviews
Capture font usage for licensing audits.
Keep the code small.
Let Orsa do the messy part
Use the endpoint directly, then combine it with adjacent Orsa APIs as the workflow grows.
{
"domain": "figma.com",
"fonts": [
{ "family": "Inter", "role": "body", "approx_usage": 0.62 }
]
}Build the full workflow,
not another point solution
The best product integrations usually combine two or three Orsa endpoints behind one customer experience.
The questions teams ask
before shipping
Short answers for the practical details: rendering, limits, freshness, and how this fits into production.
Put this endpoint
in your product today
Try the live endpoint, then wire the same response into your app with one API key.
One API key for every Orsa endpoint · No card required to start.