{ "data": { "a": { "slug": "46elks", "name": "46elks Voice API", "vendor": "46elks AB", "vendorUrl": "https://46elks.com", "kind": "http-api", "category": "voice-calling", "summary": "46elks is a Swedish telecom operator's REST API for phone calls, SMS and virtual numbers in 48 countries, with JSON call actions, call recording, SIP and WebRTC clients, and a WebSocket Realtime Voice API for connecting AI agents to calls.", "url": "https://www.anchorterminal.com/tools/46elks", "markdownUrl": "https://www.anchorterminal.com/tools/46elks.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/46elks.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/46elks.json", "dns": "46elks.grade.anchorterminal.com", "repo": "https://github.com/46elks/46elks-getting-started", "license": "Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository", "transports": [ "http", "websocket" ], "remoteUrl": "https://api.46elks.com/a1", "packages": [], "auth": "api-key", "authNotes": "HTTP Basic auth with an API username and password from the dashboard after a browser signup. Subaccounts have their own credentials. No scopes or read-only credentials found. Webhook origin can be verified per the Verify Callback Origin guide.", "pricing": "usage", "pricingNotes": "Per started minute, published by destination. UK calls cost €0.02 to landlines and €0.456 to mobiles, forwarding to a WebSocket €0.015 and to a SIP trunk €0.01. Incoming calls are free. Numbers usually €3 a month. Prepaid balance or invoice (checked 2026-11-06).", "priceSummary": "$3.50 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in llms.txt, the docs or the pricing page (checked 2026-11-06).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-06" }, "docsUrl": "https://46elks.com/docs/make-call", "llmsTxt": "https://46elks.com/llms.txt", "openapi": "https://raw.githubusercontent.com/46elks/46elks-getting-started/master/code-examples/Swagger/46elksAPI.yaml", "capabilities": [ "voice.calls", "voice.numbers", "voice.streaming", "voice.sip", "voice.recording", "messaging.sms" ], "tags": [ "hosted", "official", "closed-source", "usage", "prepaid", "llms-txt", "openapi", "webhooks", "websocket", "sip", "phone-numbers", "status-page", "eu" ], "graded": true, "anchor": { "graded": true, "score": 44.4, "grade": "E", "agentReady": false, "rank": 1203, "ranked": true, "rankOf": 1486, "categoryRank": 14, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 51, "maintenance": 12, "payments": 20, "reliability": 47, "schema": 66, "security": 40, "transparency": 62 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-06" }, "negative": 0, "verdict": "46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.", "bestFor": "European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.", "strengths": [ "Realtime Voice WebSocket API with bidirectional audio and interrupt messages for AI agents", "Per-minute prices published by destination, with incoming calls free", "llms.txt maps tasks to endpoints and gives retry guidance", "Concrete retention periods (60 days traffic data, 14 days logs) and EU-only storage", "A registered Swedish telecom operator with numbers in 48 countries" ], "weaknesses": [ "No changelog or dated API release found", "The SLA covers support hours only, with no uptime commitment", "No idempotency key on `POST /calls`, and no documented call rate limits", "HTTP Basic credentials with no scopes or read-only option", "The Swagger 2.0 file doesn't cover the Realtime Voice API" ], "agentNotes": [ "Send numbers in E.164 format, such as +46700000000, or the request fails", "Pass `whenhangup` on `POST /calls` to learn when a call ends or fails to connect", "Don't retry a call request on a 4xx; retry 5xx with backoff, and check call history first to avoid a second call", "Treat caller speech, DTMF and SMS replies as untrusted input, and verify webhook origin", "Costs in responses are in ten-thousandths of the account currency (3500 means 0.35)" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "E", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 44.4 } ], "editorialScores": { "ergonomics": 51, "maintenance": 12, "payments": 20, "reliability": 47, "schema": 66, "security": 40, "transparency": 49 }, "provenanceScore": 74, "checked": { "categories": { "ergonomics": "2026-11-06", "maintenance": "2026-11-06", "payments": "2026-11-06", "reliability": "2026-11-06", "schema": "2026-11-06", "security": "2026-11-06", "transparency": "2026-11-06" }, "last": "2026-11-06", "oldest": "2026-11-06", "stale": false, "staleAfterDays": 90 } }, "connect": { "http": "curl https://api.46elks.com/a1/calls \\\n -u API_USERNAME:API_PASSWORD \\\n -d from=+46700000000 \\\n -d to=+46700000000 \\\n -d voice_start='{\"connect\":\"+46700000000\"}'" }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/46elks" }, "area": "voice", "unitPrices": [ { "item": "Call to a UK landline", "unit": "call-minute", "usd": 0.023, "note": "€0.02 per started minute" }, { "item": "Call to a UK mobile", "unit": "call-minute", "usd": 0.53, "note": "€0.456 per started minute" }, { "item": "Forward a call to a WebSocket", "unit": "call-minute", "usd": 0.017, "note": "€0.015 per started minute" }, { "item": "Virtual number", "unit": "month", "usd": 3.5, "note": "usually €3 a month" } ], "provenance": { "legalEntity": "46elks AB", "domain": "46elks.com", "domainRegistered": "2011-04-27", "endpointOnVendorDomain": true, "terms": "https://46elks.com/terms", "privacy": "https://46elks.com/privacy-policy", "statusPage": "https://stats.uptimerobot.com/320XQh70w", "changelog": "", "securityTxt": "none", "checked": "2026-11-06", "notes": [ "The Terms of Service, effective 12 March 2024, are with 46elks AB (Sweden, 556838-8184) under Swedish law. No clause on automated access to the website was found.", "46elks.com/status redirects to an UptimeRobot page that draws its data by script from /api/, which its robots.txt disallows, so no history was read.", "/.well-known/security.txt returns 404. No changelog was found; the newest blog post in the sitemap is from 2014.", "Euro prices converted at about 1.16 dollars to the euro for unitPrices; the pricing page lists euro and kronor.", "RDAP gives 46elks.com a registration date of 27 April 2011." ], "score": 74 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/46elks.json", "live": { "slug": "46elks", "probe": { "target": "https://api.46elks.com/a1", "method": "get", "lastAt": "2026-11-07T18:20:08.122651517Z", "lastOk": true, "lastStatus": 401, "lastMs": 426, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 318, "p95ms24h": 457, "samples24h": 200, "samples30d": 200, "days": [ { "date": "2026-11-06", "probes": 13, "ok": 13 }, { "date": "2026-11-07", "probes": 187, "ok": 187 } ] }, "vendorStatus": { "page": "https://stats.uptimerobot.com/320XQh70w", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-07T04:47:03.46439958Z" }, "githubStars": 57, "securityTxt": { "url": "https://46elks.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:02:02.719722143Z" }, "llmsTxt": { "url": "https://46elks.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:31:04.362648825Z" }, "pages": [ { "url": "https://46elks.com/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T13:58:27.545226578Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "bff2a55e1a02" }, { "url": "https://46elks.com/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T13:58:29.648545838Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "be068526a0d6" } ], "updatedAt": "2026-11-07T18:20:08.122651517Z" } }, "answer": "LiveKit Telephony scores 67.6 (B) on agent readiness against 46elks Voice API's 44.4 (E), and leads in every scored category.", "b": { "slug": "livekit-telephony", "name": "LiveKit Telephony", "vendor": "LiveKit Incorporated", "vendorUrl": "https://livekit.com", "kind": "http-api", "category": "voice-calling", "summary": "LiveKit Telephony connects phone calls to LiveKit rooms as SIP participants. On LiveKit Cloud it covers SIP trunks to outside carriers, US inbound phone numbers, dispatch rules and transfers, managed through a Twirp API, server SDKs and the `lk` CLI.", "url": "https://www.anchorterminal.com/tools/livekit-telephony", "markdownUrl": "https://www.anchorterminal.com/tools/livekit-telephony.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/livekit-telephony.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json", "dns": "livekit-telephony.grade.anchorterminal.com", "repo": "https://github.com/livekit/sip", "license": "Proprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0", "transports": [ "http" ], "packages": [ { "registry": "npm", "name": "livekit-server-sdk" }, { "registry": "pypi", "name": "livekit-api" }, { "registry": "go", "name": "github.com/livekit/server-sdk-go/v2" } ], "auth": "api-key", "authNotes": "A project API key and secret, created in the LiveKit Cloud dashboard, sign a JWT sent as `Authorization: Bearer \u003ctoken\u003e`. The token's `sip` grant carries `admin` (trunks, dispatch rules, phone numbers) or `call` (`CreateSIPParticipant` and `TransferSIPParticipant`), and its lifetime is set by whoever signs it. Keys can be rotated in the dashboard and the secret is shown once. Access is self-serve after a browser sign-up. The CLI links a project with `lk cloud auth`, which opens a browser.", "pricing": "freemium", "pricingNotes": "Free Build plan with no card. It includes 1 US local number, 50 US local inbound minutes and 1,000 third-party SIP minutes a month as a hard cap. Ship starts at $50 a month and Scale at $500, with third-party SIP minutes at $0.004 and $0.003 past the allowance, US local inbound at $0.01 a minute, toll-free inbound at $0.02, local numbers $1 a month and toll-free $2. A third-party carrier bills its own trunk and number charges. A number released mid-month is billed for the full month. Enterprise is priced by sales (https://livekit.com/pricing.md, checked 2026-10-08).", "priceSummary": "$1 / mo", "where": "local", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the telephony docs, the SIP and Phone Numbers API references or the pricing page (checked 2026-10-08).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 480, "npmWeekly": 2938925, "pypiWeekly": 1673299, "asOf": "2026-10-08" }, "docsUrl": "https://docs.livekit.io/telephony/", "llmsTxt": "https://docs.livekit.io/telephony/llms.txt", "capabilities": [ "voice.calls", "voice.sip", "voice.numbers", "voice.transfer", "voice.streaming" ], "tags": [ "hosted", "sip", "open-source", "llms-txt", "cli", "typescript", "python", "go", "webhooks", "free-tier", "status-page", "soc2" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 67.6, "grade": "B", "agentReady": false, "rank": 312, "ranked": true, "rankOf": 1486, "categoryRank": 4, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 66, "maintenance": 90, "payments": 40, "reliability": 65, "schema": 84, "security": 61, "transparency": 76 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-01" }, "negative": 0, "verdict": "Signed tokens separate the right to dial (`sip.call`) from the right to manage trunks (`sip.admin`), and per-minute prices are public with a free plan that needs no card. LiveKit's own phone numbers are US only and inbound only, so outbound calls need a third-party SIP trunk, and the docs give no 429 or retry guidance.", "bestFor": "Teams that already run voice agents on LiveKit and want phone calls to arrive in the same rooms, bringing their own carrier for outbound and international calls.", "strengths": [ "Token grants separate `sip.call` (dial and transfer) from `sip.admin` (trunks, dispatch rules, numbers), with a lifetime the issuer sets", "Free Build plan with no card has one US local number, 50 inbound minutes and 1,000 third-party SIP minutes a month", "Per-minute and per-number prices are public, also as Markdown at livekit.com/pricing.md", "The SIP service is open source under Apache 2.0, with 14 tagged releases from 5 August to 28 October 2026", "Status page lists Global SIP, US Phone Numbers and SIP in 15 regions as separate components" ], "weaknesses": [ "LiveKit Phone Numbers are US only and inbound only, and `TransferSIPParticipant` does not work on them yet", "Outbound calls need a trunk from another carrier, billed by that carrier on top of LiveKit's SIP minutes", "No 429 or Retry-After guidance in the docs, and no documented idempotency key, so a retried `CreateSIPParticipant` may dial twice, whether the caller or the SDKs' region failover retries it", "The 99.99% uptime on the pricing page is an objective only, with no credits outside a written Enterprise agreement", "Sign-up and `lk cloud auth` need a person in a browser, and no machine payment protocol was found", "The terms bar benchmarking for competitive purposes without written consent" ], "agentNotes": [ "Ask the operator for a short-lived token with only the `sip.call` grant to dial or transfer. Trunk, dispatch rule and number changes need `sip.admin`", "Use a third-party outbound trunk for outbound calls. LiveKit Phone Numbers only receive calls", "Set `wait_until_answered` on `CreateSIPParticipant` and read the SIP status on `SipCallError` before retrying. Voicemail answers with 200 OK", "Current server SDKs retry a failed call in another region with the same request id, which the server isn't documented to deduplicate. Check the room for an existing SIP participant before dialling again", "Send every request as a JSON POST to `/twirp/livekit.SIP/\u003cMethod\u003e` or `/twirp/livekit.PhoneNumberService/\u003cMethod\u003e` on the project's own host, with `{}` for an empty body", "A released number is billed for the whole month, and the free Build allowance is a hard cap after which requests fail" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.8, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 67.6 } ], "editorialScores": { "ergonomics": 66, "maintenance": 90, "payments": 40, "reliability": 65, "schema": 84, "security": 61, "transparency": 69 }, "provenanceScore": 83, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-27", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "brew install livekit-cli", "http": "curl -X POST https://\u003cyour LiveKit URL domain\u003e/twirp/livekit.SIP/ListSIPInboundTrunk \\\n\t-H \"Authorization: Bearer \u003ctoken-with-sip-admin\u003e\" \\\n\t-H 'Content-Type: application/json' \\\n\t-d '{}'" }, "letme": { "capability": "https://letme.dev/voice.calls", "tool": "https://letme.dev/livekit-telephony" }, "sameCompany": [ "livekit-agents" ], "area": "voice", "unitPrices": [ { "item": "Third-party SIP minutes, Ship plan", "unit": "call-minute", "usd": 0.004, "note": "past 5,000 included minutes, carrier charges extra" }, { "item": "Third-party SIP minutes, Scale plan", "unit": "call-minute", "usd": 0.003, "note": "past 50,000 included minutes, carrier charges extra" }, { "item": "US local inbound minutes", "unit": "call-minute", "usd": 0.01, "note": "LiveKit Phone Numbers, past 100 (Ship) or 1,000 (Scale) included minutes" }, { "item": "US toll-free inbound minutes", "unit": "call-minute", "usd": 0.02, "note": "Ship and Scale only" }, { "item": "US local number", "unit": "month", "usd": 1, "note": "first number free on every plan" }, { "item": "US toll-free number", "unit": "month", "usd": 2, "note": "Ship and Scale only" }, { "item": "Ship plan", "unit": "month", "usd": 50, "note": "starting price" }, { "item": "Scale plan", "unit": "month", "usd": 500, "note": "starting price" } ], "provenance": { "legalEntity": "LiveKit Incorporated", "domain": "livekit.com", "domainRegistered": "2000-02-24", "endpointOnVendorDomain": false, "terms": "https://livekit.com/legal/terms-of-service", "privacy": "https://livekit.com/legal/privacy-policy", "statusPage": "https://status.livekit.io", "changelog": "https://github.com/livekit/sip/releases", "securityTxt": "valid", "checked": "2026-11-01", "notes": [ "livekit.io answers 308 to livekit.com. Docs stay at docs.livekit.io, the dashboard at cloud.livekit.io and the status page at status.livekit.io.", "The terms link is the Terms of Service Agreement for the Build, Ship and Scale plans of LiveKit Cloud, last updated 6 October 2026, between the customer and LiveKit Incorporated of San Francisco. Enterprise customers sign a separate agreement we did not see.", "The privacy policy was last updated 15 October 2026. A Data Processing Addendum of 6 October 2026 is at https://livekit.com/legal/data-processing-addendum and the sub-processor list (10 September 2026) at https://livekit.com/legal/sub-processors.", "Each project's API answers on its own host under livekit.cloud and SIP at \u003csubdomain\u003e.sip.livekit.cloud, a second domain. LiveKit's disclosure policy lists *.livekit.cloud among its own systems.", "livekit.com/.well-known/security.txt gives security@livekit.io, a PGP key and the policy at https://livekit.com/security/policy. It has no Expires field. livekit.com/security.txt returns 404.", "No changelog page for LiveKit Cloud was found (livekit.com/changelog returns 404). Dated changes are in the livekit/sip release tags and `CHANGELOG.md` in livekit/protocol.", "RDAP for livekit.com gives a registration date of 2000-02-24, long before the company existed. RDAP for livekit.io returned no events.", "livekit/sip tagged v1.22.0 on 28 October 2026 and livekit-cli tagged v2.19.2 on 22 October 2026." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/livekit-telephony.json", "live": { "slug": "livekit-telephony", "vendorStatus": { "page": "https://status.livekit.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-07T18:21:20.587887013Z" }, "versions": [ { "registry": "npm", "name": "livekit-server-sdk", "version": "2.19.2", "seenAt": "2026-11-06T23:40:39.360302688Z" }, { "registry": "pypi", "name": "livekit-api", "version": "1.2.2", "released": "2026-10-16", "seenAt": "2026-11-06T23:40:39.585117532Z" } ], "githubStars": 494, "npmWeekly": 4316286, "pypiWeekly": 2117247, "securityTxt": { "url": "https://livekit.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:32.805462262Z" }, "llmsTxt": { "url": "https://docs.livekit.io/telephony/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:55.140973576Z" }, "domain": { "domain": "livekit.com", "registered": "2000-02-24", "source": "https://rdap.verisign.com/com/v1/domain/livekit.com", "checkedAt": "2026-11-01T14:09:57.960731673Z" }, "pages": [ { "url": "https://livekit.com/pricing.md", "kind": "pricing", "status": 200, "checkedAt": "2026-10-16T22:26:33.706805281Z", "changedAt": "2026-10-15T21:29:52.209472015Z", "fingerprint": "ca579471fe87" }, { "url": "https://livekit.com/legal/privacy-policy", "kind": "privacy", "status": 200, "checkedAt": "2026-10-16T22:26:29.434015107Z", "changedAt": "2026-10-15T21:29:47.808652564Z", "fingerprint": "34b2795621d7" }, { "url": "https://livekit.com/legal/terms-of-service", "kind": "terms", "status": 200, "checkedAt": "2026-10-16T22:26:31.681612317Z", "changedAt": "2026-10-15T21:29:50.061909577Z", "fingerprint": "faebb2e03600" } ], "github": { "repo": "livekit/sip", "checkedAt": "2026-11-02T09:01:15.064812806Z", "stars": 490, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T02:39:31Z", "openIssues": 34, "openPRs": 43, "issuesOpened90d": 19, "issuesClosed90d": 16, "prsMerged90d": 111, "ci": { "branch": "main", "runs": 50, "success": 50, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-11-01T19:38:31Z" }, "replies": { "sampled": 25, "unanswered": 14, "medianDays": 6.9 } }, "updatedAt": "2026-11-07T18:21:20.587887013Z" } }, "edges": [ { "by": 78, "category": "maintenance", "leads": "livekit-telephony", "name": "Maintenance \u0026 community", "reasons": { "a": "No changelog, release notes or dated API change was found, the sitemap's newest blog post is from 2014, and the Swagger file predates Realtime Voice (0). No dated changes in the 90 days from 8 August (0). Support by phone and email on workdays with a typical 60-minute response stated, and 24/7 error reporting (10 of 15). No official SDK (0). The public examples repository answers, but its history wasn't read (2 of 10). 0+0+10+0+2 = 12.", "b": "livekit/sip v1.22.0 was tagged on 28 October 2026, livekit-server-sdk 2.19.2 on 22 October and livekit-cli v2.19.2 on 22 October (30). livekit/sip has 14 tags in the 90 days from 3 August, v1.9.0 (5 August) to v1.22.0, and livekit-cli 9 (20). Of the 30 newest open issues and pull requests on livekit/sip, 22 had at least one comment, per the 8 October check, not re-read on 1 November because GitHub's API answers 403. Paid plans add email support and there is a community Slack (17 of 25). Current server SDKs, livekit-server-sdk 2.19.2 (22 October), livekit-api 1.2.2 (16 October) and server-sdk-go v2.19.0 (8 October), by their repository tags (15). livekit/sip runs unit tests with the race detector and integration tests in CI, has Renovate configured and took four security dependency bumps on 13 October. We did not see the latest run's result (8 of 10). 30 + 20 + 17 + 15 + 8 = 90." }, "scores": { "a": 12, "b": 90 } }, { "by": 21, "category": "security", "leads": "livekit-telephony", "name": "Security \u0026 auth", "reasons": { "a": "HTTP Basic credentials per account, with separate credentials per subaccount and no scopes found (18 of 30). Subaccounts separate traffic, with no read-only credential or confirmation for paid actions (6 of 20). Callers' speech, DTMF and SMS replies reach the agent as untrusted input. The docs show how to verify callback origin, with no prompt-injection guidance (5 of 15). Call, SMS and recording history through the API for 90 days (8 of 15). A registered Swedish telecom operator, but no security.txt (404), disclosure policy, bug bounty or certification was found (3 of 20). 18+6+5+8+3 = 40.", "b": "A project key and secret sign JWTs whose `sip` grant is `admin` or `call`, with a lifetime the signer sets. Keys rotate in the dashboard. The key pair itself can mint any grant, so scoping depends on the operator handing an agent a token and not the secret (25 of 30). `call` without `admin` is a least-privilege mode for dialling, inbound trunks can be limited by number, IP range or credentials, and no read-only grant or confirmation step for dialling or renting numbers was found (8 of 20). Calls carry untrusted caller speech, and no prompt-injection guidance was found in the telephony docs (5 of 15). The security overview says project configuration changes are logged, with export to a SIEM still on the roadmap, and the dashboard shows call logs (8 of 15). security.txt with a disclosure policy and safe harbour, a Hall of Fame with no cash bounty stated, SOC 2 Type II, six-monthly penetration tests, ISO 27001 in progress, and no OSV advisories for livekit-server-sdk, livekit-api, server-sdk-go, livekit/sip, livekit-server or livekit/protocol on 1 November. security.txt has no Expires field. The same programme reading as LiveKit's agents framework (15 of 20). 25 + 8 + 5 + 8 + 15 = 61." }, "scores": { "a": 40, "b": 61 } }, { "by": 20, "category": "payments", "leads": "livekit-telephony", "name": "Payments \u0026 pricing", "reasons": { "a": "No x402, MPP or L402 (0). Per-minute prices by destination are public without login, also in kronor, with incoming calls free (20). No free credit; only SMS to the test number +46700000000 costs nothing, and accounts are prepaid or invoiced against a deposit (0). A person signs up in a browser and copies the credentials (0). 0+20+0+0 = 20.", "b": "No x402, MPP or L402 found (0). Per-minute and per-number prices are public without a login, also as Markdown (20). The Build plan is free with no card and includes a US local number, 50 inbound minutes and 1,000 third-party SIP minutes a month (20). An account is created in a browser and `lk cloud auth` opens one, and no programmatic sign-up or key API was found (0)." }, "scores": { "a": 20, "b": 40 } }, { "by": 18, "category": "reliability", "leads": "livekit-telephony", "name": "Reliability", "reasons": { "a": "Graded on the hosted REST and Realtime Voice APIs with the hosted lines. A status page exists, linked from 46elks.com/status on UptimeRobot (20). It draws its data by script from a path its robots.txt disallows, so no history was readable (5). SMS sending speed is documented in the FAQ, but no limit for calls, numbers or WebSocket sessions was found (5 of 15). llms.txt says to retry 5xx with exponential backoff and not to retry 4xx unchanged, with no Retry-After or idempotency for `POST /calls` (7 of 15). The SLA page commits to support hours and 24/7 error reporting with no uptime figure, and extended SLAs are by sales (0). Voice and Realtime Voice carry no beta label (10). 20+5+5+7+0+10 = 47.", "b": "Graded as a hosted service, LiveKit Cloud. Statuspage at status.livekit.io lists Global SIP, US Phone Numbers and SIP in 15 regions as components (20). In the 90 days to 1 November every SIP incident read as partial or short. Failed SIP transfers for a small percentage of calls in US East on 17 August (15:48 to 16:08 and 17:24 to 18:05 UTC), one-way audio on LiveKit Phone Numbers for calls from T-Mobile and AT\u0026T on 2 September, raised SIP API latency on 15 September (about a minute from 16:11 UTC and ten minutes from 21:11 UTC), about 14% of outbound and 5% of inbound calls failing in US West on 16 October (14:49 to 15:58 UTC), and failed inbound SIP calls and about 10% of `CreateSIPParticipant` requests failing in US East on 28 October (23:30 to 23:58 UTC). Each hit one region, one carrier path or a share of calls, so each is minor. The 15 September Cloud Dashboard and billing API outage left RTC and SIP unaffected, per its own text (20). The Server API limit is 1,000 requests a minute per project, with number limits of 100 on Ship and 300 on Scale (15). No 429, Retry-After or backoff guidance was found in the docs. The server SDKs retry failed requests in another region and send an `X-Livekit-Request-Id` key on each attempt, but that is in their code and changelogs, not documented as rate-limit handling (0). The pricing page lists 99.99% uptime for every plan, and section 2.5 of the terms calls such figures objectives with no credits outside a written Enterprise agreement, per the 8 October check, so no SLA is counted (0). The SIP API carries no beta label, though the warm transfer task in the Agents framework is marked beta, in Python only (10). 20 + 20 + 15 + 0 + 0 + 10 = 65." }, "scores": { "a": 47, "b": 65 } }, { "by": 18, "category": "schema", "leads": "livekit-telephony", "name": "Schema \u0026 documentation", "reasons": { "a": "A Swagger 2.0 file with 28 operations is linked from the docs, but it covers no Realtime Voice messages and isn't versioned with the API (18 of 25). An llms.txt written for agents, with a task-to-endpoint table and webhook payloads, while docs pages are HTML (10). Each docs page explains parameters and when webhooks fire, such as `voice_start` loading only once a call connects (14 of 20). Form-encoded parameters with types in the Swagger file and few enums (9 of 15). Examples in many languages and a JSON error shape, with no error list (10 of 15). The `/a1/` path, with no changelog found (5 of 15). 18+10+14+9+10+5 = 66.", "b": "The contract is protobuf in livekit/protocol (17 SIP RPCs, 6 phone number RPCs), called as JSON over Twirp. No OpenAPI document was found, and we counted the protobuf files as the similar spec (25). llms.txt per docs section, 42 telephony pages on 1 November, and every page as Markdown (10). Reference tables give each parameter's purpose, and the guides say when to use an inline trunk or a stored one (15 of 20). Typed fields with enums for transport, encryption and number status and required fields marked, with metadata as a free string (13 of 15). Examples in six languages and the CLI, a call outcome table and a troubleshooting guide by SIP code. No full list of Twirp errors was found, and the reference still shows `TransferSIPParticipant` returning an empty message on 1 November where the protocol changelog says it returns a response object (11 of 15). The Twirp path has no version. Changes are dated in livekit/sip release tags and the protocol `CHANGELOG.md`, with no cloud changelog page found (10 of 15)." }, "scores": { "a": 66, "b": 84 } }, { "by": 15, "category": "ergonomics", "leads": "livekit-telephony", "name": "Agent ergonomics", "reasons": { "a": "Compact JSON responses, and call actions returned as small JSON objects (18 of 25). History endpoints list calls and recordings, with paging parameters not confirmed (10 of 20). Errors carry `error` and `detail` (12 of 20). No idempotency key on `POST /calls` or number allocation (3 of 20). Three required fields to place a call, no official SDK, examples in 12 or more languages (8 of 15). 18+10+12+3+8 = 51.", "b": "List calls take a limit and ID, number or status filters, with no field selection (15 of 25). A `Pagination` type with `after_id` and `limit` on the SIP list calls (18 of 20). `wait_until_answered` returns a `SipCallError` with the carrier's SIP status code, and the docs map codes to outcomes. Twirp errors are named only in passing (15 of 20). The Go, Node.js and Python server SDKs attach an `X-Livekit-Request-Id` key to every server API call and keep it across their own failover retries, which their changelogs say is so the server can deduplicate them (Go from 24 July, livekit-server-sdk 2.19.0 on 9 September, livekit-api 1.2.1 on 27 August). That is the SDKs' stated purpose, not documented server behaviour. The API docs don't mention the key, the open-source LiveKit server read on 1 November never takes it from the request, and its `CreateSIPParticipant` path mints a fresh call ID each time, so a retried dial isn't shown to be safe (3 of 20). A call needs a trunk, a number and a room name, and SIP clients ship in Go, JavaScript, Python, Ruby, Kotlin and Rust plus the `lk` CLI (15). 15 + 18 + 15 + 3 + 15 = 66." }, "scores": { "a": 51, "b": 66 } } ], "facts": [ { "a": "HTTP API", "b": "HTTP API", "name": "Kind" }, { "a": "46elks AB", "b": "LiveKit Incorporated", "name": "Vendor" }, { "a": "https://api.46elks.com/a1", "b": "no (local only)", "name": "Hosted endpoint" }, { "a": "HTTP, websocket", "b": "HTTP", "name": "Transports" }, { "a": "API key", "b": "API key", "name": "Auth" }, { "a": "Pay per use", "b": "Freemium", "name": "Pricing" }, { "a": "$0.017 per minute of call", "b": "not published", "name": "Price for phone calls" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository", "b": "Proprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0", "name": "Licence" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "none", "b": "2026-10-28", "name": "Last release" }, { "a": "2024-03-12", "b": "no date given", "name": "Terms last updated" }, { "a": "2018-05-20", "b": "no date given", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "yes", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "480 stars, 2.9M npm/wk, 1.7M PyPI/wk", "name": "Popularity" }, { "a": "none", "b": "2.8/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "LiveKit Telephony scores 67.6 (B) on agent readiness against 46elks Voice API's 44.4 (E), and leads in every scored category.", "question": "Which is better for AI agents, 46elks Voice API or LiveKit Telephony?" }, { "answer": "Both need an API key.", "question": "Do 46elks Voice API and LiveKit Telephony need an API key?" }, { "answer": "46elks Voice API has a hosted endpoint at https://api.46elks.com/a1. No hosted endpoint is listed for LiveKit Telephony.", "question": "Can an agent call 46elks Voice API and LiveKit Telephony without installing anything?" }, { "answer": "No open-source release is listed for 46elks Voice API. LiveKit Telephony is open source (Proprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0).", "question": "Are 46elks Voice API and LiveKit Telephony open source?" } ], "goodFor": [ { "aheadOn": null, "also": [ "A hosted endpoint, with nothing to install" ], "goodFor": "European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.", "slug": "46elks", "watchFor": "No changelog or dated API release found" }, { "aheadOn": [ "Reliability, 65 against 47", "Schema \u0026 documentation, 84 against 66", "Agent ergonomics, 66 against 51", "Security \u0026 auth, 61 against 40", "Payments \u0026 pricing, 40 against 20", "Maintenance \u0026 community, 90 against 12", "Transparency \u0026 trust, 76 against 62" ], "also": [ "Open source" ], "goodFor": "Teams that already run voice agents on LiveKit and want phone calls to arrive in the same rooms, bringing their own carrier for outbound and international calls.", "slug": "livekit-telephony", "watchFor": "LiveKit Phone Numbers are US only and inbound only, and `TransferSIPParticipant` does not work on them yet" } ], "history": { "46elks": null, "livekit-telephony": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 67.5, "fromGrade": "B", "to": 67.6, "toGrade": "B" } ] }, "job": { "capability": "voice.calls", "name": "Phone calls" }, "others": [ { "json": "https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice.json", "title": "46elks Voice API vs Bandwidth Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-didlogic.json", "title": "46elks Voice API vs didlogic Voice API", "url": "https://www.anchorterminal.com/compare/46elks-vs-didlogic" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-exotel-voice.json", "title": "46elks Voice API vs Exotel Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-exotel-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.json", "title": "46elks Voice API vs Infobip Calls API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-infobip-calls" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-jambonz.json", "title": "46elks Voice API vs jambonz", "url": "https://www.anchorterminal.com/compare/46elks-vs-jambonz" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-plivo-voice.json", "title": "46elks Voice API vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/46elks-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice.json", "title": "46elks Voice API vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-sinch-voice.json", "title": "46elks Voice API vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.json", "title": "46elks Voice API vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-twilio-voice.json", "title": "46elks Voice API vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.json", "title": "46elks Voice API vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/46elks-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-voximplant.json", "title": "46elks Voice API vs Voximplant", "url": "https://www.anchorterminal.com/compare/46elks-vs-voximplant" }, { "json": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.json", "title": "Bandwidth Voice API + MCP vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.json", "title": "Exotel Voice API + MCP vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony.json", "title": "Infobip Calls API + MCP vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.json", "title": "jambonz vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice.json", "title": "LiveKit Telephony vs Plivo Voice API", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice.json", "title": "LiveKit Telephony vs SignalWire Voice API", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice.json", "title": "LiveKit Telephony vs Sinch Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice.json", "title": "LiveKit Telephony vs Telnyx Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice.json", "title": "LiveKit Telephony vs Twilio Programmable Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.json", "title": "LiveKit Telephony vs Vonage Voice API + MCP", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice" }, { "json": "https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.json", "title": "LiveKit Telephony vs Voximplant", "url": "https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant" }, { "json": "https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management.json", "title": "46elks Voice API vs DIDWW Voice and Number Management API", "url": "https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management" }, { "json": "https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony.json", "title": "didlogic Voice API vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony" }, { "json": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.json", "title": "DIDWW Voice and Number Management API vs LiveKit Telephony", "url": "https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony" } ], "panel": null, "scores": [ { "46elks": 47, "by": 18, "edge": "livekit-telephony", "key": "reliability", "livekit-telephony": 65, "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "46elks": 66, "by": 18, "edge": "livekit-telephony", "key": "schema", "livekit-telephony": 84, "name": "Schema \u0026 documentation", "weight": 13 }, { "46elks": 51, "by": 15, "edge": "livekit-telephony", "key": "ergonomics", "livekit-telephony": 66, "name": "Agent ergonomics", "weight": 13 }, { "46elks": 40, "by": 21, "edge": "livekit-telephony", "key": "security", "livekit-telephony": 61, "name": "Security \u0026 auth", "weight": 14 }, { "46elks": 20, "by": 20, "edge": "livekit-telephony", "key": "payments", "livekit-telephony": 40, "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "46elks": 12, "by": 78, "edge": "livekit-telephony", "key": "maintenance", "livekit-telephony": 90, "name": "Maintenance \u0026 community", "weight": 7 }, { "46elks": 62, "by": 14, "edge": "livekit-telephony", "key": "transparency", "livekit-telephony": 76, "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "LiveKit Telephony scores 67.6 (B) on agent readiness against 46elks Voice API's 44.4 (E), and leads in every scored category. Both do phone calls.", "tasks": null, "tutorials": [], "verdicts": { "46elks": "46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.", "livekit-telephony": "Signed tokens separate the right to dial (`sip.call`) from the right to manage trunks (`sip.admin`), and per-minute prices are public with a free plan that needs no card. LiveKit's own phone numbers are US only and inbound only, so outbound calls need a third-party SIP trunk, and the docs give no 429 or retry guidance." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony", "json": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.min.md" }, "markdown": "LiveKit Telephony scores 67.6 (B) on agent readiness against 46elks Voice API's 44.4 (E), and leads in every scored category. Both do phone calls.\n\n- 46elks Voice API: grade E, 44.4/100, rank #1203 of 1486. Markdown https://www.anchorterminal.com/tools/46elks.md · JSON https://www.anchorterminal.com/api/v1/tools/46elks.json\n- LiveKit Telephony: grade B, 67.6/100, rank #312 of 1486. Markdown https://www.anchorterminal.com/tools/livekit-telephony.md · JSON https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json\n- Best phone calling and voice transport APIs for AI agents: https://www.anchorterminal.com/best/voice-calling/index.md\n- All 105 calling comparisons: https://www.anchorterminal.com/compare/voice-calling/index.md\n\n## Which one, for what\n\n### 46elks Voice API (E)\n\nGood for: European teams that want EU-resident calling and numbers with a simple REST API and a WebSocket bridge to an AI agent.\n\nAlso in its favour:\n- A hosted endpoint, with nothing to install\n\nWatch for: No changelog or dated API release found\n\n### LiveKit Telephony (B)\n\nGood for: Teams that already run voice agents on LiveKit and want phone calls to arrive in the same rooms, bringing their own carrier for outbound and international calls.\n\nAhead on:\n- Reliability, 65 against 47\n- Schema \u0026 documentation, 84 against 66\n- Agent ergonomics, 66 against 51\n- Security \u0026 auth, 61 against 40\n- Payments \u0026 pricing, 40 against 20\n- Maintenance \u0026 community, 90 against 12\n- Transparency \u0026 trust, 76 against 62\n\nAlso in its favour:\n- Open source\n\nWatch for: LiveKit Phone Numbers are US only and inbound only, and `TransferSIPParticipant` does not work on them yet\n\n\n## Why the edge\n\n### Maintenance \u0026 community: LiveKit Telephony +78\n\n- 46elks Voice API (12): No changelog, release notes or dated API change was found, the sitemap's newest blog post is from 2014, and the Swagger file predates Realtime Voice (0). No dated changes in the 90 days from 8 August (0). Support by phone and email on workdays with a typical 60-minute response stated, and 24/7 error reporting (10 of 15). No official SDK (0). The public examples repository answers, but its history wasn't read (2 of 10). 0+0+10+0+2 = 12.\n- LiveKit Telephony (90): livekit/sip v1.22.0 was tagged on 28 October 2026, livekit-server-sdk 2.19.2 on 22 October and livekit-cli v2.19.2 on 22 October (30). livekit/sip has 14 tags in the 90 days from 3 August, v1.9.0 (5 August) to v1.22.0, and livekit-cli 9 (20). Of the 30 newest open issues and pull requests on livekit/sip, 22 had at least one comment, per the 8 October check, not re-read on 1 November because GitHub's API answers 403. Paid plans add email support and there is a community Slack (17 of 25). Current server SDKs, livekit-server-sdk 2.19.2 (22 October), livekit-api 1.2.2 (16 October) and server-sdk-go v2.19.0 (8 October), by their repository tags (15). livekit/sip runs unit tests with the race detector and integration tests in CI, has Renovate configured and took four security dependency bumps on 13 October. We did not see the latest run's result (8 of 10). 30 + 20 + 17 + 15 + 8 = 90.\n\n### Security \u0026 auth: LiveKit Telephony +21\n\n- 46elks Voice API (40): HTTP Basic credentials per account, with separate credentials per subaccount and no scopes found (18 of 30). Subaccounts separate traffic, with no read-only credential or confirmation for paid actions (6 of 20). Callers' speech, DTMF and SMS replies reach the agent as untrusted input. The docs show how to verify callback origin, with no prompt-injection guidance (5 of 15). Call, SMS and recording history through the API for 90 days (8 of 15). A registered Swedish telecom operator, but no security.txt (404), disclosure policy, bug bounty or certification was found (3 of 20). 18+6+5+8+3 = 40.\n- LiveKit Telephony (61): A project key and secret sign JWTs whose `sip` grant is `admin` or `call`, with a lifetime the signer sets. Keys rotate in the dashboard. The key pair itself can mint any grant, so scoping depends on the operator handing an agent a token and not the secret (25 of 30). `call` without `admin` is a least-privilege mode for dialling, inbound trunks can be limited by number, IP range or credentials, and no read-only grant or confirmation step for dialling or renting numbers was found (8 of 20). Calls carry untrusted caller speech, and no prompt-injection guidance was found in the telephony docs (5 of 15). The security overview says project configuration changes are logged, with export to a SIEM still on the roadmap, and the dashboard shows call logs (8 of 15). security.txt with a disclosure policy and safe harbour, a Hall of Fame with no cash bounty stated, SOC 2 Type II, six-monthly penetration tests, ISO 27001 in progress, and no OSV advisories for livekit-server-sdk, livekit-api, server-sdk-go, livekit/sip, livekit-server or livekit/protocol on 1 November. security.txt has no Expires field. The same programme reading as LiveKit's agents framework (15 of 20). 25 + 8 + 5 + 8 + 15 = 61.\n\n### Payments \u0026 pricing: LiveKit Telephony +20\n\n- 46elks Voice API (20): No x402, MPP or L402 (0). Per-minute prices by destination are public without login, also in kronor, with incoming calls free (20). No free credit; only SMS to the test number +46700000000 costs nothing, and accounts are prepaid or invoiced against a deposit (0). A person signs up in a browser and copies the credentials (0). 0+20+0+0 = 20.\n- LiveKit Telephony (40): No x402, MPP or L402 found (0). Per-minute and per-number prices are public without a login, also as Markdown (20). The Build plan is free with no card and includes a US local number, 50 inbound minutes and 1,000 third-party SIP minutes a month (20). An account is created in a browser and `lk cloud auth` opens one, and no programmatic sign-up or key API was found (0).\n\n### Reliability: LiveKit Telephony +18\n\n- 46elks Voice API (47): Graded on the hosted REST and Realtime Voice APIs with the hosted lines. A status page exists, linked from 46elks.com/status on UptimeRobot (20). It draws its data by script from a path its robots.txt disallows, so no history was readable (5). SMS sending speed is documented in the FAQ, but no limit for calls, numbers or WebSocket sessions was found (5 of 15). llms.txt says to retry 5xx with exponential backoff and not to retry 4xx unchanged, with no Retry-After or idempotency for `POST /calls` (7 of 15). The SLA page commits to support hours and 24/7 error reporting with no uptime figure, and extended SLAs are by sales (0). Voice and Realtime Voice carry no beta label (10). 20+5+5+7+0+10 = 47.\n- LiveKit Telephony (65): Graded as a hosted service, LiveKit Cloud. Statuspage at status.livekit.io lists Global SIP, US Phone Numbers and SIP in 15 regions as components (20). In the 90 days to 1 November every SIP incident read as partial or short. Failed SIP transfers for a small percentage of calls in US East on 17 August (15:48 to 16:08 and 17:24 to 18:05 UTC), one-way audio on LiveKit Phone Numbers for calls from T-Mobile and AT\u0026T on 2 September, raised SIP API latency on 15 September (about a minute from 16:11 UTC and ten minutes from 21:11 UTC), about 14% of outbound and 5% of inbound calls failing in US West on 16 October (14:49 to 15:58 UTC), and failed inbound SIP calls and about 10% of `CreateSIPParticipant` requests failing in US East on 28 October (23:30 to 23:58 UTC). Each hit one region, one carrier path or a share of calls, so each is minor. The 15 September Cloud Dashboard and billing API outage left RTC and SIP unaffected, per its own text (20). The Server API limit is 1,000 requests a minute per project, with number limits of 100 on Ship and 300 on Scale (15). No 429, Retry-After or backoff guidance was found in the docs. The server SDKs retry failed requests in another region and send an `X-Livekit-Request-Id` key on each attempt, but that is in their code and changelogs, not documented as rate-limit handling (0). The pricing page lists 99.99% uptime for every plan, and section 2.5 of the terms calls such figures objectives with no credits outside a written Enterprise agreement, per the 8 October check, so no SLA is counted (0). The SIP API carries no beta label, though the warm transfer task in the Agents framework is marked beta, in Python only (10). 20 + 20 + 15 + 0 + 0 + 10 = 65.\n\n### Schema \u0026 documentation: LiveKit Telephony +18\n\n- 46elks Voice API (66): A Swagger 2.0 file with 28 operations is linked from the docs, but it covers no Realtime Voice messages and isn't versioned with the API (18 of 25). An llms.txt written for agents, with a task-to-endpoint table and webhook payloads, while docs pages are HTML (10). Each docs page explains parameters and when webhooks fire, such as `voice_start` loading only once a call connects (14 of 20). Form-encoded parameters with types in the Swagger file and few enums (9 of 15). Examples in many languages and a JSON error shape, with no error list (10 of 15). The `/a1/` path, with no changelog found (5 of 15). 18+10+14+9+10+5 = 66.\n- LiveKit Telephony (84): The contract is protobuf in livekit/protocol (17 SIP RPCs, 6 phone number RPCs), called as JSON over Twirp. No OpenAPI document was found, and we counted the protobuf files as the similar spec (25). llms.txt per docs section, 42 telephony pages on 1 November, and every page as Markdown (10). Reference tables give each parameter's purpose, and the guides say when to use an inline trunk or a stored one (15 of 20). Typed fields with enums for transport, encryption and number status and required fields marked, with metadata as a free string (13 of 15). Examples in six languages and the CLI, a call outcome table and a troubleshooting guide by SIP code. No full list of Twirp errors was found, and the reference still shows `TransferSIPParticipant` returning an empty message on 1 November where the protocol changelog says it returns a response object (11 of 15). The Twirp path has no version. Changes are dated in livekit/sip release tags and the protocol `CHANGELOG.md`, with no cloud changelog page found (10 of 15).\n\n### Agent ergonomics: LiveKit Telephony +15\n\n- 46elks Voice API (51): Compact JSON responses, and call actions returned as small JSON objects (18 of 25). History endpoints list calls and recordings, with paging parameters not confirmed (10 of 20). Errors carry `error` and `detail` (12 of 20). No idempotency key on `POST /calls` or number allocation (3 of 20). Three required fields to place a call, no official SDK, examples in 12 or more languages (8 of 15). 18+10+12+3+8 = 51.\n- LiveKit Telephony (66): List calls take a limit and ID, number or status filters, with no field selection (15 of 25). A `Pagination` type with `after_id` and `limit` on the SIP list calls (18 of 20). `wait_until_answered` returns a `SipCallError` with the carrier's SIP status code, and the docs map codes to outcomes. Twirp errors are named only in passing (15 of 20). The Go, Node.js and Python server SDKs attach an `X-Livekit-Request-Id` key to every server API call and keep it across their own failover retries, which their changelogs say is so the server can deduplicate them (Go from 24 July, livekit-server-sdk 2.19.0 on 9 September, livekit-api 1.2.1 on 27 August). That is the SDKs' stated purpose, not documented server behaviour. The API docs don't mention the key, the open-source LiveKit server read on 1 November never takes it from the request, and its `CreateSIPParticipant` path mints a fresh call ID each time, so a retried dial isn't shown to be safe (3 of 20). A call needs a trunk, a number and a room name, and SIP clients ship in Go, JavaScript, Python, Ruby, Kotlin and Rust plus the `lk` CLI (15). 15 + 18 + 15 + 3 + 15 = 66.\n\n## Score by category\n\n| Category | Weight | 46elks Voice API | LiveKit Telephony | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 47 | 65 | LiveKit Telephony +18 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 66 | 84 | LiveKit Telephony +18 |\n| Agent ergonomics | 13% (16.2 this run) | 51 | 66 | LiveKit Telephony +15 |\n| Security \u0026 auth | 14% (17.5 this run) | 40 | 61 | LiveKit Telephony +21 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 40 | LiveKit Telephony +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 12 | 90 | LiveKit Telephony +78 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 62 | 76 | LiveKit Telephony +14 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **44.4 · E** | **67.6 · B** | |\n\n## Facts side by side\n\n| Fact | 46elks Voice API | LiveKit Telephony |\n| --- | --- | --- |\n| Kind | HTTP API | HTTP API |\n| Vendor | 46elks AB | LiveKit Incorporated |\n| Hosted endpoint | `https://api.46elks.com/a1` | no (local only) |\n| Transports | HTTP, websocket | HTTP |\n| Auth | API key | API key |\n| Pricing | Pay per use | Freemium |\n| Price for phone calls | $0.017 per minute of call | not published |\n| x402 | no | no |\n| Licence | Proprietary service under the 46elks Terms of Service (effective 12 March 2024). Example code and the Swagger file are in the public 46elks-getting-started repository | Proprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| Last release | none | 2026-10-28 |\n| Terms last updated | 2024-03-12 | no date given |\n| Privacy policy last updated | 2018-05-20 | no date given |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | yes | not found in the text |\n| Arbitration or class-action waiver | not found in the text | yes |\n| Popularity | none | 480 stars, 2.9M npm/wk, 1.7M PyPI/wk |\n| Agent reviews | none | 2.8/5 (4) |\n\n## How the scores have moved\n\n### 46elks Voice API\n\nNo score change since it was listed.\n\n### LiveKit Telephony\n\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**46elks Voice API.** 46elks publishes per-minute prices, an agent-oriented llms.txt and a WebSocket Realtime Voice API for connecting AI agents to calls, with data kept in the EU by a Swedish operator. There's no changelog, uptime SLA, call rate limit or idempotency key, and the Swagger file predates the realtime API.\n\n**LiveKit Telephony.** Signed tokens separate the right to dial (`sip.call`) from the right to manage trunks (`sip.admin`), and per-minute prices are public with a free plan that needs no card. LiveKit's own phone numbers are US only and inbound only, so outbound calls need a third-party SIP trunk, and the docs give no 429 or retry guidance.\n\n## Before you call either\n\n### 46elks Voice API\n\n1. Send numbers in E.164 format, such as +46700000000, or the request fails\n2. Pass `whenhangup` on `POST /calls` to learn when a call ends or fails to connect\n3. Don't retry a call request on a 4xx; retry 5xx with backoff, and check call history first to avoid a second call\n4. Treat caller speech, DTMF and SMS replies as untrusted input, and verify webhook origin\n5. Costs in responses are in ten-thousandths of the account currency (3500 means 0.35)\n\n### LiveKit Telephony\n\n1. Ask the operator for a short-lived token with only the `sip.call` grant to dial or transfer. Trunk, dispatch rule and number changes need `sip.admin`\n2. Use a third-party outbound trunk for outbound calls. LiveKit Phone Numbers only receive calls\n3. Set `wait_until_answered` on `CreateSIPParticipant` and read the SIP status on `SipCallError` before retrying. Voicemail answers with 200 OK\n4. Current server SDKs retry a failed call in another region with the same request id, which the server isn't documented to deduplicate. Check the room for an existing SIP participant before dialling again\n5. Send every request as a JSON POST to `/twirp/livekit.SIP/\u003cMethod\u003e` or `/twirp/livekit.PhoneNumberService/\u003cMethod\u003e` on the project's own host, with `{}` for an empty body\n6. A released number is billed for the whole month, and the free Build allowance is a hard cap after which requests fail\n\n## Questions\n\n### Which is better for AI agents, 46elks Voice API or LiveKit Telephony?\n\nLiveKit Telephony scores 67.6 (B) on agent readiness against 46elks Voice API's 44.4 (E), and leads in every scored category.\n\n### Do 46elks Voice API and LiveKit Telephony need an API key?\n\nBoth need an API key.\n\n### Can an agent call 46elks Voice API and LiveKit Telephony without installing anything?\n\n46elks Voice API has a hosted endpoint at https://api.46elks.com/a1. No hosted endpoint is listed for LiveKit Telephony.\n\n### Are 46elks Voice API and LiveKit Telephony open source?\n\nNo open-source release is listed for 46elks Voice API. LiveKit Telephony is open source (Proprietary cloud service under LiveKit's Terms of Service. The SIP service (livekit/sip), the protocol definitions, the CLI and the server SDKs are Apache 2.0).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.json, and with the fewest tokens: https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"46elks\", \"b\": \"livekit-telephony\"}`. From a terminal: `anchor compare 46elks livekit-telephony`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/46elks.json and https://www.anchorterminal.com/api/v1/tools/livekit-telephony.json\n\n## Other comparisons with 46elks Voice API or LiveKit Telephony\n\n- [46elks Voice API vs Bandwidth Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-bandwidth-voice.md)\n- [46elks Voice API vs didlogic Voice API](https://www.anchorterminal.com/compare/46elks-vs-didlogic.md)\n- [46elks Voice API vs Exotel Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-exotel-voice.md)\n- [46elks Voice API vs Infobip Calls API + MCP](https://www.anchorterminal.com/compare/46elks-vs-infobip-calls.md)\n- [46elks Voice API vs jambonz](https://www.anchorterminal.com/compare/46elks-vs-jambonz.md)\n- [46elks Voice API vs Plivo Voice API](https://www.anchorterminal.com/compare/46elks-vs-plivo-voice.md)\n- [46elks Voice API vs SignalWire Voice API](https://www.anchorterminal.com/compare/46elks-vs-signalwire-voice.md)\n- [46elks Voice API vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-sinch-voice.md)\n- [46elks Voice API vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-telnyx-voice.md)\n- [46elks Voice API vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-twilio-voice.md)\n- [46elks Voice API vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/46elks-vs-vonage-voice.md)\n- [46elks Voice API vs Voximplant](https://www.anchorterminal.com/compare/46elks-vs-voximplant.md)\n- [Bandwidth Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/bandwidth-voice-vs-livekit-telephony.md)\n- [Exotel Voice API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/exotel-voice-vs-livekit-telephony.md)\n- [Infobip Calls API + MCP vs LiveKit Telephony](https://www.anchorterminal.com/compare/infobip-calls-vs-livekit-telephony.md)\n- [jambonz vs LiveKit Telephony](https://www.anchorterminal.com/compare/jambonz-vs-livekit-telephony.md)\n- [LiveKit Telephony vs Plivo Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-plivo-voice.md)\n- [LiveKit Telephony vs SignalWire Voice API](https://www.anchorterminal.com/compare/livekit-telephony-vs-signalwire-voice.md)\n- [LiveKit Telephony vs Sinch Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-sinch-voice.md)\n- [LiveKit Telephony vs Telnyx Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-telnyx-voice.md)\n- [LiveKit Telephony vs Twilio Programmable Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-twilio-voice.md)\n- [LiveKit Telephony vs Vonage Voice API + MCP](https://www.anchorterminal.com/compare/livekit-telephony-vs-vonage-voice.md)\n- [LiveKit Telephony vs Voximplant](https://www.anchorterminal.com/compare/livekit-telephony-vs-voximplant.md)\n- [46elks Voice API vs DIDWW Voice and Number Management API](https://www.anchorterminal.com/compare/46elks-vs-didww-voice-and-number-management.md)\n- [didlogic Voice API vs LiveKit Telephony](https://www.anchorterminal.com/compare/didlogic-vs-livekit-telephony.md)\n- [DIDWW Voice and Number Management API vs LiveKit Telephony](https://www.anchorterminal.com/compare/didww-voice-and-number-management-vs-livekit-telephony.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-07", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "46elks Voice API vs LiveKit Telephony", "url": "" } ], "description": "LiveKit Telephony scores 67.6 (B) to 46elks Voice's 44.4 (E) for phone calls. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "46elks Voice API E 44.4", "LiveKit Telephony B 67.6", "scores" ], "h1": "46elks Voice API vs LiveKit Telephony", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/46elks-vs-livekit-telephony", "published": "2026-10-01", "section": "tools", "title": "46elks Voice vs LiveKit Telephony for AI agents (2026)", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/46elks-vs-livekit-telephony" }, "tokens": { "markdown": 5400, "slim": 3280 }, "version": 1 }