Callerapi
for LuumenAI
Check number reputation and manage daily spam report webhooks from the terminal
Connect CallerAPI and ask about any phone number in plain language: reputation, carrier, business details, FTC complaints. Check your account's credit usage, review which endpoints receive daily spam reports, and send a test payload before you trust one. Changes to subscriptions are previewed and approved first.
The Callerapi toolbox
7 tools: 4 read, 3 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadGet Phone Number InformationRetrieve detailed information about a specific phone number, including reputation, business and carrier details, and FTC complaints.
- ReadGet User InformationRetrieve information about the authenticated user, including email and credit usage details.
- ReadList Webhook SubscriptionsList all webhook subscriptions for daily spam reports.
- ReadTest WebhookSend a sample webhook payload to test your webhook endpoint integration.
- WriteDispatch Reports ManuallyManually trigger today's spam reports webhook delivery for enterprise clients. Approval by default
- WriteSubscribe to Daily Spam ReportsSubscribe to daily spam report webhooks for enterprise clients. Approval by default
- WriteUnsubscribe from Daily ReportsUnsubscribe from daily spam report webhooks. Approval by default
One prompt, start to finish
What a governed Callerapi 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 — dispatch reports manually, subscribe to daily spam reports, unsubscribe from daily reports — 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 Callerapi — 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
SlackRead the incident thread; post updates and approvals back.
GmailVendor and alert mail as context; replies drafted for review.
Microsoft TeamsRead Teams channels and chats for context, then make membership changes as approved steps.
DiscordRead Discord command permissions and app context, then change them with approvalPut Callerapi to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.