The Old Reader API

Name: The Old Reader API
Brand: The Old Reader API
Availability: InStock

✓ Official Vendor SpecPaymentsBilling SubscriptionsapiKey18 EndpointsREST

For Agents

Programmatically authenticate and obtain auth token, get authentication token. Covers 18 operations with apiKey authentication.

Install Jentic One Beta

Connect the The Old Reader API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the The Old Reader 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.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | 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 The Old Reader API.

Authenticate and obtain auth token

Get authentication token

Check API status

List all subscriptions

GET STARTED

Start building with The Old Reader API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use The Old Reader API for, with concrete tasks.

★ Payments Operations

Use the The Old Reader API to perform payments operations programmatically. The API provides 18 endpoints covering core functionality including authenticate and obtain auth token, get authentication token, get authenticated user details.

Call POST /accounts/ClientLogin to authenticate and obtain auth token

Automated Accounts Management

Automate accounts operations by combining multiple The Old Reader API endpoints. Agents can get authentication token and then get authenticated user details in a single workflow.

Call GET /reader/api/0/token to get authentication token, then verify the result

AI Agent Integration via Jentic

AI agents discover and call The Old Reader API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle apiKey tokens manually.

Search Jentic for 'authenticate and obtain auth token', load the operation schema, and execute with Jentic-managed credentials

Key Endpoints

18 endpoints — a google reader-compatible rss reader api with authentication, subscriptions, items, folders, friends, and comments management.

METHOD

PATH

DESCRIPTION

POST

/accounts/ClientLogin

Authenticate and obtain auth token

GET

/reader/api/0/token

Get authentication token

GET

/reader/api/0/user-info

Get authenticated user details

GET

/reader/api/0/status

Check API status

GET

/reader/api/0/subscription/list

List all subscriptions

POST

/reader/api/0/subscription/quickadd

Add a subscription

POST

/reader/api/0/subscription/edit

Edit a subscription

GET

/reader/api/0/unread-count

Get unread counts

POST

/accounts/ClientLogin

Authenticate and obtain auth token

GET

/reader/api/0/token

Get authentication token

GET

/reader/api/0/user-info

Get authenticated user details

GET

/reader/api/0/status

Check API status

GET

/reader/api/0/subscription/list

List all subscriptions

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

The Old Reader API apiKey credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'authenticate and obtain auth token') and Jentic returns the matching The Old Reader API operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct The Old Reader API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

FAQs

Specific to using The Old Reader API through Jentic.

What authentication does the The Old Reader API use?

The The Old Reader API uses an API key passed in the `Authorization` header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.

Can I authenticate and obtain auth token with the The Old Reader API?

Yes. Use the POST /accounts/ClientLogin endpoint. The API returns structured JSON responses that agents can parse and act on directly.

What are the rate limits for the The Old Reader API?

Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.

How do I authenticate and obtain auth token through Jentic?

Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'authenticate and obtain auth token'. Jentic returns the matching The Old Reader API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.

How many endpoints does the The Old Reader API have?

The The Old Reader API exposes 18 endpoints covering accounts, reader operations.

The Old Reader API

Connect the The Old Reader API to your agent

Capabilities

Start building with The Old Reader API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs