Polymorfa vs TimelinesAI

Three reasons teams move from TimelinesAI

1. 01

   Webhooks you can build a business on

   Polymorfa signs every delivery with HMAC-SHA256 and makes up to eight delivery attempts over 24 hours, set per webhook. Delivery and attempt records are readable and retryable through the API, so a missed event is something you can find and replay.¹⁰

   TimelinesAI: TimelinesAI webhooks carry no signature, allow no custom headers and get three attempts.^1,11

   import { createHmac, timingSafeEqual } from "node:crypto";
   
   // native format: X-Webhook-Signature, HMAC-SHA256 of the raw body
   function verify(rawBody: string, signature: string, secret: string) {
     const expected = Buffer.from(createHmac("sha256", secret).update(rawBody).digest("hex"));
     const received = Buffer.from(signature);
     return expected.length === received.length && timingSafeEqual(expected, received);
   }

2. 02

   Throughput per number, with no call meter

   A Polymorfa Standard number sends up to 10 messages a second, and a Pro number up to 100.⁵ A linked-device number is billed per online day, not per message, and sends accept an Idempotency-Key so a retry never messages a customer twice.^4,12

   TimelinesAI: TimelinesAI caps the API at 50 requests a minute, spaces sends about 2 seconds apart and bills extra calls by the 100,000.^2,13

3. 03

   An API that is the product, not a tab in the settings

   Polymorfa publishes an OpenAPI 3.1 reference pinned by a Polymorfa-Version contract date, development prerelease SDK documentation, and an MCP server with 195 tools.^14,15,9 Calls from code and SIP trunks sit on the same numbers.^7,8

   TimelinesAI: TimelinesAI sells seats for its inbox and CRM sync. The API allowance and usage sit in the workspace under Integrations → Public API.²