> ## Documentation Index
> Fetch the complete documentation index at: https://docs.scrnshot.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> What scrnshot is and how the API is organized

scrnshot is a screenshot API: send a URL and a few options, get back a
hosted image. No headless browser to manage, no infrastructure to run.

## Base URL

All API requests go to:

```
https://api.scrnshot.site
```

The dashboard, where you create an account and manage API keys, is at
[scrnshot.site](https://scrnshot.site).

## How the API is organized

<CardGroup cols={2}>
  <Card title="Capture" href="/api-reference/screenshots/capture-a-screenshot">
    `POST /v1/screenshots` — the endpoint you'll use for almost everything.
  </Card>

  <Card title="Usage" href="/api-reference/usage/get-current-usage">
    `GET /v1/usage` — check quota consumption programmatically.
  </Card>

  <Card title="Authentication" href="/authentication">
    API keys, headers, and how revocation works.
  </Card>

  <Card title="Plans & limits" href="/guides/plans-and-limits">
    What each plan allows, and what happens when you hit a limit.
  </Card>
</CardGroup>

Two endpoints are **not** part of the programmatic API even though they live
under the same domain:

* `POST /demo/screenshot` — powers the live demo on scrnshot.site. It's
  unauthenticated and IP-rate-limited to 5 requests/day. Don't integrate
  against it.
* `/v1/keys` and `/v1/billing/*` — dashboard-only endpoints authenticated
  with a session cookie, not an API key. They're documented in the API
  reference for completeness, not because you'll call them from server code.

## Next steps

Head to [Quickstart](/quickstart) to create an API key and capture your
first screenshot.