Questions

Ledger is invite-only for now. Join the waiting list and 100x sends you a personal invite link. It works once and expires after 14 days.

No. Twilio sends Ledger a copy of each message event. Vapi sends its report after the call has ended. The SDK hands your code the exact same requests and responses. Ledger is never in the path of a reply to your customer.

No. The SDK queues events in memory and sends them in the background, in batches. The connectors receive copies, after the fact.

Your assistant keeps working. The SDK retries a failed batch 3 times, then drops it, without ever throwing an error into your app.

Yes, with the HTTP API: send events to POST /api/v1/events with your API key. Up to 500 events per request, 8 MB at most, 600 requests a minute per key. Sending an event with the same id again never counts it twice.

curl -s https://ledger.100xnative.com/api/v1/events \
  -H "Authorization: Bearer $LEDGER_KEY" \
  -H "content-type: application/json" \
  -d '{"events":[
    {"type":"message","id":"m1","conversationId":"c1","role":"customer","text":"Do you open on Friday?","at":"2026-10-25T09:00:00Z"},
    {"type":"message","id":"m2","conversationId":"c1","role":"agent","text":"Yes, from 4 pm.","at":"2026-10-25T09:00:03Z"},
    {"type":"outcome","id":"w1","conversationId":"c1","win":"booking","value":390,"currency":"AED","at":"2026-10-25T09:01:00Z"}
  ]}'

A Python package is planned. Until then, the API is the way.

Twilio and Vapi carry the conversation, not the result. Your bookings, leads or payments live in your own system. Send each one to Ledger when it happens, with the SDK or the API. A win does not need a conversation id:

ledger.outcome({ win: "booking", value: 390, currency: "AED" }); // no conversationId needed

Resolutions are the exception: when you send none, Ledger works them out from the conversations. See how.

Yes. Each route gets its own link or key, and everything lands in the same workspace. A common setup: Twilio for the messages, plus the SDK for the wins.

Ledger counts conversations, not messages. With Twilio, one conversation is one customer’s messages over 24 hours from their first message. A conversation also needs at least one message from the customer.

Ledger needs your opening hours to know when you are closed. Add them in Settings → Workspace. Until then, nothing is counted as closed, so the card never makes a claim without data.

No. A rate needs at least 10 conversations (or 10 calls) to mean something, and mood, topics and unanswered questions appear once Ledger has read your conversations. See the basics.

Yes, in Settings → Workspace. Your dashboard switches to the cards of the new type.

Your workspace currency. Currencies with a fixed rate to the US dollar (AED, USD, SAR, QAR, BHD, OMR, JOD) are converted at that rate. Others, such as EUR, show “—” for costs for now.

No. From a Vapi call, Ledger keeps the call’s times, status and cost, and the spoken lines as masked text, for 90 days. No audio.

No one can: Ledger keeps only a fingerprint of it. Create a new one in Settings → Keys, update your app or your Twilio or Vapi setting, then revoke the old one. Why keys are shown once.

Free during the pilot. Invite only. No card. Ask us about pricing after the pilot.