Pg TypeSafe

It is labelled pre-alpha. It supports PostgreSQL 15, 16, 17 and 18 on Linux and macOS with libcurl 7.61 or newer, via prebuilt binaries, a Docker image, PGXN, or a source build. Installing needs write access to pkglibdir, and the API key is set on the server process rather than in SQL.

Scalar functions issue one HTTP call per row, which is why the batched variants exist. In the repo's demo, typesafe_detect once per distinct text took 23 s while typesafe_detect_many classified the same 38 distinct NYC 311 resolution strings in two requests in 0.86 s, at the default batch_size of 32 with http_concurrency 4.

Yes. typesafe.mock_response short-circuits the HTTP call and returns the given body verbatim. It is superuser-only on purpose, so a granted app role cannot forge classification answers, and the repo ships a mock regression suite against sql/typesafe.sql and expected/typesafe.out.

Yes, via the superuser-only typesafe.api_key_file setting, which points at a file whose first line is the key and keeps it out of SQL and logs. Note the tradeoffs: the endpoint must be https://, with plain http:// allowed only toward localhost, responses are capped at 8 MB, and 429/529 are retried up to three times honoring Retry-After. SET typesafe.api_key does appear in query logs.

PostgreSQL 15, 16, 17, and 18 on Linux and macOS, with libcurl 7.61 or newer. It is MIT-licensed and marked pre-alpha, and is not affiliated with TypeSafe AI or the PostgreSQL Global Development Group.

With TYPESAFE_API_KEY set, install.sh sends the key to the server over COPY ... FROM STDIN, never in statement text or logs, writes typesafe.key in the data directory, and points typesafe.api_key_file at it. It finds every PostgreSQL 15+ server, uses a checksum-verified prebuilt binary or builds from source, and needs no restart.

Scalars issue one HTTP call per row, while the *_many functions batch distinct values at typesafe.batch_size (default 32) with overlapping chunks at typesafe.http_concurrency (default 4). In the NYC 311 demo, classifying 38 distinct strings took two TypeSafe requests and 0.86 s, against 23 s for the per-text scalar.