Developer API · OG images + screenshots

Pixel-exact OG images, one request away.

Ogle renders dynamic Open Graph cards and full-page screenshots from a single API call — key-gated, metered per request, and fast enough to call inline.

GET01 / request
GET /api/og
  ?title=Ship better link previews
  &subtitle=Dynamic OG images in one call
  &theme=dark

x-api-key: YOUR_API_KEY
02 / response200OK
Live Open Graph image generated by the Ogle API630 px
image/png · cache 1h1200 px
output
1200 × 630
format
PNG
engine
next/og
auth
x-api-key

Why Ogle

Infrastructure, not an image model

An OG card is a template with your text in it — the same input must always produce the same pixels. That’s a rendering problem, not a generative one. Ogle renders deterministically, so link previews stay pixel-exact and on-brand on every request.

01

Deterministic

Same params in, same PNG out — every time. No sampling, no drift, no surprise layouts. Render once, cache forever.

02

Pixel-exact & on-brand

Your fonts, your colors, your layout — down to the pixel. Not an approximation of your brand that a model reinvents each call.

03

Sub-second

Rendered in milliseconds, fast enough to call inline while a page loads. Generative image models take seconds and cost real money per image.

04

Cheap at scale, SLA-backed

Flat per-request metering up to a million calls/mo on Scale, with priority rendering and an SLA — not a per-image inference bill.

What it does

Two endpoints, one key

Everything a micro-SaaS needs to ship metered image generation — without wiring a browser farm yourself.

01GET /api/og

Dynamic OG images

Render 1200×630 social cards on the fly with next/og. No headless browser, edge-fast, cache-friendly.

02GET /api/screenshot

Full-page screenshots

Capture any URL as a PNG with puppeteer-core + @sparticuz/chromium on Vercel. Great for previews and monitoring.

03x-api-key

Keys and metering

Every request is gated by an API key and counted per key. Ship a metered product from day one.

How it works

Live in three steps

No SDK, no browser farm, no build step. A URL and a key is the whole integration.

01

Get your key

Sign in and copy your ogs_ key from the dashboard — the free plan is ready the moment you land.

02

Build the URL

Add your title and subtitle (or a URL to screenshot) as query params, and attach your key.

03

Request the image

Call it from a server, an <img> tag, or an og:image meta tag. You get back a ready-to-use PNG.

For developers

Ship it with a single request

Read the reference, grab a key, and call the API from your backend, an <img>, or an og:image meta tag.

For everyone else

No code? Use the Studio

Type a title, see the image, and download a ready-to-share PNG. No API calls, no setup — just your headline.

Integrate

Call it from anywhere

Pass your key via the x-api-key header or a ?key= query param. No SDK required.

bash · curl
# Generate an OG image (1200x630 PNG)
curl "https://ogle.talrax.com/api/og?title=Hello&subtitle=World" \
  -H "x-api-key: YOUR_API_KEY" -o og.png

# Capture a full-page screenshot
curl "https://ogle.talrax.com/api/screenshot?url=vercel.com" \
  -H "x-api-key: YOUR_API_KEY" -o shot.png

FAQ

Common questions

Is this AI?
No. Ogle deterministically renders a template with next/og — the same request always returns the exact same pixels. That makes previews reliable, cacheable, and precisely on-brand, unlike a generative image model that reinvents the layout each call.
How am I billed?
Monthly, through Paddle as our Merchant of Record. Choose a plan on the pricing page; you can upgrade, downgrade, or cancel anytime from your dashboard.
Can non-developers use it?
Yes. The no-code Studio lets anyone type a title and download a ready-to-share image — no API calls or code required.
What happens at my limit?
Requests return a 402 once your monthly quota is used up. Upgrade your plan to raise the cap, or wait for the monthly reset.

# More detail in the docs and on pricing.