# Phonekit > Real phone numbers for your coding agents, tests and team. Mobile numbers are real SIM lines on a mobile network; Standard numbers are US local VoIP. Agents and tests read whole messages (sign-in codes, links and any other text) through the SDK, CLI, MCP server or HTTP API, and can text within closed-loop limits. Every page below has a Markdown version at the listed .md URL. The same Markdown is returned for any page URL requested with `Accept: text/markdown`. Overview: https://www.phonekit.io/index.md ## Product - [Agents](https://www.phonekit.io/agents.md): Give Claude Code, Codex, Cursor and OpenCode a real US phone number, including real SIM lines, so they can sign in to your own app, read the code and text your product without asking you. - [Testing](https://www.phonekit.io/testing.md): Test everything your app texts end to end, from sign-in codes and invite links to confirmations and two-way replies, with real US phone numbers, including real SIM lines, in Playwright, Cypress and CI. - [Teams](https://www.phonekit.io/teams.md): Move your company's verification codes and texts off personal phones. Shared US numbers, including real SIM lines, delivered to a shared inbox, email or Slack, with per-number access and a record of who opened what. - [Pricing](https://www.phonekit.io/pricing.md): Phonekit plans start at $29 a month per workspace, with Standard numbers and real SIM Mobile lines, the SDK, CLI, MCP server and API, and a shared inbox on every plan. ## Testing guides - [Playwright](https://www.phonekit.io/docs/guides/playwright.md): A complete Playwright SMS test: receive a fresh code with the Phonekit SDK, submit it in the browser, and assert the signed-in account. - [Continuous integration](https://www.phonekit.io/docs/guides/ci.md): A complete GitHub Actions workflow for SDK-based SMS verification tests, with scoped secrets, number serialization, and trusted deployment configuration. - [Cypress](https://www.phonekit.io/docs/guides/cypress.md): A Cypress SMS recipe with server-side Phonekit tasks, an explicit fresh-message cursor, hidden code entry, and a final application assertion. - [Supabase Auth](https://www.phonekit.io/docs/guides/supabase.md): Test Supabase SMS sign-in end to end with a selected Phonekit number, real receipt, verifyOtp, a session assertion, and explicit test-mode boundaries. - [Firebase Auth](https://www.phonekit.io/docs/guides/firebase.md): A Firebase phone-auth acceptance recipe that preserves real app verification, receives an SMS through Phonekit, and distinguishes fictional-number coverage. - [Twilio Verify](https://www.phonekit.io/docs/guides/twilio-verify.md): Run a complete Twilio Verify send, Phonekit SMS receipt and Verification Check test, with service isolation and unfinished-attempt cleanup. - [iOS simulator / XCUITest](https://www.phonekit.io/docs/guides/ios-simulator.md): A native Swift XCUITest recipe that receives real SMS through a test-runner HTTP fixture and enters the fresh code into the iOS simulator. ## Integrations - [Claude Code](https://www.phonekit.io/integrations/claude.md): Install the Phonekit skill and Claude Code can read the texted code in your own app's sign-in and finish the step itself. - [Codex](https://www.phonekit.io/integrations/codex.md): Install the Phonekit skill and Codex can receive texts on a number you choose, read the code or reply, and test your app's SMS flows end to end. - [Cursor](https://www.phonekit.io/integrations/cursor.md): Install the Phonekit skill and Cursor Agent can read the texted code in your own app, so it can reproduce and fix sign-in problems end to end. - [OpenCode](https://www.phonekit.io/integrations/opencode.md): Install the Phonekit skill and OpenCode can read the texted code in your own app, so it can write and run real phone sign-in tests. ## Documentation - [Quickstart](https://www.phonekit.io/docs/quickstart.md): Connect the Phonekit CLI, choose an authorized company number, and wait for a fresh SMS verification code. - [CLI reference](https://www.phonekit.io/docs/cli.md): Commands, JSON output, selected-number access, closed-loop sending, project aliases, timeouts, and exit codes for the Phonekit CLI. - [JS/TS SDK](https://www.phonekit.io/docs/sdk.md): Install Phonekit's server-side SDK, capture message cursors, wait for OTPs, and handle deadlines and cancellation in JavaScript or TypeScript. - [API reference](https://www.phonekit.io/docs/api.md): Discover allowances, manage authorized lines, immediately read fresh SMS, send texts inside your own closed loop, and subscribe to selected-line webhooks through one API. - [Webhooks](https://www.phonekit.io/docs/webhooks.md): A complete Next.js Phonekit webhook receiver: verify raw-body signatures, validate message metadata, atomically deduplicate and enqueue, then read content with a scoped SDK key. - [MCP](https://www.phonekit.io/docs/mcp.md): Phonekit MCP connection authentication, explicit permissions, prompt cursor reads and shared lifecycle/subscription tools. ## Learn - [Offboarding](https://www.phonekit.io/learn/offboarding.md): Keep the company number, change who can read it, review the keys and connections the person made, and prove the next owner can sign in. - [One number per test](https://www.phonekit.io/learn/one-number-per-test.md): Make SMS tests repeatable: mark the inbox before you send, give each parallel worker its own number, budget the whole test and report the stage that failed. - [Real SMS vs. mocks](https://www.phonekit.io/learn/real-vs-mocked-sms-tests.md): When to mock the code, when to use your auth provider's test numbers and when to send a real text, with a coverage matrix and a rollout plan. - [VoIP vs real SIM](https://www.phonekit.io/learn/voip-vs-real-sim.md): A plain comparison of VoIP numbers and real SIM lines for SMS verification, with when to choose each, when to keep or release a number, and a checklist. ## Comparisons - [Phonekit vs build it yourself](https://www.phonekit.io/compare/build-it-yourself.md): The code and costs of testing SMS codes on a number rented from an SMS API, side by side with Phonekit, and when building it yourself is the better choice. - [Phonekit vs Mailosaur](https://www.phonekit.io/compare/mailosaur.md): A plain comparison of Phonekit and Mailosaur for testing SMS codes: number types, how tests and agents read codes, team access, and when each is the better fit. - [Sharing SMS codes](https://www.phonekit.io/compare/sharing-codes.md): A company account texts its sign-in code to one number and several teammates need it. Personal phone, Google Voice, a password manager, a forwarding service and Phonekit compared. ## Company - [About Phonekit](https://www.phonekit.io/about.md): Phonekit gives coding agents, tests and teams real phone numbers. Why we built it, what we believe, and who it's for. - [Privacy](https://www.phonekit.io/privacy.md): What Phonekit stores, how message retention works, what analytics and session replay record, and how your company can manage and delete its data. - [Security](https://www.phonekit.io/security.md): How Phonekit protects your numbers and the texts they receive: passkey sign-in, per-organization and per-number access, scoped API keys, a full history and encrypted messages. - [Support](https://www.phonekit.io/support.md): Find the setup guide for your stack, report a delivery problem with the details we need, and keep secrets out of your request.