This page defines the canonical CALL ANYTHING vocabulary for English readers, README references, compare pages, and answer-engine extraction. These terms should stay stable across the site.
The minimum vocabulary required to understand CALL ANYTHING.
productized capability endpoint
A Hotline is the capability unit in CALL ANYTHING: a standardized contract that bundles identity, billing, approval, observability, and routing into the protocol layer so any agent can discover, call, and settle it.
A Hotline may expose an MCP server, an HTTP endpoint, or a SKILL.md wrapper, but those are access surfaces. The product itself is the Hotline.
one-person company
OPC stands for one-person company: an individual packaging private expertise into digital twins that agents can call 24/7, with protocol-level billing and settlement built in.
CALL ANYTHING treats the OPC as a first-class seller persona rather than a side case hidden behind generic API infrastructure.
OPC digital twin
A digital twin is the service form of an OPC's expertise after it has been packaged as one or more Hotlines that agents can call continuously without exposing the underlying workflow or prompt stack.
Caller and Responder are the two sides of every Hotline interaction.
agent-side caller
A Caller is the AI agent or agent team that invokes a Hotline. It discovers available capabilities through catalog APIs and reads a shared result_package shape instead of writing custom client code for every provider.
capability operator
A Responder is the operator behind a Hotline, usually a one-person company or a small team. It keeps the core implementation private, runs the business logic locally, and returns protocol-shaped results to Callers.
How public discovery works at the protocol layer.
public hotline directory
The Marketplace is the public directory of Hotlines on callanything.xyz. It lets agents discover responders, compare capability summaries, inspect versions, and decide what to call next.
Implementation-level concepts that appear in docs, APIs, and examples.
local runtime daemon
The Supervisor is the local process that mounts Hotlines, manages sessions, forwards calls, and records operational events for both Caller and Responder roles.
versioned capability identifier
A Hotline ID is the globally unique, versioned name of a Hotline. It lets a Caller pin exactly which capability and version it wants to invoke.
shared protocol result envelope
A result package is the shared response structure defined by the protocol. It gives every Hotline the same outer shape for status, output, timing, and identity signals, so agents only learn one parsing model.
available hotline list
A Catalog is the Hotline list exposed by the Supervisor. A Caller uses it to determine which capabilities are currently installed, routable, and callable in its runtime.
hotline capability bundle
A Template Bundle is the minimum descriptive package for publishing a Hotline: summary, schemas, examples, risk notes, and adapter shape. Review and discovery both depend on it.
Control-plane concepts for teams and operators.
human review rule
An Approval Policy is the rule set a Caller team applies to a Hotline so high-risk calls can require human review before execution or settlement.
agent-team control plane
The Caller Console is the control surface for agent teams. It covers discovery, approvals, runtime history, billing, and version awareness across every Hotline the team uses.
operator workspace
The Responder Console is the operating surface for the seller side. It is where an OPC manages Hotline versions, pricing, review status, and usage signals for its digital twins.