Developer Dashboard

Manage your Prism API credentials and test captures in real-time.

Your API Tokens

Prism Scoped

                        
                                    Token Name
                                    Created
                                    Last Used
                                    Action
                                
                                    Loading tokens...

Token Name	Created	Last Used	Action
Loading tokens...

Screenshot Playground

Target URL

Viewport

Format

Delay (ms)

Options

Full Page

◫

Captured webpage will appear here.

Capture History

No captures yet. Take one above!

Generate API Key

API Usage Guide

curl -X POST https://devetty-backoffice.test/api/v1/capture \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://google.com"}'

fetch('https://devetty-backoffice.test/api/v1/capture', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_TOKEN',
    'Content-Type': 'application/json'
  },
  body: JSON.stringify({ url: 'https://google.com' })
})
.then(res => res.json())
.then(data => console.log(data));

import requests

res = requests.post(
  'https://devetty-backoffice.test/api/v1/capture',
  headers={
    'Authorization': 'Bearer YOUR_API_TOKEN',
    'Content-Type': 'application/json'
  },
  json={'url': 'https://google.com'}
)
print(res.json())

use Illuminate\Support\Facades\Http;

$res = Http::withHeaders([
  'Authorization' => 'Bearer YOUR_API_TOKEN'
])->post('https://devetty-backoffice.test/api/v1/capture', [
  'url' => 'https://google.com'
]);

print_r($res->json());

MCP Integration (HTTP)

Add Prism as a Model Context Protocol server in Gemini IDE (mcp_config.json). It exposes only the take_screenshot tool.

"prism": {
  "transport": "http",
  "serverURL": "https://devetty-backoffice.test/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_API_TOKEN"
  },
  "disabled": false,
  "disabledTools": []
}

Some desktop clients (e.g. Claude Desktop or ChatGPT desktop) don't support custom headers on remote MCP connections. For those, pass the token as an api_key query parameter on the same URL instead:

https://devetty-backoffice.test/mcp?api_key=YOUR_API_TOKEN

Both methods use the same scoped token and grant the same access — use headers when the client supports them, otherwise use the URL query parameter.