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

Screenpipe Frames API

Access captured screenshots and their extracted text

Screenpipe Frames API is one of 18 APIs that Screenpipe publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Frames. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and authentication docs.

This API exposes 9 operations across 7 paths, and defines 12 schemas. It is described by OpenAPI 3.0.3, at version 1.0.0.

Requests are made against the base URL http://localhost:3030.

9 operations 7 paths 12 schemas 7 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0.0
Base URL
http://localhost:3030
Resource Areas
1

Paths & Operations 9

Across 7 paths, the API surfaces 9 operations — 7 GET, 2 POST. Each is listed below with its method, path, parameters, and response codes.

Frames 9

Access captured screenshots and their extracted text

GET
/frames/{frame_id}
Get frame by ID
routes_frames_get_frame_data 1 param → 200
GET
/frames/{frame_id}/text
Get frame text and bounds
routes_frames_get_frame_text_data 2 params → 200
POST
/frames/{frame_id}/text
Run OCR on frame
routes_frames_run_frame_ocr 1 param → 200
GET
/frames/{frame_id}/ocr
Get frame OCR (deprecated)
routes_frames_get_frame_text_data 2 params → 200
POST
/frames/{frame_id}/ocr
Run frame OCR (deprecated)
routes_frames_run_frame_ocr 1 param → 200
GET
/frames/{frame_id}/context
Get frame context
routes_frames_get_frame_context 1 param → 200
GET
/frames/{frame_id}/metadata
Get frame metadata
routes_frames_get_frame_metadata 1 param → 200
GET
/frames/next-valid
Get next valid frame
routes_frames_get_next_valid_frame 3 params → 200
GET
/frames/{frame_id}/elements
Get frame UI elements
routes_elements_get_frame_elements 2 params → 200

Schemas 12

The contract defines 12 schemas that model the data the API accepts and returns. The most detailed are ElementResponse (10 properties), FrameContextResponse (5 properties), AccessibilityNode (5 properties), AccessibilityNodeBounds (4 properties). Each schema is shown below with its type and property counts.

FrameTextResponse
object
Response type for frame OCR data endpoint
2 properties 2 required
TextBounds
object
4 properties 4 required
ElementsListResponse
object
2 properties 2 required
FrameContextResponse
object
Response type for frame context endpoint (accessibility-first, OCR fallback)
5 properties 5 required
BoundsResponse
object
4 properties 4 required
PaginationResponse
object
3 properties 3 required
AccessibilityNode
object
A node from the accessibility tree
5 properties 3 required
TextPosition
object
3 properties 3 required
FrameMetadataResponse
object
Response type for frame metadata (used by deep link navigation)
2 properties 2 required
ElementResponse
object
10 properties 10 required
AccessibilityNodeBounds
object
Bounding box for an accessibility node (0-1 normalized to monitor)
4 properties 4 required
NextValidFrameResponse
object
Response for next valid frame endpoint
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

screenpipe-frames-api-openapi.yml Raw ↑

Other APIs Screenpipe publishes across the network.

Screenpipe Activity API
Screenpipe Audio API
Screenpipe Cloud Archive API
Screenpipe Cloud Sync API
Screenpipe Data Management API
Screenpipe Data Retention API
Screenpipe Database API
Screenpipe Elements API
Screenpipe Experimental API
Screenpipe Meetings API
Screenpipe Memories API
Screenpipe Search API
Where this information came from

This is an independent, third-party profile of Screenpipe Frames 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.