Lockally

      Use your API key in the examples

      Replaces lk_live_… in the code samples on this site so you can copy and run them. It is stored in this browser only and is never sent anywhere, including to Ask AI.

      It will be visible on the page. Use a test key if you are sharing your screen or taking screenshots.

      Deliverability fundamentals

      Deliverability is decided by the receiving mailbox provider, not by us and not by you. What either of us can do is remove the reasons they have to doubt you.

      This section is about what this platform actually does, so you can tell which of the usual advice applies here and which is somebody else’s product.

      What the platform does without being asked

      Signs every message SPF, DKIM and DMARC alignment come from domain verification. See Email authentication.
      Refuses obviously dead recipients A pre-send MX check rejects a domain with no mail exchanger before it becomes a bounce.
      Suppresses hard bounces automatically A permanent failure adds the address to your suppression list, and later sends to it are skipped.
      Suppresses complaints automatically Where a feedback loop delivers one. See Complaint handling.
      Watches your bounce rate and acts Throttle, then suspend, without a human in the loop. See Sender reputation.
      Caps a new domain’s daily volume A ramp over roughly four weeks. See Warm-up.

      What it does not do

      It does not clean your list. There is no verification service, no role-address detection and no syntax-quality scoring beyond refusing an undeliverable domain.

      It does not track opens or clicks. No pixel, no link rewriting. Delivery reporting is aggregate counts by outcome instead. This is a deliberate choice and it means engagement-based list hygiene is something you do with your own data.

      It does not give you a dedicated IP. Everyone sends from the same address. See Shared and dedicated IPs.

      It does not decide what you send. Content, cadence and consent are yours. Nothing here rescues mail that people did not ask for.

      The three things that actually matter

      In order of how often they are the problem:

      1. Send to people who asked. Every mechanism on this page is downstream of consent. A bounce rate, a complaint rate and a spam-folder placement are all measurements of the same underlying thing.
      2. Authenticate properly. Unauthenticated mail is rejected or foldered before anything else about it is considered. This one is mechanical and you either did it or you did not.
      3. Keep volume steady and your list clean. A cold domain that sends 50,000 messages on its first day is a spam signal regardless of consent.

      Transactional and bulk are different problems

      A receipt sent to one person who just bought something, and a newsletter sent to forty thousand people, fail in different ways and are judged differently.

      The platform separates them with the unsubscribe flag on each send. There is no stream field to set: "unsubscribe": true makes a send broadcast, and its absence makes it transactional. That one boolean also decides which suppressions apply and whether a one-click unsubscribe header is added. See Transactional and bulk.

      Where to look when something is wrong

      Symptom Start at
      Sends rejected before they leave Sending rate management and Warm-up
      Messages accepted, never confirmed Temporary and permanent failures
      Some recipients never receive anything Suppression management
      Your rate cap dropped on its own Sender reputation
      Mail lands in spam Email authentication, then Monitoring