Readwise connector for AI agents

Tools your reading agent reaches for on Readwise, scoped per user.

CALL ANY TOOL

27 tools for reading highlights in Readwise: list, export, create, and update highlights, tag books and highlights, run the daily review, and save and organize documents in Reader.

readwise_check_auth

Check auth

Verify that the connected Readwise access token is valid. Returns an empty response with HTTP 204 when the token is valid and an auth error otherwise. Use it to diagnose authentication failures before calling other tools.

Parameters

Name

Type

Required

Description

—

No parameters required

readwise_complete_daily_review

Complete daily review

readwise_create_book_tag

Create book tag

readwise_create_highlight_tag

Create highlight tag

readwise_create_highlights

Create highlights

readwise_delete_book_tag

Delete book tag

readwise_delete_highlight

Delete highlight

readwise_delete_highlight_tag

Delete highlight tag

readwise_export_highlights

Export highlights

readwise_get_book

Get book

readwise_get_daily_review

Get daily review

readwise_get_highlight

Get highlight

readwise_list_book_tags

List book tags

readwise_list_books

List books

readwise_list_highlight_tags

List highlight tags

readwise_list_highlights

List highlights

readwise_reader_bulk_update_documents

Reader bulk update documents

readwise_reader_create_highlight

Reader create highlight

readwise_reader_delete_document

Reader delete document

readwise_reader_list_documents

Reader list documents

readwise_reader_list_tags

Reader list tags

readwise_reader_save_document

Reader save document

Save a URL, or your own HTML, to the user's Reader library as a new document. Returns the document id and its Reader url; the status is 201 for a new document and 200 when it already exists. Use it to add articles, PDFs or any web page to Reader. Use reader_create_highlight to highlight text in a document that is already saved. Limited to 50 requests per minute.

Parameters

Name

Type

Required

Description

url

string

Required

The document's unique URL. If you have none, use a made-up value such as https://yourapp.com#document1. Example: https://example.com/article/.

author

string

Optional

Author of the document; overrides the author found while parsing. Example: Paul Graham.

tags

array

Optional

List of tag names to attach to the document. Example: ["reading-list", "ai"].

title

string

Optional

Title of the document; overrides the title found while parsing. Example: How to Do What You Love.

readwise_reader_update_document

Reader update document

readwise_update_book

Update book

readwise_update_book_tag

Update book tag

readwise_update_highlight

Update highlight

readwise_update_highlight_tag

Update highlight tag

Build your Agent

Same auth pattern across LangChain, OpenAI, Anthropic, and Google ADK.

import { ScalekitClient } from "@scalekit-sdk/node";
import { createReactAgent } from "@langchain/langgraph/prebuilt";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

// Readwise tools scoped to this user
const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["readwise"], toolNames: [
    "readwise_list_books",
    "readwise_list_highlights",
    "readwise_reader_save_document"] },
  pageSize: 100,
});

const agent = createReactAgent({ llm, tools });
await agent.invoke({ messages: [{ role: "user", content: "Show my highlights from The Mom Test" }] });

import OpenAI from "openai";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["readwise"] }, pageSize: 100,
});

const res = await openai.chat.completions.create({
  model: "gpt-5",
  messages: [{ role: "user", content: "Show my highlights from The Mom Test" }],
  tools,
});

// Execute the tool call with the user's vaulted Readwise API key
await sk.tools.executeTool(res.choices[0].message.tool_calls[0], "user_123");

import Anthropic from "@anthropic-ai/sdk";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["readwise"] }, pageSize: 100,
});

const msg = await anthropic.messages.create({
  model: "claude-sonnet-5",
  max_tokens: 1024,
  messages: [{ role: "user", content: "Show my highlights from The Mom Test" }],
  tools,
});

// Tool call runs with the user's vaulted Readwise API key
await sk.tools.executeTool(msg.content, "user_123");

import { Agent } from "@google/adk/agents";
import { ScalekitClient } from "@scalekit-sdk/node";

