Jentic OSThe workplace. An in-house AI platform for every employeeJentic OneSafe access. Agents reach your systems without holding keysJentic AIRThe foundation. Gets your existing platforms ready for AI
Pricing

GET STARTED

API DirectoryBrowse 10,000+ APIs ready for AI agent integrationDocumentationGuides and API reference

TOOLS

API ScoringCheck your AI readiness using our scorecardArazzo UIVisualize Arazzo workflows as interactive documentationArazzo EditorBuild and edit multi-step API workflows visually

COMMUNITY

GitHubOpen source projects and examplesOpen StandardsBuilt on open specs. Never locked in.
All ResourcesEverything in one placeBlogLatest articles and insightsTech Talk NewsletterAPIs, AI agents, architecture and strategyWebinarsLive sessions and on-demand recordingsReports & WhitepapersOriginal research on enterprise AI
About UsOur mission and teamCareersJoin our teamContactGet in touch
Try it now
Jentic OSJentic OneJentic AIR
Pricing
API DirectoryDocumentationAPI ScoringArazzo UIArazzo EditorGitHubOpen Standards
All ResourcesBlogTech Talk NewsletterWebinarsReports & Whitepapers
About UsCareersContact
Try it now
JenticJentic
Products
  • Jentic OS
  • Jentic One
  • Jentic AIR
For Developers
  • API Directory
  • Documentation
  • GitHub
Company
  • About Jentic
  • Careers
  • Contact Us
  • Trust Centre
ISO/IEC 27001:2022 certification badge issued by Prescient SecurityISO/IEC 27001:2022 certification badge issued by Prescient Security

Information Security Management System

Certified to ISO/IEC 27001:2022 by Prescient Security

AICPA SOC for Service Organizations logoAICPA SOC for Service Organizations logo

SOC 2® Type 1 report

Audited by Prescient Assurance

Terms & Conditions•Privacy Policy•
© 2026 Jentic Technology Ltd. All rights reserved.
2 Grattan Court East, Dublin, D02 VX86, Ireland
Switch to light modeSwitch to dark mode
APIs / Media / Google / Reader Revenue Subscription Linking API
Reader Revenue Subscription Linking API logo

Google Reader Revenue Subscription Linking API

Browse all Google APIs
39
AI ReadinessNon-Ready (F)39/100
See full scorecard
Official vendor OpenAPI document · agent-readyMediaContent Deliveryoauth23 EndpointsREST

For Agents

Link, update, and unlink Google reader identities with publisher subscriptions so reader entitlements are recognized across Google surfaces.

Use for: I need to link a Google reader to an active publisher subscription, Update the entitlement metadata when a reader upgrades their plan, Remove the subscription link when a reader cancels, Retrieve the current entitlement state for a Google reader

Not supported: Does not process payments, run paywalls, or send subscriber email - use only to link, update, and unlink Google reader identities with publisher subscription records.

The Reader Revenue Subscription Linking API lets news publishers tie a Google reader identity to a publisher subscription so that signed-in Google users see their entitlements honored across Google surfaces. Publishers exchange reader IDs and subscription metadata with Google to mark a reader as entitled, update existing entitlements, or remove the link when a subscription ends. The API is the connective tissue between a publisher's subscription system of record and Google's reader-facing surfaces.

Jentic One on GithubView OpenAPI Document

Install Jentic One Beta

Connect the Reader Revenue Subscription Linking API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Reader Revenue Subscription Linking 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%2Fgoogleapis.com%2Freader-revenue-subscription-linking" | sh
2

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%2Fgoogleapis.com%2Freader-revenue-subscription-linking" | sh
jentic register       # connects your agent to your Jentic One instance

Jentic 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 Reader Revenue Subscription Linking API.

Create or update a reader-to-subscription link with the publisher's entitlement metadata

Retrieve the current subscription link for a Google reader identity

Delete a reader-subscription link when a reader cancels or unsubscribes

Synchronize entitlement state from a publisher's subscription system of record into Google

