# Linq vs Plivo API (slim)

> Linq scores 71.7 (BB) to Plivo's 63.6 (B) for sms. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/linq-vs-plivo.md (~4,000 tokens) · this version ~1,980 tokens · JSON https://www.anchorterminal.com/compare/linq-vs-plivo.json · canonical https://www.anchorterminal.com/compare/linq-vs-plivo
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Linq scores 71.7 (BB) on agent readiness against Plivo API's 63.6 (B), and leads in 4 of 7 scored categories. Plivo API leads on reliability. Both do sms.

- Linq: BB 71.7, rank #151 of 1510 · https://www.anchorterminal.com/tools/linq.min.md
- Plivo API: B 63.6, rank #508 of 1510 · https://www.anchorterminal.com/tools/plivo.min.md
- Linq, good for Agents that talk to people over iMessage with SMS fallback, such as assistants and concierge bots. Ahead on Schema & documentation, 93 against 59; Agent ergonomics, 90 against 57; Maintenance & community, 83 against 78. Also Agent-ready, a grade of BB or better; Runs on your own machine.
- Plivo API, good for Cost-sensitive SMS and WhatsApp sends from code, and for teams that also use Plivo voice. Ahead on Reliability, 90 against 83.

| Category | Linq | Plivo API |
| --- | --- | --- |
| Reliability (16%) | 83 | 90 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 93 | 59 |
| Agent ergonomics (13%) | 90 | 57 |
| Security & auth (14%) | 50 | 50 |
| Payments & pricing (10%) | 40 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 78 |
| Transparency & trust (7%) | 72 | 71 |

| Fact (where they differ) | Linq | Plivo API |
| --- | --- | --- |
| Vendor | Linq App Inc. | Plivo |
| Hosted endpoint | `https://api.linqapp.com/api/partner/v3` | `https://api.plivo.com/v1` |
| Transports | HTTP, stdio | HTTP |
| Pricing | Paid | Pay per use |
| Price for sms | not published | $0.0077 per message |
| Licence | Proprietary service under Linq App Inc.'s terms of service and sale. The TypeScript, Python and Go SDKs, the MCP server and the CLI are Apache-2.0 | MIT |
| Tools exposed | 2 | none |
| MCP registry | `io.github.linq-team/linq` | not listed |
| Last release | 2026-11-05 | 2026-10-28 |
| Terms last updated | 2026-04-14 | 2026-04-29 |
| Privacy policy last updated | 2026-06-26 | 2026-05-27 |
| Terms restrict benchmarking | yes | not found in the text |
| Popularity | 264k npm/wk | 102 stars, 51k npm/wk, 69k PyPI/wk |
| Agent reviews | none | 3.5/5 (2) |

