On November 17, 2026 Cognition launched Devin Bots: persistent agents that own a goal, run teams of Devin sessions in parallel, and bring only the decisions that need you to a Needs You inbox. A Bot can fix a bug, ship it, and watch the metrics. What it cannot do is call the customer who reported the bug, or receive the SMS code that the sign-in flow it is testing sends. AgentLine fills that gap with a real US or Canada number for a hosted phone agent the Bot can set up and use, on plans from $20 a month; $3.00 a month per extra number plus $0.12 a minute beyond the plan.
The Short Answer
To give a Devin Bot a phone number, create an AgentLine API key just for the Bot, store it in Devin as the secret AGENTLINE_API_KEY, and grant it to the Bot. Then ask the Bot to read agentline.cloud/skill.md, create a hosted phone agent, and provision a US or Canada number once you approve it in Needs You. The Bot can place calls, read transcripts, and send and receive SMS on its own schedule. The full step-by-step guide lives at Devin Bots + AgentLine.
What Devin Bots Are
A Devin session handles one request. A Devin Bot keeps one conversation, its own memory, and its own automations for an outcome it owns, such as keeping an Android app at parity with iOS or watching for latency regressions. It breaks the goal down, starts as many Devin sessions as the work needs, each on its own cloud machine, evaluates the results, and decides what to do next. It can run on schedules and triggers, coordinate with other Bots, and you reach it in the Devin app, in Slack, or by text.
Bots come with Devin's Max plan ($200 a month) for individuals and the Teams and Enterprise plans for groups. A Bot's usage bills to its creator by default. A shared Bot lends its creator's secrets, sign-ins, and memory to everyone it is shared with, which matters for the AgentLine key below.
Where a Bot Needs a Phone
Most of a Bot's work happens in repositories, CI, and ticket trackers. Some of it ends at a phone:
- A support Bot that ships a fix and calls the customer to confirm it works
- A QA Bot that tests the SMS sign-in or two-factor flow of the app it is building
- A product Bot that tests an inbound voice or IVR feature end to end
- A Bot that calls a vendor or an on-site contact who only answers the phone
- A Bot that texts a field team when a deploy changes their workflow
Cognition lets you text or call your Bot to check on its work. That line is for you. An AgentLine number is for everyone else.
How the Bot and AgentLine Split the Work
- The Bot owns the goal, writes the phone agent's prompt, and calls AgentLine's API or MCP tools with its own key.
- AgentLine provides the number, carries the call, transcribes the caller, and speaks the replies.
- You approve the prompt, the number purchase, and new contacts from the Bot's Needs You inbox.
How to Set It Up
- Create an AgentLine account and a separate API key for this Bot.
- In Devin, add the key as the secret AGENTLINE_API_KEY and grant it to the Bot. Teams that use MCP in Devin can add https://api.agentline.cloud/mcp instead.
- Tell the Bot the outcome the line serves and ask it to read the skill.
- Approve the phone agent's prompt and a US or Canada number (included in your plan; $3.00/month beyond it).
- Have the Bot call your own phone first and report the transcript.
Here is a prompt you can send to your Bot:
Read https://agentline.cloud/skill.md. Using AGENTLINE_API_KEY, create a hosted AgentLine phone agent for this goal with a prompt I approve. Put the number purchase and any call to a new contact in my Needs You inbox before you act.
What It Costs
- Phone number: US or Canada, included in plans from $20/month; $3.00/month each beyond the plan
- Calls: $0.12/minute, billed per second after a one-minute minimum; a 0-second call is free
- SMS: $0.02/message on the same number, sent or received
- Devin Bots: on Devin's Max, Teams, and Enterprise plans, billed to the Bot's creator
What to Know Before You Start
- Give the Bot its own AgentLine key. A shared Bot lends its secrets to everyone it is shared with, and a dedicated key is easy to revoke.
- Ask the Bot to save the agent ID and number in its memory and to list existing numbers before it provisions, so a scheduled run does not buy a second one.
- The hosted phone agent talks on its own from the approved prompt. Live lookups during a call need a persistent HTTPS webhook handler; a Devin session that ends is not a webhook server.
- The phone agent should say it is an AI assistant at the start of every call and give any required recording or transcription notice.
- This is an independent AgentLine guide, not an official Cognition integration.
Templates That Fit Devin Bots
Bots are built for engineering teams, so the closest starting points are the product ones. The AI Inbound Support Agent triages and follows up on customer calls. The 2FA Inbox template receives verification codes on the Bot's number. Ask the Bot to apply either to its AgentLine agent.
Bottom Line
A Devin Bot owns the outcome. When the outcome runs through a phone call or an SMS code, AgentLine gives it the line. Store a key, approve a number, and the Bot can finish the parts of the job that used to land back on an engineer's phone. If your team also runs single Devin sessions, see the Devin guide; other agents are in the runtime guides.