<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">
<title>Jepela: blog and changelog</title><link href="https://jepela.com/feed.xml" rel="self"/><link href="https://jepela.com/"/><id>https://jepela.com/feed.xml</id><updated>2026-10-15T00:00:00Z</updated><author><name>Jepela</name></author>
<entry><title>When not to use an LLM for a decision</title><link href="https://jepela.com/blog/when-not-to-use-an-llm.html"/><id>https://jepela.com/blog/when-not-to-use-an-llm.html</id><updated>2026-10-15T00:00:00Z</updated><summary>If your code needs one judgment from a known set of answers, a text generator is more than you need. When to use a decision engine, and when not.</summary></entry>
<entry><title>What our engine gets wrong, and why limits go in code</title><link href="https://jepela.com/blog/what-our-engine-gets-wrong.html"/><id>https://jepela.com/blog/what-our-engine-gets-wrong.html</id><updated>2026-10-15T00:00:00Z</updated><summary>The Jepela engine does not compare numbers or read negation, and lines move answers by being there. Measured, with what we check in code instead.</summary></entry>
<entry><title>Jepela accounts are open: a decision API that remembers</title><link href="https://jepela.com/blog/jepela-is-open.html"/><id>https://jepela.com/blog/jepela-is-open.html</id><updated>2026-10-15T00:00:00Z</updated><summary>Since 2026-10-15 businesses can sign up for Jepela, a decision API with memory: typed answers with probabilities, and output is free.</summary></entry>
<entry><title>Forgetting with proof</title><link href="https://jepela.com/blog/forgetting-with-proof.html"/><id>https://jepela.com/blog/forgetting-with-proof.html</id><updated>2026-10-15T00:00:00Z</updated><summary>Jepela&#x27;s forget removes a fact from a subject&#x27;s memory, then checks that recall no longer finds it. What it removes, what stays, and a measured run.</summary></entry>
<entry><title>Changelog: Accounts open, with card top-ups</title><link href="https://jepela.com/changelog.html#2026-10-15-accounts-open-with-card-top-ups"/><id>https://jepela.com/changelog.html#2026-10-15-accounts-open-with-card-top-ups</id><updated>2026-10-15T00:00:00Z</updated><summary>Business customers can open an account at app.jepela.com. Jepela approves each new account. Prepaid credit can be added by card, on the payment provider&#x27;s checkout page where VAT is added, or by invoice. The price is unchanged: $0.042 per million input tokens, output free. See Pricing.</summary></entry>
<entry><title>Changelog: Calibration for yes/no questions</title><link href="https://jepela.com/changelog.html#2026-09-29-calibration-for-yes-no-questions"/><id>https://jepela.com/changelog.html#2026-09-29-calibration-for-yes-no-questions</id><updated>2026-09-29T00:00:00Z</updated><summary>Calibration fitted on your own labels now also sets a shift for yes/no questions, for a question the engine leans towards yes or no on. Measured on public benchmark yes/no questions: fitted on 593, the other 461 went from 59.2% to 70.1% right. Details in Quality.</summary></entry>
<entry><title>Changelog: Public, with live demos</title><link href="https://jepela.com/changelog.html#2026-09-28-public-with-live-demos"/><id>https://jepela.com/changelog.html#2026-09-28-public-with-live-demos</id><updated>2026-09-28T00:00:00Z</updated><summary>jepela.com, the documentation and the live demos are open to everyone. A try-it box on the home page asks the live engine three questions, with and without one account&#x27;s memory. Jepela Arcade: seven games where two players make the same decisions and only one has a Jepela memory. Station 7, a first-person game, and a gallery of twelve small apps that decide with memory.</summary></entry>
<entry><title>Changelog: Matching for choices with many options</title><link href="https://jepela.com/changelog.html#2026-09-27-matching-for-choices-with-many-options"/><id>https://jepela.com/changelog.html#2026-09-27-matching-for-choices-with-many-options</id><updated>2026-09-27T00:00:00Z</updated><summary>A choice with more than 20 options is matched by vectors by default. &quot;method&quot;: &quot;engine&quot; still reads every option. Measured on 600 bank messages with 77 intents: 65.2% right, against 62.2% for the engine reading all 77. A matched choice is billed for the state and memory it read, not its options: 23 tokens against 812 on that test. Details in Choice.</summary></entry>
<entry><title>Changelog: Memory, fine-tuning and shared passes</title><link href="https://jepela.com/changelog.html#2026-09-26-memory-fine-tuning-and-shared-passes"/><id>https://jepela.com/changelog.html#2026-09-26-memory-fine-tuning-and-shared-passes</id><updated>2026-09-26T00:00:00Z</updated><summary>Recall also searches the subject&#x27;s names and aliases, and the question&#x27;s own words. Pinned lines go first at every decision about a subject, and exclusion rules remove options in code. Fine-tuning: a model of your own from your labelled cases, used only when it beats the standard engine on cases it never saw and still listens to memory. Requests that arrive together share one pass on the engine.</summary></entry>
<entry><title>Changelog: The Jepela API goes live</title><link href="https://jepela.com/changelog.html#2026-09-24-the-jepela-api-goes-live"/><id>https://jepela.com/changelog.html#2026-09-24-the-jepela-api-goes-live</id><updated>2026-09-24T00:00:00Z</updated><summary>The hosted API at api.jepela.com, in the United States region. Keys, prepaid credit with a ledger, and a memory per subject. Three question types: choice, score and noul (yes or no), each with probabilities and a confidence. $0.042 per million input tokens. Output and memory writes are free.</summary></entry>
</feed>
