About Phonekit
Company phone infrastructure for people and software
We’re building Phonekit so a company can manage its phone numbers as shared infrastructure. People, tests, and approved agents should be able to use them through clear access controls.
The number needs a company home
Phone verification appears in places where companies work: product testing, distribution accounts, advertising tools, and account invitations. A text arriving on one person’s phone can interrupt the whole workflow. Automated tests and agents encounter the same step with no inbox they can read.
Phonekit brings the number and its received messages into an organization workspace. People can use the shared inbox. Software can retrieve messages through authorized API or CLI access. The company keeps control of the number and decides who may read it.
Built around workflows we use ourselves
We use Phonekit in QA, development, and testing, and to manage SMS access associated with company accounts. Those uses shape the details: recognizable number labels, explicit sharing, extracting a code, and waiting for a fresh message in a running test.
We’re also working with early-access users to understand their account and delivery requirements. The aim is a useful business that teams continue to rely on, with a product that serves both shared human access and software workflows.
Software is another user of company infrastructure
Agents and assistants increasingly perform tasks across services. When an authorized task reaches a phone verification step, the agent needs a practical way to retrieve its message. The company needs to know which numbers that agent can access.
The CLI and agent skill support terminal environments. The JS/TS SDK supports test runners and custom tools, and MCP supports message reads and explicitly authorized number management. The platform guides explain current setup and hosted requirements. Programmatic access belongs across plans because it is a normal way to use a company number.
Clear control, useful tools, and public documentation
We organize access around the company and its selected numbers. Message bodies are encrypted at rest, and people and credentials receive explicit permissions. We publish implementation guides so teams can understand how to connect their workflows.
We want the site to answer practical questions before you contact us: what the product does, how a real SMS test works, how to share company messages, and how an agent retrieves a fresh code. If your workflow adds a new requirement, tell us about it.