provider coverage is not one checkbox. voice topology, sms intake, outbound adapters, and real-world verification are separate properties, and current provider prices are not quoted here.
bring your
own carrier.
voice registration and sms model, with one of main's three wired outbound http adapters. live carrier verification is still required.
voice and sms provider model with a wired outbound adapter. account credentials and a real delivery test remain operator responsibilities.
voice and sms provider model with a wired outbound adapter using the provider's space, project, and token configuration.
stock and area lookup plus prepared order requests. cli purchasing is deliberately parked rather than presented as working provisioning.
trunk-routing coverage rather than a per-number softphone login. the voice topology differs from registration-based providers.
modeled telephone-provider coverage. check the specific voice and sms route before assuming the same setup as another carrier.
a distinct provider path using xmpp rather than the same webhook or carrier-email intake shape as the other models.
listed for voice coverage. no baseline outbound sms adapter is claimed for this provider.
listed for voice coverage. no baseline outbound sms adapter is claimed for this provider.
listed for voice coverage. no baseline outbound sms adapter is claimed for this provider.
- 01json or form webhook
the provider posts to the catcher's provider-specific route, where the payload is normalized and stored.
- 02query-string delivery
providers that forward message details in a url can use the same intake boundary without pretending the payload is identical.
- 03carrier email
message or voicemail email can be imported with its attachments, providing an alternative where the carrier supports it.
- 04xmpp route
jmp.chat follows its own communications path rather than being forced into a webhook-only description.
the clearest host path for persistent services and pulseaudio or pipewire audio experiments.
documented host paths and blackhole installation for audio routing experiments.
available as the least-proven host route; windows audio experiments involve proprietary vb-cable.
four adb control verbs and ring experiments. this is not a shipped android phone app or a proven real-call flow.
screen-access mirroring only. no equivalent ios automation or calling capability is claimed.
the mcp branch exposes local stdio tools and a javascript sdk. it is not a hosted internet api.
zoom, google meet, teams, whatsapp, slack, discord, and streaming lanes belong to designed meeting or omni branches, not to main's working telephone inbox. mobile calling is also experimental rather than delivered.