Getpocket Pocket API
50
AI ReadinessFoundational (C-)50/100
Agent-ready OpenAPI document · curated by JenticProductivityNote TakingapiKey7 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Save URLs to a user's Pocket queue, retrieve saved items by tag or state, and apply batch tag and archive operations through OAuth-scoped access tokens.
Use for: I need to save this URL to my Pocket reading list with the tag 'research', Retrieve my unread Pocket items modified in the last 7 days, Archive every Pocket item tagged 'read-later' that is older than 30 days, List all tags I have applied across my saved items
Not supported: Does not handle full-text content extraction, recommendation, or social sharing - use for managing a user's saved-item queue and tags only.
Jentic publishes the only available OpenAPI specification for Pocket API, keeping it validated and agent-ready. Pocket is a read-it-later service that lets users save articles, videos, and links to a personal queue for offline reading and later review. The v3 HTTP API exposes seven endpoints covering item ingestion, batch modifications, retrieval with filters and tags, OAuth handshake, tag listing, and account-level statistics. It is the canonical integration surface for browser extensions, recommendation pipelines, and reading-list automation that needs a stable, long-lived saved-item store.
Install Jentic One Beta
Connect the Pocket API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Pocket 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%2Fgetpocket.com%2Fgetpocket" | 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%2Fgetpocket.com%2Fgetpocket" | 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 Pocket API.
Add a URL with optional tags and title to the user's Pocket queue
Retrieve saved items filtered by state, tag, content type, or modified-since timestamp
Apply batch actions to archive, favourite, delete, or retag many items at once
Run the OAuth request-token and access-token flow to authorise a new user
List all tags the user has applied across their saved items
Pull account stats covering item counts and reading activity
Use Cases
Patterns agents use Pocket API for, with concrete tasks.
★ Read-later pipeline from chat agents
Knowledge workers paste links into a chat agent and ask it to 'save this for later'. The agent calls Pocket's add endpoint with the URL and a context-derived tag, building a structured personal reading queue without manual triage. Retrieval later is one search-by-tag away.
Save https://example.com/long-read to Pocket with tags 'research' and 'ai-agents' and confirm the item id
Tag-driven content recommender
Build a weekly digest by retrieving Pocket items with a specific tag added since the last digest run, summarising each, and emailing the result. The /get endpoint supports tag and since filters, so the digest job pulls only the new items rather than re-processing the full archive.
Retrieve all Pocket items with tag 'ml-papers' added since 2026-06-01 and produce a summarised digest
Archive cleanup at scale
Power users accumulate thousands of saved items. The /send endpoint accepts a batch of actions in one request, so an agent can archive everything older than a threshold or retag a set of items without making a call per item. This is meaningfully cheaper than walking the queue one item at a time.
Archive all unread Pocket items older than 90 days in a single batch /send call
Key Endpoints
7 endpoints — jentic publishes the only available openapi specification for pocket api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/add
Save a URL to the user's queue
POST
/get
Retrieve saved items with filters
POST
/send
Apply batch actions to many items
POST
/oauth/request
Request an OAuth request token
POST
/oauth/authorize
Exchange request token for access token
POST
/tags/get
List all tags applied across items
POST
/add
Save a URL to the user's queue
POST
/get
Retrieve saved items with filters
POST
/send
Apply batch actions to many items
POST
/oauth/request
Request an OAuth request token
POST
/oauth/authorize
Exchange request token for access token
POST
/tags/get
List all tags applied across items
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.
P
Pocket API
- Foundational (C-)50/100
83
Foundational Compliance55
Developer Experience & Jentic Compatibility30
AI-Readiness & Agent Experience94
Agent Usability50
Security43
AI DiscoverabilityPowered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
83
Foundational Compliance
Base layer of spec validity and structural soundness.
Grade: ASignals: 4
98%
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).
35%
Structural Integrity
Structural correctness score based on schema issues using logarithmic dampening.
55
Developer Experience & Jentic Compatibility
Clarity, completeness, and ingestion readiness for developers and tooling.
Grade: CSignals: 4
0%
Example Density
How richly the API is illustrated with examples.
100%
Example Validity
Percentage of examples that conform to their schemas.
25%
Response Coverage
Percentage of operations with complete response definitions (success, client error, server error).
93%
Tooling Readiness
Health of API ingestion, bundling, and resolution within Jentic pipelines.
30
AI-Readiness & Agent Experience
Semantic breadth, depth, and agent comprehension for AI systems.
Grade: FSignals: 4
15%
Description Coverage
Coverage of descriptions across API elements.
0%
Error Standardization
Coverage of RFC 9457 Problem Details for error responses.
57%
OperationId Quality
Coverage, uniqueness, and casing consistency of operationIds for AI inference.
50%
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.
50
Security
Trust, risk posture, and security compliance.
Grade: C-Signals: 1
50%
Authentication Strength
Average quality of security schemes based on authentication method strength (weakest link for OAuth2).
43
AI Discoverability
Findability, semantic richness, and reasoning readiness.
Grade: D-Signals: 1
43%
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 Pocket by hand means passing both the consumer_key and a per-user access_token, running its OAuth request-and-authorize handshake, and shaping the add, get, and send payloads yourself. Through Jentic you install once, import the Pocket API from the API Directory, store the credentials once, and your agent calls it.
Permission scoping
Pocket carries the action and item targets in the request body rather than a resource id in the path, so you limit the agent to the operations it needs, such as saving a URL or retrieving saved items. Because you pick the operation set, bulk changes through the send operation are not reachable unless you add it.
Credential isolation
Your Pocket consumer key and per-user access token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'save a URL to read later' or 'list saved items', and Jentic returns the matching Pocket 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 Pocket API through Jentic.
Why is there no official OpenAPI spec for Pocket API?
Pocket does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Pocket API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Pocket API use?
Pocket uses a consumer_key plus a per-user access_token sent in the request body. The OAuth handshake at /oauth/request and /oauth/authorize mints the access_token. Through Jentic the consumer_key and access_token are vaulted and injected at execution time.
Can I save a URL to Pocket through the API?
Yes. POST /add with the URL and optional tags or title creates a new saved item in the user's queue. The response returns the canonical item identifier you can later use with /send for batch operations.
What are the rate limits for the Pocket API?
The OpenAPI spec does not encode explicit rate limits, but Pocket historically applies per-consumer-key and per-user-token thresholds. Use the /send batch endpoint for bulk modifications instead of looping /add or /modify, which keeps you well under the limits.
How do I retrieve saved items filtered by tag through Jentic?
Search Jentic for 'get pocket items by tag', load the POST /get schema, then execute with the tag and optional since timestamp. Jentic injects the consumer_key and access_token automatically.
Can I run multiple actions in one call?
Yes. POST /send accepts an actions array where each element is an archive, favourite, delete, tag-add, or tag-remove action. This is the supported way to perform bulk maintenance without flooding the per-item endpoints.
Is the Pocket API free?
Pocket's API has historically been free for developers with a registered consumer_key, though Pocket's product status has shifted recently - check getpocket.com for current availability and any successor service before building production integrations.
Can I limit what my agent is allowed to do with the Pocket API?
Yes. Because you run Jentic One yourself, your own rules decide which Pocket operations the agent can reach and which credentials it may use. Pocket carries the action and item targets in the request body rather than a resource id in the path, so you grant only the operations the agent needs, such as saving a URL with /add or retrieving saved items with /get. Bulk changes through the /send batch operation stay out of reach unless you explicitly add it to the agent's allowed set.
GET STARTED