const sk = new ScalekitClient(env.SCALEKIT_ENV_URL, env.SCALEKIT_CLIENT_ID, env.SCALEKIT_CLIENT_SECRET);

const { tools } = await sk.tools.listScopedTools("user_123", {
  filter: { connectionNames: ["readwise"] }, pageSize: 100,
});

const agent = new Agent({
  name: "reading_agent",
  model: "gemini-2.5-pro",
  instruction: "Readwise tools scoped to this user",
  tools,
});

await agent.run("Show my highlights from The Mom Test");

Try these prompts

Copy any prompt into your agent. Each maps directly to a Readwise tool. Click to copy, paste into your agent, done.

Highlights

Copy the prompt

Copied

Show my highlights from The Mom Test.

Copy the prompt

Copied

Export every highlight I made in the last 7 days.

Copy the prompt

Copied

Add a note to my latest highlight from Atomic Habits.

Reader

Copy the prompt

Copied

Save https://example.com/agent-auth to my Reader library.

Copy the prompt

Copied

List Reader documents in Later tagged research.

Copy the prompt

Copied

Move these 5 Reader documents to Archive.

Review and tags

Copy the prompt

Copied

What's in my latest daily review?

Copy the prompt

Copied

Mark my daily review as complete.

Copy the prompt

Copied

Tag the book Deep Work with focus.

SEE HOW AUTH WORKS

Each user connects their own Readwise API key once, and Scalekit sends it with every call. Keys stay vaulted, every call is scope checked, and every action is logged.

Authorize

Your user connects

Readwise

once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access

Who:

user ‘A’

when:

Once per user

access:

Limited to user

Store

Their

Readwise

token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection

vault:

encrypted

scope:

per-user

tokens:

auto-refreshed

Resolve

When your agent calls a

Readwise

tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs

speed:

~40ms

check:

before every call

seen by:

nobody

Audit

Every

Readwise

tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it

history:

90 days

export:

SIEM-ready

logged:

every call

Test other agents

See the same per-user auth pattern across other productivity and knowledge connectors.

GTM and RevOps Teams

Competitive intelligence briefing agent

Scans Gong calls for competitor mentions, matches each one to its Notion battlecard, and DMs every affected rep a single Slack digest per cycle. Every call runs as the PMM who owns the briefing, never a shared bot.

Support and Ops Teams

Meeting prep

Pulls agenda, participant context, and open action items before every meeting.

Why Scalekit

Secure your agent's access. Connectors ship in minutes

01.

Shared tokens break per-user analytics

A shared Readwise API key looks fine in a demo. In production every highlight the agent saves looks like one service account, and you cannot tell which user triggered it. Scalekit resolves the credential of the actual user who triggered the agent, never a shared bot.

// shared key
audit → bot_service_account

// scalekit
audit → user_abc ✓

02.

Authentication is not authorization

03.

Multi-tenancy is architectural

04.

Readwise today. Ten connectors tomorrow.

“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”

Venu Madhav Kattagoni

Head of Engineering / Von

FAQs

Frequently Asked Questions

Does the agent access Readwise as the user or through a shared key?

As the user. Each user connects their own Readwise API key once, and Scalekit sends it with every call. Highlights, tags, and Reader documents the agent saves are attributed to that user in your audit trail, not a shared service account.

Where is the Readwise API key stored?

In Scalekit's managed AES-256 token vault, namespaced per tenant. To rotate it, the user reconnects with a new API key. Revocation is a single dashboard action. Credentials never appear in prompts, logs, or LLM context.

Can I limit what the agent does in Readwise?

Yes. Filter by tool name in listScopedTools to expose only what you want, for example the list and export tools without readwise_reader_delete_document, which permanently deletes a Reader document with its highlights, or readwise_delete_highlight. Scalekit also enforces scope checks before every API call.

What happens when a user revokes Readwise access?

The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.

Does the connector cover both Readwise and Reader?

Yes. The Readwise tools work with the books, articles, podcasts, and highlights in the user's Readwise library, and the Reader tools save, list, update, and delete documents in Reader. One connection covers both.