Jev (TypeSafe AI) inside SQL and document pipelines: pg-jev, sqlite-jev, DocJev

What pg-jev, sqlite-jev, sqlite3-jev, pg-redact and DocJev do when a Jev call fails, is unsure or has no key, and what text they send. 8 Oct 2026. The title is the pool's own label. When the pool checked search suggestions on 8 Oct 2026, 05:16–05:17 UTC, no phrase about Jev in databases was offered by two of the three endpoints: Google offered "jev postgres", Bing and DuckDuckGo offered nothing for it, and "jev sql", "jev sqlite", "jev database" and "jev pdf" had no matching suggestion on any of the three. A suggestion shows that people search for something; it does not show how many.

Before you call Jev from a query or a pipeline

1. Expect a Jev error to stop the statement or the request.

   All 5 raise on a Jev error or timeout (5 of 5 fail-closed). In SQL that aborts the statement; it does not return partial rows. Timeouts and retries per project are in the table; general advice is on errors and rate limits.

   fail-closed 5 of 5
2. Know what "unsure" becomes.

   Below threshold, 2 of 5 return false or 0 to your query (pg-jev, sqlite-jev, threshold 0.5), 1 of 5 has no threshold and returns the raw value (sqlite3-jev), and 2 of 5 act anyway (pg-redact stores the span unredacted; DocJev joins the page to the current document).

   returns to the query 2no-threshold 1acts-anyway 2
3. Do not use a Jev predicate as an access-control WHERE clause.

   Below the threshold jev() returns false; answers are cached per session (pg-jev) or per process (sqlite-jev), so a changed policy may not be asked again.

   pg-jev, sqlite-jev: answer cache
4. Assume the whole row or page leaves the database.

   pg-jev sends each whole row as JSON, not only the columns in the predicate. See what each project sends.

   5 of 5 send text out
5. Set a spend guard.

   pg-jev sends one request per 20 rows; sqlite-jev's jev_rows table sends up to 500 rows per query in batches of 40.

   calls per row in the table

What each project does when Jev fails, is unsure or has no key

Documented Source at the pins below. Error, malformed and no-key cells and timeouts were read on 7 Oct 2026 and reused; what Jev decides, below threshold, bypass, data sent and calls were read on 8 Oct 2026, 05:15–05:16 UTC, at the same pins. Colour marks the verdict cells only (error, malformed, below threshold, no key).

• fail-closed or held (the item does not go ahead; a person, the host's prompt or, for two passage filters, the code's own cut decides)
• fail-open or acts-anyway; a "conditional" cell that can act is counted fail-open
• fallback-<what> (named in the cell)
• no-decision (nothing returned; caller must handle)
• advisory (Jev never decides), or conditional where the page has no count
• not recorded, not applicable or no-threshold (the cell says which)

• Jev error or timeoutof 5
  • fail-closed5 of 5
• Malformed answerof 5
  • fail-closed4 (pg-jev, sqlite3-jev, sqlite-jev, DocJev)
  • fail-open1 (pg-redact)
• Below thresholdof 5
  • returns false or 0 to the query2 (pg-jev, sqlite-jev)
  • no-threshold1 (sqlite3-jev)
  • acts-anyway2 (pg-redact, DocJev)
• No keyof 5
  • fail-closed4
  • sent without a key1 (sqlite3-jev)
• Bypassof 5
  • recorded4
  • none found1 (sqlite3-jev)

sqlite-jev's malformed cell is counted fail-closed; its jev_rows NULL-column path is a no-decision detail inside that cell. pg-redact's malformed cell is counted fail-open because a missing span answer stores text unredacted; a broken body gives 502.

Which of the 5 are counted on When Jev fails

Counted 2 of 5; returns to the query 3 of 5.

• Not counted (3): pg-jev, sqlite3-jev and sqlite-jev. These three SQL extensions return Jev's value into your query. Your query, not the extension, decides what to do with that value, so they are listed but not counted on When Jev fails. This follows the pool's counting rule from 8 Oct 2026. A Jev error still aborts the statement, as the table above shows.
• Counted (2): pg-redact and DocJev. Their own code acts on Jev's answer: pg-redact decides which spans are redacted before it writes the message; DocJev builds the page groups. Two rows are too few for a domain of their own, so they sit in the nearest existing domains on When Jev fails by domain: pg-redact under Content moderation (PII redaction before storage) and DocJev under Email and lead (document splitting).

What text leaves the database

Documented From source at the pins above, read 8 Oct 2026.

pg-jev sends each whole row as JSON (every column), 20 rows per request. The SQLite extensions send what the SQL passes; sqlite-jev's jev_rows sends every non-hidden column. pg-redact sends the whole message before it stores it. DocJev sends page text. How long that text is kept depends on the route you call Jev through: see What data leaves your system when you use Jev. Timeouts and retries in general: Jev errors and rate limits.

No project publishes a price or token count per row, so this page gives no cost per row; calls per row or batch are in the table.

Six further SQL candidates (not audited, not counted)

Found on 8 Oct 2026 and read for one line each at the commit shown (HEAD on 8 Oct, 05:16 UTC). Documented for the line quoted; nothing else was read.

• judoaseeta/duckdb-jev (58e5484): calls api.typesafe.ai; its boolean number >= threshold returns to the query.
• Sheltercosmo/jev4pg (511432a): a TYPESAFE_API_KEY read was found; the call path was not recorded.
• wuxianliang/pg_typesafe (11d9358): reads the key from TYPESAFE_API_KEY; the endpoint was not located.
• sashimikun/sql-jev (f8a6937): fetch(config.apiUrl); default URL not read; predicates return to the query.
• Peterrallojay/sqlite-utils-jev (8ddfaeb): calls the TypeSafe endpoint and raises with no key. Its README says it saves results (Reported); the write was not located.
• qsliu2017/pg_jevplanner (5e88834): a PostgreSQL planner_hook that falls back to standard_planner. Its own code acts on Jev's answer (query planning), so it could be counted on When Jev fails after a full read.