Your phone as an API for SMS, calls, recordings and transcripts
Free API for Tempo electricity pricing colors from RTE data
Stage
Not given
Established
Founded
Not given
2014
Based in
NO
FR
Pricing model
Paid
Open source
Pricing
Monthly subscription per connected line (exact price not specified in documentation). Recording and transcription are optional, charged from prepaid credits at rates shown in workspace. Credits are in US dollars and never expire while workspace is active.
Not given
Key features
Send SMS messages up to 1,600 characters
Receive incoming SMS and calls as webhook events
Outgoing calls with WebRTC audio for browser or AI
Idempotent messaging with operation status tracking
Model Context Protocol server for Claude and Cursor
Included bridge minutes per month
Conversation scoping per line and number
API rate limiting and fair-use enforcement
Dual-SIM support with separate credentials per line
Free API endpoint for today's and tomorrow's Tempo color in JSON
Historical Tempo data since 2014 in CSV format
No API key or authentication required
Open CORS headers for cross-domain access
Official Python and JavaScript libraries
Ready-to-use code examples for Home Assistant, Jeedom, Domoticz, Arduino, ESP32
Home Assistant integration available in HACS
EJP and PP (capacity mechanism) data endpoints
Data updated six times daily from official RTE sources
API versioning guarantee (v1 field names and meanings unchanging)
What makes it different
Use your own Android phone and SIM instead of a phone number service
Pay only per connected line; recording and transcription are optional and prepaid
Calls merged on bridge preserve your business number to recipients
Live AI voice support via WebRTC audio tracks
Every resource reports whether it is real or simulated
Completely free with no authentication, accounts, or API keys required
Official RTE data sourced automatically multiple times daily
Complete historical record from 2014 included in CSV format
MIT-licensed open source code for all integrations and libraries
Stable API with version 1 promises never to change field names or meanings