OpenAlex
for LuumenAI
Search scholarly metadata and keep private OpenAlex collections current
OpenAlex holds metadata on works, authors, institutions, sources, topics, funders, and awards. Luumen reads it on request: resolve an ambiguous name, pull a work record, group results by year or venue, or check your API key budget before a large query. Changes to your private collections are previewed first, then applied on approval.
The OpenAlex toolbox
14 tools: 9 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadAutocomplete EntitiesResolve a partial name or title to likely OpenAlex entity IDs before filtering or retrieving metadata.
- ReadDownload Work ContentDownload an OpenAlex-cached PDF or gzipped GROBID TEI file for a work.
- ReadGet CollectionGet metadata for one private OpenAlex collection owned by the connected user.
- ReadGet Metadata EntityRetrieve one OpenAlex work, author, source, institution, topic, keyword, publisher, funder, award, taxonomy item, country, continent, or language by its supported identifier.
- ReadGet Rate Limit StatusValidate the connected OpenAlex API key and inspect daily budget, prepaid balance, reset timing, and current endpoint costs before expensive queries or downloads.
- ReadList Collection EntitiesList one page of entity IDs in an owned private collection together with collection metadata and page totals.
- ReadList My CollectionsList private OpenAlex collections owned by the connected API-key user, optionally finding collections that contain an entity.
- ReadQuery Metadata EntitiesSearch, filter, sort, sample, select, or group one OpenAlex metadata resource other than works, including authors, venues, organizations, taxonomy, geography, awards, and enumerations.
- ReadQuery WorksSearch, filter, sort, sample, select, or group scholarly works.
- WriteAdd Collection EntitiesBulk-add one or more matching OpenAlex entity IDs to an owned collection without duplicating existing memberships. Approval by default
- WriteCreate CollectionCreate a private, single-entity-type OpenAlex collection, optionally with an initial bounded set of entity IDs. Approval by default
- WriteDelete CollectionPermanently delete exactly one owned private OpenAlex collection and all of its collection memberships. Approval by default
- WriteRemove Collection EntitiesBulk-remove one or more entity memberships from an owned private OpenAlex collection without deleting the underlying OpenAlex entities. Approval by default
- WriteUpdate CollectionUpdate a private collection's name or description, or change its entity type while the collection is empty. Approval by default
One prompt, start to finish
What a governed OpenAlex run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
Read actions answer immediately. Anything that writes — add collection entities, create collection, delete collection, remove collection entities, and more — is shown as a plan and requires approval by default, including the 2 actions classified as destructive. Administrators configure that per tool, so you decide exactly which actions can ever run unattended.
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.
Every call to OpenAlex — 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.
Often connected alongside
All integrations
PostgreSQLQuery PostgreSQL state safely; maintenance held for approval.
MySQLQuery MySQL state safely; maintenance held for approval.
Microsoft SQL ServerQuery Microsoft SQL Server state safely; maintenance held for approval.Oracle DatabaseQuery Oracle Database state safely; maintenance held for approval.Put OpenAlex to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.