Read Fidel API programs, offers, and cards, then make changes as approved steps
Connect Fidel API and Luumen can answer questions about your card-linking setup without you opening the dashboard: which programs exist, which locations sit under a brand, which cards activated an offer, what a given transaction looked like. Changes — new offers, locations, webhooks, MID requests — are previewed and sent for approval first. Luumen authenticates with an API key.
39 tools: 22 read, 17 write. Reads answer instantly. Writes require approval by default. Everything is logged.
What a governed Fidel API 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 — create brand, create brand webhook, create location, create mid request, and more — is shown as a plan and requires approval by default, including the 4 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 Fidel API — 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.