Read parsed documents and change extraction schemas as approved steps
Connect Airparser and Luumen can see your inboxes, their extraction schemas, and the parsed output of any document you have processed. Ask why a field came back empty, or which documents failed last week. When the fix is a schema change, a new inbox, or a test upload, Luumen shows the plan first and waits for your approval. Authentication is by API key.
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Airparser run looks like inside Luumen.
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 — clone extraction schema, create inbox, delete inbox, parse document synchronously, and more — 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.
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 Airparser — 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.
Connect in minutes. Every action scoped, approved, and audited from day one.