Readwise Reader
for LuumenAI

Read, sort, and file your Readwise Reader library from the terminal

Your Reader library becomes something you can query and tidy from the terminal. Luumen lists documents, filters by location or tag, and reads the tag list for context. Saving a link, retagging a batch of articles, or moving something to the archive is a previewed step you approve first. Connects with an API key.

The Readwise Reader toolbox

6 tools: 2 read, 4 write. Reads answer instantly. Writes require approval by default. Everything is logged.

  • ReadList DocumentsList, filter, incrementally sync, or fetch a specific Reader document.
  • ReadList TagsList tags in the connected Reader library, returning one page and a cursor for the next page.
  • WriteBulk Update DocumentsPartially update up to 50 Reader documents in one request and return a success or error result for every document. Approval by default
  • WriteDelete DocumentPermanently delete one Reader document by its ID. Approval by default
  • WriteSave DocumentSave a URL or supplied HTML as a document in the connected Reader library, with optional metadata, location, and tags. Approval by default
  • WriteUpdate DocumentPartially update supported fields on one Reader document by ID; omitted fields remain unchanged. Approval by default

One prompt, start to finish

What a governed Readwise Reader run looks like inside Luumen.

Questions

How does LuumenAI connect to Readwise Reader?

Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.

Can LuumenAI change things in Readwise Reader on its own?

Read actions answer immediately. Anything that writes — bulk update documents, delete document, save document, update document — is shown as a plan and requires approval by default, including the 1 action classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.

Who gets access to the integration?

You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.

Is there an audit trail?

Every call to Readwise Reader — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.

Put Readwise Reader to work with Luumen

Connect in minutes. Every action scoped, approved, and audited from day one.