DogeSMS sits at a particular intersection: we are an OTP and verification primitive, and the fastest-growing consumers of OTP primitives in 2026 are AI agents. Autonomous agents need throwaway numbers to sign up for SaaS on behalf of users, headless browsers need SMS verification to complete account creation in sandboxed runs, and developer-tooling agents (Claude Code, Codex, Cursor, Devin, and their successors) increasingly want to script entire account-onboarding flows as part of larger workflows. Today they all reinvent the integration. They should not have to.

This role exists to make DogeSMS the default verification primitive across the agent ecosystem. Concretely that means owning the surface area where agents meet our API: a first-class MCP (Model Context Protocol) server that any Anthropic-compatible client can mount and immediately have tool-calls for request a number, wait for SMS, return the OTP; a Claude Code plugin and a Codex plugin publi...