fenecdb.com valid

fenecdb

Minimal embedded document database: one file, live queries an app's

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-25T02:10:53.550Z. Cached copy · Source on fenecdb.com

# fenecdb

> Minimal embedded document database: one file, live queries an app's
> screens follow, a replica on the device that syncs with a server, a server
> over HTTP with a file per tenant, and search built in -- BM25 over text,
> with typos, highlights and facets, and HNSW vectors for meaning. It runs in
> the browser as WebAssembly, in an app, and as a server. Its query language
> is FenecQL, which is not SQL but reads SQL's everyday spellings.

Writing FenecQL -- the reference below spells it out in full:

- It is not SQL, but it reads SQL's everyday spellings as the statements
  they mean: `CREATE TABLE` and `CREATE INDEX`, `INSERT INTO t (a, b)
  VALUES (1, 'x')`, `UPDATE t SET a = 1 WHERE ...`, `IN (1, 2)`,
  `BETWEEN`, `LIKE` and `ILIKE`, `ON CONFLICT DO NOTHING` and `DO UPDATE
  SET`, `DISTINCT`, `EXISTS`, single quotes and `||`
  (https://fenecdb.com/docs/sql). A double-quoted word is text, never a
  column: a field is written bare, `where name = 'Ada'`. Every row has an
  `id` (an int the database makes; no `rowid`, no `_id`). A JOIN on a
  key is read as `lookup`, which FenecQL writes `get orders lookup users on
  id = user_id` -- each order with its user nested; the clauses after
  `lookup` are the looked-up collection's -- and a filter by another
  collection's rows is an uncorrelated
  `in (get <collection> select <field> where ...)`, or `not in (...)` for
  the rows it does not name. There is no interactive
  transaction: a `/batch` of statements (in the page, a `run` of several)
  lands whole or not at all, and `require <n>` after a write makes its count
  a condition that puts the whole batch back.
- The aggregates -- `count(*)`, `count(f)` (the rows where `f` is not
  null), `count(distinct f)`, `sum`, `avg`, `min`, `max`, `first(f by k)`,
  `last(f by k)` -- go in the select list, over every match or per
  `group <key>`, and `having` keeps groups. Distinct values are a group:
  `select city group city`.
- Text: `like 'a%'` and `ilike` take SQL's `%` and `_`; `~` is a
  case-insensitive *contains* (`email ~ "@example.org"`), never a regular
  expression, and `match` ranks words over an `@text` field.
- Square brackets are list literals and nothing else: `tags: ["a", "b"]`,
  `tags [text]`. Nothing here marks an optional part with them; a clause you
  do not need is simply left out.
- Strings take double or single quotes. Parameters are `$1`, `$2`, ...; a vector
  parameter is a list of numbers. A timestamp is written as text,
  `"2026-09-01T10:00:00Z"`, or `"2026-01-01"` in a comparison.
- Types: `bool int float text bytes timestamp`, lists such as `[text]`,
  `json` (any JSON value; a path such as `meta.source` reads into it),
  `geo` (a point, `[lon, lat]`), `vector<N>`, `vector<N, f16>` and
  `sparse<N>`. A typed field holds no object; a `json` field does. There is
  no decimal -- money is an `int` of cents -- and no UUID type (use
  `text @hash`).
- Indexes: `@hash` for equality, `@unique` for a value only one row may ho
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=fenecdb.com · GET /v1/domain/fenecdb.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for fenecdb.com:
1. POST https://agentwebmap.com/v1/sites/fenecdb.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://fenecdb.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/fenecdb.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/fenecdb.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.