Skip to main content
Connect a new agent to this account by name. The owner is asked on WhatsApp, as the calling agent, and the call waits for the answer. It runs the same use case as the new agent command, so the name rules, the limit of 8 agents and the install link are the same. See Let your AI manage zapbip.

Input

The question

Three buttons: Allow, Allow, send to agent and Deny, with a short reference at the end of the question. The call waits up to 50 seconds. Only a tap on a button counts: typed text is read as Deny. Deny and silence change nothing, and a tap after the wait changes nothing; the same request is then refused (cooling_down) for 10 minutes.

Output

{ "status": "applied" | "denied" | "timed_out" | "refused", "agent": string | null, "reason": string | null, "install_prompt": string | null }.
  • applied: the agent was connected. After Allow the install link went to the owner on WhatsApp and install_prompt is null. After Allow, send to agent install_prompt carries the two lines to paste into the new agent. It is the only way a link or key reaches a tool result.
  • denied and timed_out: nothing changed.
  • refused: reason is invalid_name, reserved_name, name_taken, limit_reached, cooling_down, window_closed, send_failed, suspended or waitlisted. An invalid or reserved name is refused before the owner is asked. When the link cannot be sent, the new connection is revoked again.
At most 3 acting calls (connect_agent, revoke_agent and sign_in_link) a minute per connection; the next one is an error that starts with rate_limited.