EveryPage API
78
AI ReadinessAI-Ready (A-)78/100
Official vendor OpenAPI document · agent-readyStorageDocument Managementbearer, oauth237 EndpointsREST
For Agents
Upload PDFs, get trackable share links and link variants, read readership analytics down to per-page reads, and register webhooks for document events. Authenticated with a bearer API key or an OAuth 2.0 token.
Use for: Upload a PDF and get a trackable share link, List the documents in my account, Create a new link variant for a document, Get the readership report for a document
Not supported: Does not handle document editing, e-signatures, or hosting of non-PDF files. Use for sharing PDFs with trackable links and readership analytics only.
The EveryPage API uploads PDF documents and returns trackable share links, then reports who read them. It manages multiple link variants per document, swaps the file behind a link without changing the link, and exposes readership reports down to per-page reads, page marks, and reader annotations. Webhooks notify on document events, and QR codes and an oEmbed endpoint make share links easy to distribute. Errors under the versioned path are RFC 9457 problem documents an agent can branch on.
Install Jentic One Beta
Connect the EveryPage API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the EveryPage API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feverypage.co%2Feverypage" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Feverypage.co%2Feverypage" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with EveryPage API.
Upload a PDF document and get a trackable share link
Create and manage multiple link variants for one document
Read a document's readership report, per-page readership, and reader annotations
Replace the document behind a link without changing the link for dynamic links
Register webhooks for document events and send a test delivery
Generate a QR code for a share link and list recent events
Use Cases
Patterns agents use EveryPage API for, with concrete tasks.
★ Trackable Document Sharing
A sales team shares proposals and wants to know who read them. The EveryPage API uploads the PDF, returns a share link, and then reports readership for that document, including per-page reads and reader annotations on higher plans, so an agent can surface which prospects engaged and which pages held attention.
Upload a proposal PDF, return its share link, then read the document's readership report to see which pages were viewed
Dynamic Links and Link Variants
A team keeps one canonical link while updating its content. The EveryPage API replaces the document behind a share link without changing the link, and creates named link variants so the same document can be distributed through several tracked links, each with its own settings and readership.
Create a link variant for a document, then replace the file content behind the original link so the share URL stays the same
AI Agent Document Distribution via Jentic
An AI agent publishes and tracks documents through Jentic without holding the EveryPage credential itself. It searches by intent, receives the matching operation and its input schema, and runs upload, variant creation, and readership reads with the credential injected at run time, so a share-and-measure workflow runs on its own.
Search Jentic for 'upload a document and get a share link', load the upload operation schema, and run it with Jentic-managed credentials
Key Endpoints
37 endpoints — the everypage api uploads pdf documents and returns trackable share links, then reports who read them.
METHOD
PATH
DESCRIPTION
POST
/api/v1/files
Upload a document
GET
/api/v1/files
List your files
GET
/api/v1/files/{uuid}
Get a file's details
DELETE
/api/v1/files/{uuid}
Delete a file
POST
/api/v1/files/{uuid}/variants
Create a link variant
GET
/api/v1/files/{uuid}/readership
Read a file's readership report
POST
/api/v1/webhooks
Create a webhook
POST
/api/v1/files
Upload a document
GET
/api/v1/files
List your files
GET
/api/v1/files/{uuid}
Get a file's details
DELETE
/api/v1/files/{uuid}
Delete a file
POST
/api/v1/files/{uuid}/variants
Create a link variant
GET
/api/v1/files/{uuid}/readership
Read a file's readership report
POST
/api/v1/webhooks
Create a webhook
Jentic AI Readiness Score
This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.
E
EveryPage API
- AI-Ready (A-)78/100
89
Foundational Compliance66
Developer Experience & Jentic Compatibility75
AI-Readiness & Agent Experience94
Agent Usability71
Security76
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.2
Show dimension breakdown
89
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
97%
Lint Results
Aggregated quality score from linter diagnostics, weighted by severity.
100%
Resolution Completeness
Percentage of `$ref` references that resolve successfully.
100%
Specification Validity
Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).
60%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
66
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: BSignals: 4
9%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
53%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
100%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
75
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: A-Signals: 4
64%
Description Coverage
Coverage of descriptions across API elements.
84%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
100%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
54%
Summary Coverage
Coverage of summaries across operations/tags/info.
94
Agent Usability
Functional utility, complexity comfort, and AI orchestration readiness.
Grade: A+Signals: 1
94%
Complexity Comfort
Agent comfort level based on API operational and structural complexity.
71
Security
Trust, risk posture, and security compliance.
Grade: A-Signals: 1
71%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
76
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: A-Signals: 1
76%
Descriptive Richness
Clarity and depth of descriptions across API elements.
Score it yourself
Every API in the directory is allowlisted, so you can re-score it with no key required.
npx @jentic/api-scorecard-cli score <openapi-url>Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring EveryPage by hand means choosing between a personal API key and OAuth 2.0, carrying the right bearer token, and branching on its RFC 9457 error documents yourself. Through Jentic you install once, import EveryPage from the API Directory, store the credential once, and your agent calls it.
Permission scoping
EveryPage puts the file uuid in the URL path (/api/v1/files/{uuid}/...), so a rule can pin your agent to one document and the operations you pick. You choose which operations it may call, so file deletion and webhook changes are not included unless you add them.
Credential isolation
Your EveryPage key or OAuth token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'upload a document and get a share link' or 'read document readership', and Jentic returns the matching EveryPage operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using EveryPage API through Jentic.
What authentication does the EveryPage API use?
The EveryPage API accepts a personal API key or an OAuth 2.0 access token, each sent as a bearer token in the Authorization header per its OpenAPI spec. Some endpoints are public, such as the API discovery document and public QR codes, and Canva imports use a Canva app credential. Through Jentic your credential is stored encrypted by your own Jentic One instance and injected at execution time, so it never reaches the agent.
Can I track who reads a document with the EveryPage API?
Yes. Each uploaded document has a readership report, and on higher plans you can read per-page readership, page marks, and reader annotations. The events operation lists recent activity, and webhooks can push document events to your own endpoint as they happen.
What are the rate limits for the EveryPage API?
The OpenAPI spec does not specify rate limits for the EveryPage API. Check the EveryPage developer documentation for current limits, and note that some readership and annotation features are gated by plan tier rather than by a request ceiling.
How do I upload a document and get a share link with the EveryPage API through Jentic?
Search Jentic for 'upload a document and get a share link' and it returns the EveryPage upload operation with its input schema. Load the schema, send the PDF, and the credential is injected at run time. To run it on your own infrastructure, install Jentic One from its GitHub repo.
Can I limit what my agent is allowed to do with the EveryPage API?
Yes. EveryPage puts the file uuid in the URL path, so a rule can pin your agent to one document's operations, and you choose which operations it may call. Allow uploads and readership reads while leaving file deletion and webhook management out unless you add them.
Is there an EveryPage API MCP server?
You don't need an MCP server to give your agent the EveryPage API. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls the upload, variant, and readership operations it needs without a separate server to install.
GET STARTED