Filedroppr EveryPage API
78
AI ReadinessAI-Ready (A-)78/100
Official vendor OpenAPI document · agent-readyStorageDocument Managementbearer, oauth237 EndpointsREST
For Agents
Upload documents, mint trackable share links and link variants, and read readership reports down to the page. List events and gate responses, and register webhooks for document activity.
Use for: Upload a PDF and get a share link I can track, List the files in my account, Create a second tracked link for an existing document, Get the readership report for a document
Not supported: Does not handle e-signatures, document generation, or long-term file storage tiers. Use for sharing documents through trackable links and reading their readership only.
The EveryPage API uploads documents and returns trackable share links, then reports how each link is read. A single file can carry several link variants, each tracked on its own, and readership reports break viewing down to the page on paid plans, alongside reader annotations and page marks. Recent events and completed viewing-gate responses are listable, and webhooks push document events as they happen. Every error under the versioned path is an RFC 9457 problem document, so a client can branch on its code.
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%2Ffiledroppr.com%2Ffiledroppr" | 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%2Ffiledroppr.com%2Ffiledroppr" | 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 and get a trackable share link, or import one from an export URL
Create and manage link variants so one document can have several tracked links
Read a document's readership report, including per-page viewing time on paid plans
Pull reader annotations and page marks left on a document
List recent events and completed viewing-gate responses from readers
Register webhooks to receive document events as they happen
Use Cases
Patterns agents use EveryPage API for, with concrete tasks.
★ Agent-driven document sharing through Jentic
An AI agent uploads a proposal, mints a tracked share link, and later reads the readership report to see whether the recipient opened it and which pages held their attention. With link variants the agent can give each recipient their own link, so the report attributes views to the right person without a person opening the dashboard.
Upload a PDF, create a link variant for one recipient, then read that document's readership report
Per-recipient link variants
Sales and partnerships send the same document to many people but want to know who engaged. EveryPage lets a file carry multiple link variants, each tracked separately, so an integration can generate a distinct link per recipient and later compare their readership side by side.
Create three link variants on one file and list the variants to confirm each has its own tracked link
Readership-driven follow-up
Knowing a prospect read pages three through five changes the follow-up. EveryPage reports readership down to the page and surfaces reader annotations, and webhooks deliver viewing events as they happen, so an assistant can trigger a timely nudge the moment a key page is reached.
Register a webhook for viewing events, then read the per-page readership for a document to find its most-read pages
Key Endpoints
37 endpoints — the everypage api uploads documents and returns trackable share links, then reports how each link is read.
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
POST
/api/v1/files/{uuid}/variants
Create a link variant
GET
/api/v1/files/{uuid}/readership
A file's readership report
GET
/api/v1/files/{uuid}/readership/pages
A file's per-page readership
POST
/api/v1/webhooks
Create a webhook
GET
/api/v1/events
List recent events
POST
/api/v1/files
Upload a document
GET
/api/v1/files
List your files
GET
/api/v1/files/{uuid}
Get a file's details
POST
/api/v1/files/{uuid}/variants
Create a link variant
GET
/api/v1/files/{uuid}/readership
A file's readership report
GET
/api/v1/files/{uuid}/readership/pages
A file's per-page readership
POST
/api/v1/webhooks
Create a webhook
GET
/api/v1/events
List recent events
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 the EveryPage API by hand means choosing between a personal API key and an OAuth 2.0 token, branching on its RFC 9457 error bodies, and managing link variants and webhooks yourself. Through Jentic you install once, import it from the API Directory, store the credential once, and your agent calls it.
Permission scoping
You choose which operations your agent may call, so it can upload documents and read readership while the delete and webhook-management operations stay out unless you add them. The OAuth token exchange, oEmbed, and public QR-code links are open operations that need no credential at all.
Credential isolation
Your EveryPage API key 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 a document's 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?
It accepts a personal API key or an OAuth 2.0 access token, both sent as a Bearer token in the Authorization header, per its OpenAPI spec. Some endpoints, such as the OAuth token exchange, the oEmbed provider, and the public QR-code links, need no credential.
Can I track readership per page with the EveryPage API?
Yes. The readership report covers a document's overall engagement, and on paid plans a per-page endpoint breaks viewing time down page by page. You can also pull reader annotations and page marks left on the document, and list the raw viewing events behind them.
What are the rate limits for the EveryPage API?
The OpenAPI spec does not state a numeric rate limit, though it notes that every error under the versioned path is an RFC 9457 problem document you can branch on. Check the EveryPage documentation for current rate limits before syncing many files.
Is there an EveryPage 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, readership, and webhook operations on demand.
Can I limit what my agent is allowed to do with the EveryPage API?
Yes. Write a rule that allows the upload, file-read, and readership operations and leaves the delete and webhook-management operations off the list, so an agent can share documents and report on them without removing files or changing your webhooks. Every call it makes is recorded in your Jentic One audit log.
How do I share a tracked document with the EveryPage API through Jentic?
Search Jentic for 'upload a document and get a share link', add the EveryPage API from the directory, and store your API key once; your agent then uploads the file, creates a link variant, and reads its readership. To run it on your own infrastructure, install Jentic One from its GitHub repo.
GET STARTED