Honor reader entitlements consistently across Google reader-facing surfaces

Drive subscription linking from webhook handlers when subscriptions change

Use Cases

Patterns agents use Reader Revenue Subscription Linking API for, with concrete tasks.

★ Initial Reader Onboarding

When a reader signs in to a publisher's site with their Google account and their subscription is verified, the publisher calls Subscription Linking to register the entitlement with Google. From then on, the reader's entitlement is honored on Google reader surfaces.

Call PATCH /v1/publications/{publication}/readers/{reader_id} with subscription metadata when a verified reader signs in for the first time.

Subscription Lifecycle Sync

Publishers run their subscription system of record (Stripe, Recurly, Zuora, in-house) and need entitlement changes there to flow to Google. Webhook handlers on the publisher side translate billing events into Subscription Linking API calls so Google's view of the entitlement always matches the source of truth.

When the billing system fires a subscription.updated webhook, look up the linked Google reader and call the upsert endpoint with the new plan tier and renewal date.

Cancellation and Unlink

When a reader cancels or their subscription lapses, the publisher must remove the entitlement link so Google does not continue to show the reader as entitled. Subscription Linking exposes a delete operation that performs this unlink cleanly.

When a reader cancels, call DELETE /v1/publications/{publication}/readers/{reader_id} to remove the entitlement from Google.

Agent-Driven Entitlement Reconciliation

An agent monitors the publisher's billing data and reconciles entitlement state with Google through Jentic, calling the Subscription Linking API to add, update, or remove links so the Google view of who is entitled stays in sync with the publisher's system of record.

Search Jentic for link a google reader to a subscription, load the schema for the readers upsert operation, and execute it for the affected reader.

Key Endpoints

3 endpoints — the reader revenue subscription linking api lets news publishers tie a google reader identity to a publisher subscription so that signed-in google users see their entitlements honored across google surfaces.

METHOD

PATH

DESCRIPTION

GET

/v1/{+name}

Retrieve a reader-subscription link

PATCH

/v1/{+name}

Create or update a reader-subscription link

DELETE

/v1/{+name}

Delete a reader-subscription link

GET

/v1/{+name}

Retrieve a reader-subscription link

PATCH

/v1/{+name}

Create or update a reader-subscription link

DELETE

/v1/{+name}

Delete a reader-subscription link

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.

R

Reader Revenue Subscription Linking API

- Non-Ready (F)
39/100
73
Foundational Compliance
56
Developer Experience & Jentic Compatibility
16
AI-Readiness & Agent Experience
94
Agent Usability
100
Security
63
AI Discoverability
Powered by JenticScoring Framework 1.0.0 | Scoring Engine 0.4.0
Show dimension breakdown
73

Foundational Compliance

Base layer of spec validity and structural soundness.

Grade: A-Signals: 4
91%

Lint Results

Aggregated quality score from linter diagnostics, weighted by severity.

100%

Resolution Completeness

Percentage of `$ref` references that resolve successfully.

0%

Specification Validity

Checks whether the API description parses successfully and conforms to its declared specification (e.g., OpenAPI).

100%

Structural Integrity

Structural correctness score based on schema issues using logarithmic dampening.

56

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).

100%

Tooling Readiness

Health of API ingestion, bundling, and resolution within Jentic pipelines.

16

AI-Readiness & Agent Experience

Semantic breadth, depth, and agent comprehension for AI systems.

Grade: FSignals: 4
62%

Description Coverage

Coverage of descriptions across API elements.

0%

Error Standardization

Coverage of RFC 9457 Problem Details for error responses.

0%

OperationId Quality

Coverage, uniqueness, and casing consistency of operationIds for AI inference.

0%

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.

100

Security

Trust, risk posture, and security compliance.

Grade: A+Signals: 1
100%

Authentication Strength

Average quality of security schemes based on authentication method strength (weakest link for OAuth2).

63

AI Discoverability

Findability, semantic richness, and reasoning readiness.

Grade: B-Signals: 1
62%

