canonical: https://jentic.com/apis/geekflare.com/geekflare

# Geekflare API

Jentic publishes the only available OpenAPI specification for Geekflare API, keeping it validated and agent-ready. The Geekflare API bundles five common web-utility operations into a single key-authenticated surface - DNS lookups, page metadata extraction, HTML to PDF rendering, scrape, and full-page screenshots. It is positioned as a quick-integration toolkit for SEO checks, link-preview generation, document export, and lightweight web monitoring without standing up Puppeteer or DNS libraries yourself. Authentication uses an x-api-key header.

## For AI agents

Run DNS lookups, extract page metadata, scrape HTML, render PDFs, and capture screenshots from any URL via a single API key.

## Scope

Does not handle authentication, payments, or persistent storage - use for DNS, metadata, PDF render, scrape, and screenshot utility calls only.

## Capabilities

- Run a DNS lookup for any domain through the /dns endpoint, returning standard record types
- Extract Open Graph and standard metadata from a URL with /metadata for link previews
- Render any URL to a PDF document via /pdf for archive and report workflows
- Scrape page HTML or text content from a URL using /scrape
- Capture a full-page or above-the-fold screenshot via /screenshot for visual monitoring

## Use cases

### Automated Link-Preview Cards

Produce rich link-preview cards for a chat app or social tool by extracting Open Graph metadata. The agent calls /metadata with the URL and uses the title, description, and image fields to render the card. Skips the work of writing your own meta-tag parser.

Example prompt: Call GET /metadata?url={target_url} and map the response title, description, and image fields onto your card component

### Scheduled Page Screenshots For Monitoring

Capture daily screenshots of key pages - pricing, status, competitor home - and diff them for visual change detection. The agent calls /screenshot with the URL on a cron and stores the image. Replaces ad-hoc browser-automation scripts.

Example prompt: Call GET /screenshot?url={url}&fullPage=true on a daily cron, store the binary, and diff against the previous run

### URL To PDF For Reports And Archives

Render a public report URL or article into a PDF for offline archival. The agent calls /pdf with the target URL and stores the resulting binary in object storage. Useful when teams need a frozen-in-time copy of a webpage for audit or compliance.

Example prompt: Call GET /pdf?url={target_url}, write the binary response to s3 with a date-stamped key, and return the storage URL

### Agent-Driven Web Utilities Through Jentic

AI agents reach for Geekflare via Jentic when a workflow needs a quick screenshot, PDF, or DNS check without standing up a separate utility service. Jentic isolates the x-api-key in its vault and returns the right operation schema based on intent.

Example prompt: Use Jentic search query 'capture a screenshot of a URL' to load the geekflare_capture_screenshot tool and execute with the target URL

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/dns` | Run a DNS lookup for a domain |
| GET | `/metadata` | Extract page metadata from a URL |
| GET | `/pdf` | Render a URL as a PDF |
| GET | `/scrape` | Scrape HTML content from a URL |
| GET | `/screenshot` | Capture a page screenshot |

## Key resources

- **DNS** — Run DNS record lookups against any domain
- **Metadata** — Extract Open Graph and meta tag data from URLs
- **PDF** — Render URLs to PDF binaries
- **Scrape** — Fetch HTML or text content from URLs
- **Screenshot** — Capture page screenshots at configured viewports

## Why Jentic

- **Setup:** Wiring the Geekflare API by hand means setting up its x-api-key header auth against api.geekflare.com and threading the key through its DNS, metadata, PDF, scrape, and screenshot calls yourself. Through Jentic you install once, import the Geekflare API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** Geekflare takes its target as a request parameter rather than a URL path resource, so scope this by operation: limit the agent to the operations it needs, such as a DNS lookup or screenshot, and leave the utilities you do not want it calling out of the allowed set. Every operation the agent can run is one you chose to include.
- **Credential handling:** Your Geekflare API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'look up DNS records for a domain' or 'take a screenshot of a page', and Jentic returns the matching Geekflare API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Abstract API** — Abstract API offers a similar grab-bag of utility endpoints; Geekflare bundles screenshot, PDF, DNS, scrape, and metadata behind a single key.
- **OpenAI API** — Use OpenAI to summarise the HTML returned by /scrape or to extract structured fields from a screenshot.
- **Slack API** — Post a daily Geekflare screenshot or PDF into a Slack channel for visual change-detection notifications.

## FAQ

### Why is there no official OpenAPI spec for Geekflare API?

Geekflare does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Geekflare API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Geekflare API use?

Geekflare uses an API key in the x-api-key header. Keys are issued in the Geekflare dashboard. Through Jentic the key is stored encrypted in the vault and injected at request time.

### Can I render a URL as a PDF with the Geekflare API?

Yes. GET /pdf accepts a url query parameter and returns a PDF binary, suitable for archiving public reports or generating offline copies of articles.

### How do I capture a full-page screenshot?

Call GET /screenshot with the url query parameter; the response is a PNG binary. Geekflare's documented options include full-page mode and viewport sizing - check the developer console for the current parameter list.

### What are the rate limits for the Geekflare API?

Geekflare's OpenAPI does not declare rate-limit headers. Limits depend on your plan tier - back off on HTTP 429 and check your dashboard for the current quota.

### How do I capture a screenshot through Jentic?

Install with pip install jentic, search 'capture a screenshot of a URL', load the geekflare_capture_screenshot operation schema, and execute with the target url. Jentic injects the x-api-key header from the vault.

### Can I limit what my agent is allowed to do with the Geekflare API?

Yes. Because you run Jentic One yourself, your own rules decide which Geekflare operations the agent may call and which credential it uses. Geekflare takes its target as a request parameter rather than a URL path, so you scope it by operation: allow only the calls the agent needs, such as a DNS lookup or a screenshot, and leave the PDF render, metadata, or scrape utilities out of the allowed set. Every operation the agent can run is one you chose to include, and the x-api-key stays with your instance rather than the agent.