Why the edge:
- Schema & documentation, Linq +34: Linq 93 (OpenAPI 3.1 file for the Partner API and another for WhatsApp, both public (25). llms.txt, llms-full.txt and Markdown for every page (10). Guides say when to check capability, when to use idempotency keys and which limits are bugs (17 of 20). 93 enums in the spec and typed parts for messages (14 of 15). Curl and SDK examples on every guide and a page for each numbered error code (15). Versioned paths (v2 and v3) with fields marked deprecated in the spec, and a dated changelog only in the SDK repository (12 of 15). 25 + 10 + 17 + 14 + 15 + 12 = 93.); Plivo API 59 (No OpenAPI spec found (0). llms.txt at plivo.com/docs/llms.txt (10). Reference pages state what each endpoint does, with little on when not to use one (12 of 20). Parameter tables with types and required flags, no machine-readable schema (10 of 15). Examples in each SDK language. We didn't recheck the messaging error list this run (12 of 15). Versioned v1 path and a public changelog (15).)
- Agent ergonomics, Linq +33: Linq 90 (The MCP server has two tools, code execution against the SDK and docs search, so its definitions cost little context (25). Lists are paginated, with SDK pagination helpers; we didn't read every list endpoint's filters (16 of 20). Error bodies carry a numbered code, a message, a `doc_url` and a `trace_id`, with a page per code (20). `idempotency_key` on message sends and the SDKs add keys and retry twice by default; webhook IDs double as deduplication keys. In the MCP server only the docs search tool carries readOnlyHint (14 of 20). A send needs `from`, `to` and one message part; official SDKs in TypeScript, Python and Go (15). 25 + 16 + 20 + 14 + 15 = 90.); Plivo API 57 (List endpoints take limit and offset, with no field selection (15 of 25). Message list filters weren't rechecked this run (15 of 20). HTTP status errors, and we didn't recheck the messaging error-code list this run (12 of 20). No idempotency key or safe-retry guidance for sends found (0 of 20). Official SDKs in Node, Python and other languages, and a send needs src, dst and text (15).)
- Reliability, Plivo API +7: Linq 83 (Read with the hosted lines. status.linqapp.com lists components for the V3 and V2 APIs, WhatsApp and the dashboard, with history (20). From 8 August to 6 November its feed records six minor incidents, among them partial degradation on some lines on 13 August, elevated error rates on 22 September, authentication errors on 29 September, degraded sending on 9 October (22 minutes), webhook degradation at the start of November and latency on 5 November; the critical and major incidents fall in May to July (20). Rate limits with numbers per sender and recipient pair and for capability checks (15). 429 carries Retry-After and `retry_after`, the docs give backoff guidance, and sends take an `idempotency_key` (15). llms.txt states 99.95% uptime, but the contractual SLA is Enterprise only, no SLA document is public and the terms disclaim availability (3 of 10). Partner API v3 is generally available (10). 20 + 20 + 15 + 15 + 3 + 10 = 83.); Plivo API 90 (Statuspage at status.plivo.com with components and a readable history feed (20). From 6 August the feed posts announced India carrier maintenance (13 to 14 August, announced on 5 August), voice call webhooks degraded for a subset of calls (25 August), intermittent call failures to India (11 September, 10 October) and announced Plivo CX console and flows maintenance (23 October). None touches messaging, so a clean record for this listing (30). API limit published, 300 requests per 5 seconds, with a 429 above it (15). The API overview's error table answers 429 with "Implement exponential backoff", backoff guidance with no Retry-After or safe-retry guidance for sends (10 of 15). Plivo's Platform Service Levels document covers support response times only, with no availability figure or credits (5 of 10). Messaging API is generally available (10). 20 + 30 + 15 + 10 + 5 + 10 = 90.)
- Maintenance & community, Linq +5: Linq 83 (`@linqapp/sdk` and `@linqapp/sdk-mcp` 0.80.0 on 5 November 2026 (30). Releases on 1, 8 and 9 October and twice on 5 November, with API changes such as `line_type` and new 429 responses (20). Closed service with an SDK changelog, a help centre and a Slack channel on Pro; GitHub issue replies weren't sampled (8 of 15). `io.github.linq-team/linq` in the official MCP registry under a verified GitHub namespace, and current SDKs in three languages (15). The SDK repository runs CI and release-please, with 263,752 npm downloads in the week to 5 November (10). 30 + 20 + 8 + 15 + 10 = 83.); Plivo API 78 (plivo-cli v1.3.2 on 28 October 2026, the official Plivo CLI's newest release, adding voice stream simulate and readiness commands (30). In the 90 days from 6 August, 13 plivo-cli releases from v0.3.0 (28 August) to v1.3.2 (v1.3.1 was tagged but never released), plivo-go 7.61.0, plivo-java 5.51.0 and plivo-dotnet 5.53.0 (19 August, Caller Reputation parameters) and plivo-python v4.63.0 (25 September, an auto-pagination fix), well over three (20). The product changelog's newest entry is 6 January 2025. Closed service with support; we didn't sample GitHub issue replies (8 of 15). Official SDKs current in several languages (15). CI and dependency state not checked, and plivo-node hasn't released since 28 July (5 of 10). 30 + 20 + 8 + 15 + 5 = 78.)