Descriptive Richness

Clarity and depth of descriptions across API elements.

View full reportHow the score is calculatedMore about the dimensions

Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

Score your own APIScoring CLI agent skill
npx @jentic/api-scorecard-cli score <openapi-url>

Why Jentic?

What agents get from Jentic-routed access to this vendor.

Setup

Wiring the Reader Revenue Subscription Linking API by hand means setting up publisher Google OAuth 2.0, refreshing scoped access tokens, and formatting reader resource names for the three endpoints on readerrevenuesubscriptionlinking.googleapis.com. Through Jentic you install once, import the Reader Revenue Subscription Linking API from the API Directory, store the OAuth credential once, and your agent calls it.

Permission scoping

This API puts the reader in the URL path (/v1/{+name}), so a rule can pin your agent to one publication's reader records: it can read entitlements for that scope and nothing else. You choose the operations it may call, so state-changing ones like updating or unlinking a reader are not included unless you add them.

Credential isolation

Your publisher Google OAuth credential is stored once, encrypted, by your own Jentic One instance and a scoped access token is injected at execution time. The credential never enters the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'link a reader' or 'get a reader entitlement', and Jentic returns the matching Subscription Linking operation with its input schema so the agent calls the right endpoint without interpreting the discovery doc for a three-endpoint API.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Complementary

Gmail API

→

Sends transactional subscription emails to readers

Use Gmail when subscription lifecycle events need to trigger transactional email to the reader from a Google-hosted mailbox.

Complementary

AdSense Management API

→

Manages the publisher's ad inventory alongside reader subscriptions

Use AdSense to suppress ad units for entitled readers identified through Subscription Linking.

Complementary

AdMob API

→

Mobile ad management for publishers running app surfaces alongside reader sites

Use AdMob when the publisher's mobile app needs ad management coordinated with subscription entitlements.

FAQs

Specific to using Reader Revenue Subscription Linking API through Jentic.

What authentication does the Reader Revenue Subscription Linking API use?

The API uses Google OAuth 2.0 with publisher-scoped credentials issued through the Reader Revenue Manager onboarding. Through Jentic the OAuth credentials live encrypted in the vault and short-lived access tokens are injected at call time so the refresh token never enters the agent context.

Does this API process payments or charge subscribers?

No, billing stays with the publisher's existing system. This API only links a Google reader identity to a subscription record so Google can recognize the entitlement on Google surfaces.

What are the rate limits for the API?

The API exposes three operations and is intended for event-driven calls in response to subscription lifecycle changes. Rate limits are documented by the Reader Revenue Manager team and are sized for normal subscriber-event throughput, not for full-base reconciliation sweeps in tight loops.

How do I unlink a reader through Jentic?

Search Jentic for unlink a google reader from a subscription, load the schema for the readers delete operation which maps to DELETE /v1/{+name} on a reader resource, and execute it with the reader's resource name when the subscription is cancelled.

Is the Reader Revenue Subscription Linking API free?

API access is included with Reader Revenue Manager onboarding for eligible publishers and is not separately metered. Eligibility and onboarding details are documented on the Reader Revenue Manager publisher site.

How do I update an entitlement when a reader changes plan?

Call the upsert operation on the reader resource with the new plan tier, renewal date, and any other entitlement metadata; the API replaces the prior link in place rather than requiring a delete-then-create.

Can I limit what my agent is allowed to do with the Reader Revenue Subscription Linking API?

Yes. Because you run Jentic One yourself, your own rules decide which of the three operations your agent may call and which publisher OAuth credential it uses. Since this API puts the reader in the URL path (/v1/{+name}), a rule can pin the agent to one publication's reader records, and you can allow only the read (GET) operation while withholding the state-changing PATCH upsert and DELETE unlink operations unless you explicitly grant them. The scoped access token is injected at call time, so the agent can act on entitlements only within the boundaries you set.

GET STARTED

Start building with Reader Revenue Subscription Linking API

Explore with Jentic One
View OpenAPI Document