CallerAPI MCP integration for AI agents.
Connect AI agents to CallerAPI through 2 structured actions, including get phone number information and get user information. Review authentication, inputs…
- ACTION CONTRACTS
- 2
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the CallerAPI integration exposes
The CallerAPI Agent App exposes 2 provider-backed actions for communication and security work. Its current contract lets an authorized agent look up callerapi spam reputation, business details, complaints, and optional hlr carrier data for a phone number and retrieve the authenticated callerapi account email and credit balance. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected CallerAPI account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real CallerAPI capabilities.
Showing 2 of 2 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_phone_number_informationREADLook up CallerAPI spam reputation, business details, complaints, and optional HLR carrier data for a phone number.
INPUTS: phone / hlr
get_user_informationREADRetrieve the authenticated CallerAPI account email and credit balance.
INPUT CONTRACTS
Know what the action needs before it runs.
get_phone_number_information
phoneREQUIRED- The phone number to look up. CallerAPI accepts E.164 input.
hlrOPTIONAL- Whether to include HLR carrier data in the CallerAPI lookup.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Phone Number Information
Look up CallerAPI spam reputation, business details, complaints, and optional HLR carrier data for a phone number. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_phone_number_informationVerify with Get User Information
Retrieve the authenticated CallerAPI account email and credit balance. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
get_user_informationSAFETY BOUNDARY
Operate CallerAPI with explicit limits
- Authorize CallerAPI with API key and grant only the provider access required by the selected actions.
- The current action names appear read-oriented, but returned CallerAPI data may still be sensitive and should be minimized before it enters model context.
- Do not infer permission from catalog visibility. Workspace policy, connection identity, and upstream authorization still govern execution.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in CallerAPI rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the CallerAPI task completed successfully.
CONNECTION MODEL
API key
CallerAPI key sent with the x-auth header. Get it from the CallerAPI dashboard: https://callerapi.com/dashboard
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 2
- WRITE SIGNALS
- 0
- HIGH IMPACT
- 0
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by CallerAPI.