Grokbot + AgentLine
Give Grokbot a number it can actually call from
Grokbot already runs on a cloud computer. AgentLine gives it a real US or Canadian number so it can place calls, answer inbound voice, and read SMS without you wiring Twilio.
One skill file
Install the AgentLine skill on Grokbot, set AGENTLINE_API_KEY, and ask it to provision a number. The same skill works in Cursor-connected Grokbot sessions.
Get yourself a phone number and call me. Follow https://agentline.cloud/skill.mdWhy Grokbot needs its own number
A number the bot owns
Grokbot gets its own E.164 identity. It never borrows your cell or a shared trunk when it needs to call someone.
Calls from the cloud computer
Grokbot already has a desktop, a terminal, and apps. AgentLine is the phone line for that machine.
Same skill as every other runtime
skill.md installs the same way as Claude Code and Cursor. No Grokbot-specific SIP config.
Prompt
Paste this to your Grokbot agent. It tells the agent how to use its number.
Get yourself a phone number and call me. Follow https://agentline.cloud/skill.mdSet up Grokbot
How the skill and the service land on this runtime.
1. Set your API key
The relay reads AGENTLINE_API_KEY from the environment. Export it on Grokbot's cloud computer.
export AGENTLINE_API_KEY="al_live_..."2. Install the relay service
Grokbot's cloud computer is persistent with a real terminal, so the relay service survives. Grokbot has no built-in harness, so --handler must be a shell command that reads a caller prompt on stdin and prints the reply — without it the relay installs but cannot answer calls.
python -c "import urllib.request; urllib.request.urlretrieve('https://api.agentline.cloud/static/agentline_relay.py','agentline_relay.py')"
python agentline_relay.py install --agent-id agt_xxx --runtime custom --handler "YOUR_HANDLER_COMMAND"