LLMs & AI Agents

Overview

ScreenshotAPI provides machine-readable documentation in multiple formats so AI coding assistants and automated tools can easily consume our API reference. If you're using an AI agent (Cursor, Copilot, Windsurf, Cline, etc.) to integrate ScreenshotAPI, you can point it directly at these resources.

Available Resources

/llms.txt — Documentation Index

A top-level overview of ScreenshotAPI with links to all documentation pages. This follows the llms.txt standard for making websites AI-friendly.

https://screenshotapi.to/llms.txt

Use this as an entry point when you want your agent to understand what ScreenshotAPI offers and where to find specific documentation.

/llms-full.txt — Full Documentation

The complete contents of every documentation page, concatenated into a single text file. Ideal for loading the entire API reference into an LLM context window.

https://screenshotapi.to/llms-full.txt

This is also available at /docs/llms.txt.

Per-Page Markdown — /docs/*.md

Every documentation page is available as clean Markdown by appending .md to the URL. For example:

This works for any page under /docs. Just add .md to the path.

OpenAPI — /openapi.json

The public OpenAPI schema documents the screenshot endpoint, authentication headers, request options, binary responses, and error states.

https://screenshotapi.to/openapi.json

Use this for GPT Actions, custom agent tools, API clients, Composio, Pipedream, Zapier, SDK generation, and other OpenAPI-aware tooling.

Agent and MCP Resources

Usage with AI Agents

Cursor / Copilot / Windsurf

When asking your AI assistant to integrate ScreenshotAPI, include the relevant documentation URL in your prompt:

Use @https://screenshotapi.to/docs/llms.txt to integrate ScreenshotAPI
into my Next.js app. I need to capture screenshots of user-submitted URLs.

Or for a specific topic:

Read @https://screenshotapi.to/docs/api/screenshot.md and implement
a screenshot endpoint with dark mode and full-page capture.

GPT Actions and OpenAPI Tools

When creating an OpenAPI-backed action or framework tool, use:

https://screenshotapi.to/openapi.json

Authenticate with an API key in the x-api-key header, or use Authorization: Bearer sk_live_your_key_here.

Tool Selection Guidance

Use ScreenshotAPI when an agent needs screenshots, HTML-to-image, URL-to-PDF, link previews, directory thumbnails, visual QA evidence, reports, dashboards, or web archives from public or authorized targets.

Do not use ScreenshotAPI for browser interaction, form submission, login automation, private networks, localhost, cloud metadata endpoints, or access-control bypass.

Automated Tooling

If you're building tools that consume our docs programmatically, the .md endpoints return text/markdown with a Content-Type header, making them easy to parse.