construe

Construe private beta

A person types a sentence. You get a structure.

Deterministic parsing at the edge. No model in the request path, no tokens per search — try it.

  • No model in the request path
  • A few milliseconds of CPU
  • Zero tokens per search
What you get back
// type a sentence and press Enter

Extraction — receipt-extraction

A photograph of a receipt becomes the same kind of structure.

Crooked, half-faded thermal print. The messy end of the problem is the only end worth solving.

What you get back
// drop a receipt

The whole integration

One tag, one attribute, one event.

The element owns the session, the socket, the debounce, the autocomplete and every way this can fail.

Read the docs — the endpoint you host, the object, the extraction protocol and the limits.

<script type="module" src="/construe.js"></script>

<construe-search src="/api/construe-bootstrap"></construe-search>

<script>
  document.querySelector('construe-search')
    .addEventListener('construe-submit', (e) => {
      // The structure, or null if the parse failed.
      runSearch(e.detail.constraint ?? { text: e.detail.prompt });
    });
</script>

Access

It is not open yet.

We are running it on our own two workflows first. Leave an address and what you would point it at — we read every one.