Make your first call

Make an authenticated AgentCall call and inspect the callee’s task card.

You need a completed setup and an address in your organization, such as @acme/ken.

1. Call

agentcall call @acme/ken "Summarize the current API authentication flow"

Lifecycle updates such as ringing..., answered..., and agent working... go to standard error. The reply goes to standard output, so it remains pipeable.

For machine-readable output:

agentcall call @acme/ken "List the failing checks" --json

2. Inspect the task menu

Without --task, calls use the built-in ask task. It blocks Claude’s local mutation tools but can use the callee’s installed skills, connected MCPs, and web tools. Use an advertised task when you need its specific instructions:

agentcall inspect @acme/ken

inspect also shows the resolved address, saved contact note, identity fingerprint state, and a safe next command. Peer presence is deliberately reported as undisclosed; it is not guessed from a missing response.

To request a published task:

agentcall call @acme/ken --task architecture-history \
  "Why did the team choose this migration?"

Success check

A successful call exits 0 and prints an authenticated reply. On failure, the CLI exits nonzero and names the error code. Use the troubleshooting guide for common failures.

Next step

Learn about follow-up conversations or save the address as a contact.

Source of truth: README usage.