Geekflare API

Name: Geekflare API API
Brand: Geekflare API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentDeveloper ToolsMonitoring ObservabilityapiKey5 EndpointsREST

For Agents

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

Quickstart

Get started with Geekflare API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"capture a screenshot of a URL"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Geekflare API API.

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

GET STARTED

Start building with Geekflare API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Geekflare API, keeping it validated and agent-ready.

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.

Use Cases

Patterns agents use Geekflare API API for, with concrete tasks.

★ 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.

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.

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.

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.

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

5 endpoints — jentic publishes the only available openapi specification for geekflare api, keeping it validated and agent-ready.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Geekflare's x-api-key value is stored encrypted in the Jentic vault. Agents receive a scoped execution token; the raw API key never enters the agent's context.

Intent-based discovery

Agents search by intent (e.g. 'capture a screenshot of a URL') and Jentic picks the matching Geekflare operation among the five endpoints, returning its input schema for direct execution.

Time to first call

Direct Geekflare integration: 1-2 hours per workflow to wire auth and handle binary responses. Through Jentic: under 15 minutes — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Abstract API

Abstract API offers a similar grab-bag of utility endpoints; Geekflare bundles screenshot, PDF, DNS, scrape, and metadata behind a single key.

Choose Abstract API for validation-heavy use cases (email, phone, IP); choose Geekflare when the workflow centres on rendering or scraping URLs.

Complementary

OpenAI API

Use OpenAI to summarise the HTML returned by /scrape or to extract structured fields from a screenshot.

Pair OpenAI with Geekflare when raw scraped HTML or images need to be reduced to structured data.

Complementary

Slack API

Post a daily Geekflare screenshot or PDF into a Slack channel for visual change-detection notifications.

Use Slack with Geekflare when the consumer of a screenshot or PDF is a team channel rather than a storage bucket.

FAQs

Specific to using Geekflare API API through Jentic.

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 at https://app.jentic.com/sign-up.

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.