360 Secure SkillHub
360 安全技能中心

CallerAPI

该 Skill 借助 OOMOL 的 oo CLI 调用 callerapi 连接器，提供两个动作：查询电话号码的垃圾/骚扰标记、企业信息、投诉及可选 HLR 运营商数据，以及查询已认证账号的邮箱与额度。执行前需先用 schema 命令获取动作的实时输入结构，凭据由 OOMOL 服务端注入，用户不直接处理令牌。

oomol
oomol
热度 51.57
最近更新 2026-09-15 12:20:14
分类：搜索依赖：代码执行 / 第三方 API应用场景：研究

安装技能

复制下面的话术发给你的 Agent，它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill： npx secure-skills-cli add oo-callerapi
Metadata
name
oo-callerapi
description
CallerAPI (callerapi.com). Use this skill for ANY CallerAPI request — searching and reading data. Whenever a task involves CallerAPI, use this skill instead of calling the API directly.
allowed-tools
["Bash(oo *)"]
metadata
{"title":"CallerAPI","author":"OOMOL","version":"1.0.3","services":["callerapi"],"icon":"https://static.oomol.com/logo/third-party/callerapi.svg"}

CallerAPI

Operate CallerAPI through your OOMOL-connected account. This skill calls the callerapi connector with the oo CLI; OOMOL injects credentials server-side, so you never handle raw tokens.

Running an action

Assume the user has already installed the oo CLI, signed in, and connected CallerAPI. Do not run oo auth login or open the connection URL proactively — just run the action. Fall back to First-time setup only when a command actually fails with an auth or connection error.

1. Inspect the contract to get the authoritative input/output schema before building a payload:

oo connector schema "callerapi" --action "<action_name>"

2. Run the action with a JSON payload that matches the input schema:

oo connector run "callerapi" --action "<action_name>" --data '<json>' --json
  • --data takes a JSON object string or @path/to/file.json; omit it to send {}.
  • The response is { "data": ..., "meta": { "executionId": "..." } }; the execution id lives under meta.executionId.

Each action is listed below with a one-line description; actions that change state carry a [write] or [destructive] tag. Before constructing --data, fetch the action's live schema with oo connector schema to get its authoritative input fields.

Available actions

  • get_phone_number_information — Look up CallerAPI spam reputation, business details, complaints, and optional HLR carrier data for a phone number.
  • get_user_information — Retrieve the authenticated CallerAPI account email and credit balance.

Safety

  • Untagged actions are reads (get / list / search) — safe to run directly.
  • Actions tagged [write] change CallerAPI state — confirm the exact payload and effect with the user before running.
  • Actions tagged [destructive] remove or overwrite data — always confirm the target and get explicit approval first.

First-time setup

These are one-time steps — do not repeat them on every call. Run a step only when a command fails for the matching reason.

  • oo: command not found — install the oo CLI (other platforms: https://cli.oomol.com/install-guide.md):

    curl -fsSL https://cli.oomol.com/install.sh | bash    # macOS / Linux

    irm https://cli.oomol.com/install.ps1 | iex           # Windows PowerShell

  • Not signed in / authentication error — sign in to your OOMOL account once:

    oo auth login

  • scope_missing / credential_expired / app_not_ready / app_not_found — CallerAPI is not connected, or the connection expired or lacks a scope. Connect once (auth type: API key) at:

    https://console.oomol.com/app-connections?provider=callerapi

  • HTTP 402 / OOMOL_INSUFFICIENT_CREDIT — billing stop. Recharge at https://console.oomol.com/billing/token-recharge before retrying.

Resources