How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Pagesnap Content API

Reading and rendering

Pagesnap Content API is one of 11 APIs that Pagesnap publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Content. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, authentication docs, and rate-limit docs.

This API exposes 13 operations across 10 paths, and defines 6 schemas. It is described by OpenAPI 3.2.0, at version 1.1.0.

Requests are made against a single base URL, https://pagesnap.142-93-197-141.sslip.io.

13 operations 10 paths 6 schemas 8 GET5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.1.0
Base URL
https://pagesnap.142-93-197-141.sslip.io
Authentication
HTTP Bearer, API Key, API Key, API Key
Resource Areas
1

Authentication & Security 4

Pagesnap Content API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (ps_live_…) (bearer). An API key is passed in the header as X-API-Key (apiHeader). An API key is passed in the query as key (apiQuery). An API key is passed in the header as PAYMENT-SIGNATURE (x402). By default, every request must be authenticated, though some operations may also be called without credentials.

  • bearer — Pagesnap API key.
  • apiQuery — Compatibility only; headers avoid key leakage in URLs.
  • x402 — x402 v2 exact EIP-3009 USDC authorization on Base; X-PAYMENT is a legacy alias.

Paths & Operations 13

Across 10 paths, the API surfaces 13 operations — 8 GET, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Content 13

Reading and rendering

GET
/v1/read
Read a public URL
readUrl 13 params → 200400401403408413422429
POST
/v1/read
Read a URL with a JSON options body
readUrlPost body → 200400401403408413422429
GET
/v1/screenshot
Capture a public URL
screenshotUrl 19 params → 200400401403408413422429
POST
/v1/screenshot
Capture a URL with a JSON options body
screenshotUrlPost body → 200400401403408413422429
GET
/v1/pdf
Render a public URL as PDF
pdfUrl 16 params → 200400401403408413422429
POST
/v1/pdf
Render a URL as PDF with a JSON options body
pdfUrlPost body → 200400401403408413422429
GET
/v1/meta
Get link-preview metadata
getMeta 3 params → 200400401403408413422429
GET
/v1/extract
Extract structured page data
extractStructured 2 params → 200400401403408413422429
GET
/r/{url}
Read shortcut
readShortcut 13 params → 200400401403408413422429
GET
/s/{url}
Screenshot shortcut
screenshotShortcut 19 params → 200400401403408413422429
POST
/v1/render
Render supplied HTML
renderHtml body → 200400401403408413422429
POST
/v1/batch
Read multiple URLs
batchRead body → 200400401403408413422429
GET
/tmp/{name}
Download a temporary result
getTemporaryResult 1 param → 200404

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ReadResult (14 properties), MetaResult (12 properties), ExtractResult (8 properties), BatchResult (3 properties). Each schema is shown below with its type and property counts.

BatchResult
object
3 properties 3 required
ExtractResult
object
8 properties 1 required
MetaResult
object
12 properties 1 required
Actions
array
ReadResult
object
14 properties 1 required
Error
object
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

pagesnap-content-api-openapi.yml Raw ↑

Other APIs Pagesnap publishes across the network.

Pagesnap Account API
Pagesnap Agents API
Pagesnap Billing API
Pagesnap Crawl API
Pagesnap Diff API
Pagesnap Discovery API
Pagesnap Monitors API
Pagesnap Status API
Pagesnap Support API
Pagesnap X402 API
Where this information came from

This is an independent, third-party profile of Pagesnap Content API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.