Quiltt
for LuumenAI
Read Quiltt profiles and webhook subscriptions, change them as approved steps
Connect Quiltt and the agent can read your Profiles, webhook subscriptions, and institution lookups directly in the terminal. Ask which subscriptions point at a retired callback URL, or what a Profile holds before you edit it. Changes — creating a Profile, repointing a webhook, removing a subscription — are previewed first and go through approval by default.
The Quiltt toolbox
10 tools: 5 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet ProfileRetrieve one Profile by its Quiltt Profile ID or UUID.
- ReadList Finicity Remote DataList one page of Quiltt resource IDs with Finicity Remote Data for the selected resource type.
- ReadList ProfilesReturn one page of Profiles in the Quiltt Environment and a cursor for the next page.
- ReadList Webhook SubscriptionsReturn one page of webhook subscriptions and a cursor for the next page, including callback URLs, event types, and disabled state.
- ReadSearch InstitutionsFind financial institutions associated with a US Federal Reserve routing number.
- WriteCreate ProfileCreate a Profile in the Quiltt Environment with optional identity, contact, address, and custom metadata fields. Approval by default
- WriteCreate Webhook SubscriptionCreate a webhook subscription that sends selected Quiltt events to an HTTPS callback URL; this registers the callback but does not verify delivery. Approval by default
- WriteDelete Webhook SubscriptionPermanently remove one webhook subscription so Quiltt stops sending events to its callback URL. Approval by default
- WriteUpdate ProfileUpdate explicitly supplied contact, legal identity, address, or custom metadata fields on an existing Quiltt Profile. Approval by default
- WriteUpdate Webhook SubscriptionUpdate explicitly supplied fields on a Quiltt webhook subscription, including its name, HTTPS callback URL, or event types. Approval by default
One prompt, start to finish
What a governed Quiltt 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 — create profile, create webhook subscription, delete webhook subscription, update profile, 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 Quiltt — 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
GitHubRepos, actions, and runbook code as context and as actions.
GitLabMerge requests and pipelines proposed, triggered, and rolled back.
BitbucketRead commits, diffs, and branches in Bitbucket, then open the fix as a held write.
Azure DevOpsAzure DevOps repos and pipelines as context — and as approved actions.Put Quiltt to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.