@clinia/context-engine-js 0.5.0-rc.0

package/CHANGELOG.md

@@ -0,0 +1,57 @@
+# @clinia/context-engine-js
+
+## 0.5.0-rc.0
+
+### Minor Changes
+
+- db7bdab: **`@clinia/context-engine-js` is now published to the public npm registry.** Install it with `npm install @clinia/context-engine-js` — no registry configuration, no `.npmrc`, no authentication. Previously it existed only on GitHub Packages, so a clone outside the Clinia org could not install it at all.
+
+  Publishing continues to GitHub Packages as well, at the same version, so anything already resolving from there keeps working. The npm publish is the source of truth; the mirror is best-effort.
+
+  The package now declares `license: "Apache-2.0"` and ships a `LICENSE` file and its `CHANGELOG.md`. It carries no `repository` field on purpose: the source monorepo is private, so the link npm would render 404s for every consumer.
+
+  Two packaging defects are fixed while the consumer base is still small. `exports` listed the `import` condition before `types`, and there was no top-level `types` — so consumers on `moduleResolution: "node"` resolved the package with no type declarations at all. Both are corrected; the package remains ESM-only, which the README now states outright, since `require()` of it throws `ERR_REQUIRE_ESM`.
+
+  **`{ clientId, clientSecret }` is now a complete `auth` config.** The token endpoint and the RFC 8707 `resource` indicator default to Clinia's authorization server, so connecting to a workspace no longer means copying two console URLs into your code. `tokenUrl` and `issuer` still override it for a different authorization server, and `resource` is only defaulted when the endpoint is too — a third-party token endpoint never receives Clinia's resource value. Nothing breaks: every config that was valid before still means what it meant, and `tokenUrl` merely became optional.
+
+- 405af06: **Renamed: `@clinia/patient-memory-js` is now `@clinia/context-engine-js`.**
+
+  To upgrade, change the dependency name and your imports, and rename two symbols:
+  - `PatientMemoryClient` → `ContextEngineClient`
+  - `PatientMemoryClientOptions` → `ContextEngineClientOptions`
+
+  Nothing else about the surface changed: same constructor options, same `http` client, same generated types and resource classes. Versions 0.4.0 and earlier remain published under the old name and are not being withdrawn, but no further versions will be released there.
+
+  The types are now generated from `openapi/context-engine.yaml`, which is the spec attached to each release under that name.
+
+  The retired name is also gone from everything the package ships, which the rename had missed: the `auth` module's doc comment (carried into `dist/auth.d.ts` and into the sourcemap's inlined source), and the README's `audience` example, `baseUrl` sample host, and options table. `CHANGELOG.md` still names `@clinia/patient-memory-js` on purpose — an upgrading consumer needs to know what the package used to be called.
+
+> Renamed from `@clinia/patient-memory-js`. Versions 0.4.0 and earlier were
+> published under the old name; entries below them predate the rename and still
+> refer to it.
+
+## 0.4.0
+
+### Minor Changes
+
+- 750b6ff: Every API operation now declares an OpenAPI `operationId` (kebab-case, enforced by lint), emitted as `http.operation_id` on HTTP server spans, as a label on the `http.server.request.duration` histogram, and as `httpOperationId` on request logs. The mapping is derived at runtime from the app's OpenAPI route definitions — no hand-maintained registry. The published spec includes the ids, which activates the client's resource generation: `@clinia/patient-memory-js` now ships generated resource classes (`PatientsResource`, `IngestResource`, `SessionsResource`, `VFSResource`; not yet wired into `PatientMemoryClient`) with camelCase method names derived from the full operationId, and the generator was fixed for case-sensitive filesystems and enum query params. Inline-schema and non-JSON request bodies are supported too: `ingestFhir` types its body off the generated `operations` interface, and `ingestCda` sends `text/plain` with a passthrough serializer.
+- 29b6fb3: Add OAuth2 client-credentials authentication to the JS client (PAM-468). Pass
+  `auth` a `ClientCredentialsConfig` and the client acquires, caches, and refreshes
+  a bearer token for you; or pass `auth` a `() => string | Promise<string>` token
+  function for full control (a token from elsewhere, a different grant, or a custom
+  refresh strategy). The `createClientCredentialsTokenProvider` helper is exported
+  for sharing one cached provider across clients or transports.
+
+## 0.4.0-rc.1
+
+## 0.4.0-rc.0
+
+### Minor Changes
+
+- 750b6ff: Every API operation now declares an OpenAPI `operationId` (kebab-case, enforced by lint), emitted as `http.operation_id` on HTTP server spans, as a label on the `http.server.request.duration` histogram, and as `httpOperationId` on request logs. The mapping is derived at runtime from the app's OpenAPI route definitions — no hand-maintained registry. The published spec includes the ids, which activates the client's resource generation: `@clinia/patient-memory-js` now ships generated resource classes (`PatientsResource`, `IngestResource`, `SessionsResource`, `VFSResource`; not yet wired into `PatientMemoryClient`) with camelCase method names derived from the full operationId, and the generator was fixed for case-sensitive filesystems and enum query params. Inline-schema and non-JSON request bodies are supported too: `ingestFhir` types its body off the generated `operations` interface, and `ingestCda` sends `text/plain` with a passthrough serializer.
+- 29b6fb3: Add OAuth2 client-credentials authentication to the JS client (PAM-468). Pass
+  `auth` a `ClientCredentialsConfig` and the client acquires, caches, and refreshes
+  a bearer token for you; or pass `auth` a `() => string | Promise<string>` token
+  function for full control (a token from elsewhere, a different grant, or a custom
+  refresh strategy). The `createClientCredentialsTokenProvider` helper is exported
+  for sharing one cached provider across clients or transports.

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Clinia Health Inc.
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/README.md

@@ -0,0 +1,154 @@
+# @clinia/context-engine-js
+
+TypeScript client for the Clinia Context Engine API. A thin, typed wrapper over
+[`openapi-fetch`](https://openapi-ts.dev/openapi-fetch/) — request/response
+shapes are generated from the OpenAPI contract, so paths, params, and bodies are
+fully type-checked. Works in Node 20+ and modern browsers on the standard
+`fetch`.
+
+## Install
+
+```sh
+npm install @clinia/context-engine-js
+```
+
+Published on [npm](https://www.npmjs.com/package/@clinia/context-engine-js). No
+registry configuration or authentication is needed.
+
+While the engine is in release-candidate phase, the newest build is under the
+`rc` dist-tag:
+
+```sh
+npm install @clinia/context-engine-js@rc
+```
+
+**This package is ESM-only** (`"type": "module"`). `require()` of it throws
+`ERR_REQUIRE_ESM`; use `import`, or a dynamic `await import()` from CommonJS.
+
+## Exports
+
+| Export                                     | Description                                                                 |
+| ------------------------------------------ | --------------------------------------------------------------------------- |
+| `ContextEngineClient`                      | Entry point. Holds a low-level `http` client.                               |
+| `HttpClient`                               | Typed `openapi-fetch` wrapper (`GET`/`POST`/`PUT`/`PATCH`/`DELETE`, `use`). |
+| `ContextEngineClientOptions`               | Constructor options (alias of `HttpClientOptions`).                         |
+| `createClientCredentialsTokenProvider`     | Builds a caching OAuth2 client-credentials token provider.                  |
+| `TokenProvider`, `ClientCredentialsConfig` | Auth types.                                                                 |
+| `paths`, generated request/response types  | Emitted from the OpenAPI spec.                                              |
+
+## Usage
+
+Every Clinia workspace requires authentication. Create OAuth credentials in the
+[Console](https://console.clinia.cloud) — scoped to your workspace, with **Read &
+Write** if you intend to ingest data or create patients — then point `baseUrl` at
+your workspace:
+
+```ts
+import { ContextEngineClient } from "@clinia/context-engine-js";
+
+const client = new ContextEngineClient({
+  baseUrl: "https://<workspace-id>.w.clinia.cloud",
+  auth: {
+    clientId: "your-client-id",
+    clientSecret: "your-client-secret",
+  },
+});
+
+const { data, error } = await client.http.GET("/v1/patients");
+```
+
+That is the whole configuration. The client resolves Clinia's authorization
+server, acquires a bearer token, caches it, refreshes it before expiry, and
+attaches `Authorization: Bearer <token>` to every request. Tokens last an hour;
+you do not manage them.
+
+The `http` client exposes the typed verbs directly, and the path, path params,
+query, and body are all checked against the OpenAPI contract:
+
+```ts
+await client.http.GET("/v1/patients/{patientId}/read", {
+  params: { path: { patientId: "abc" } },
+});
+```
+
+Responses are `{ data, error }` — nothing throws on a non-2xx.
+
+### Without authentication
+
+Omit `auth` entirely and the client sends no `Authorization` header. Useful
+against a server that does not require one — a stub or recorded fixture in your
+own tests:
+
+```ts
+const client = new ContextEngineClient({ baseUrl: "http://localhost:8000" });
+```
+
+An `http://` base URL is fine here. Note this is about the _client_ sending no
+credentials: a Clinia workspace always requires them, so pointing an
+unauthenticated client at one yields 401s on every request rather than a clear
+startup failure.
+
+### Bring your own token
+
+For a token you obtained elsewhere, a different grant, or a custom refresh
+strategy, pass `auth` a function instead of a config object. It is called per
+request and returns the token to attach:
+
+```ts
+const client = new ContextEngineClient({
+  baseUrl: "https://<workspace-id>.w.clinia.cloud",
+  auth: async () => myTokenStore.getValidAccessToken(),
+});
+```
+
+`createClientCredentialsTokenProvider` returns exactly such a function, so you can
+share one cached provider across several clients (or transports):
+
+```ts
+import {
+  ContextEngineClient,
+  createClientCredentialsTokenProvider,
+} from "@clinia/context-engine-js";
+
+const getAccessToken = createClientCredentialsTokenProvider({
+  clientId: "your-client-id",
+  clientSecret: "your-client-secret",
+});
+
+const client = new ContextEngineClient({ baseUrl, auth: getAccessToken });
+// The same provider can also feed a non-REST channel, e.g. an MCP transport.
+```
+
+### Middleware
+
+`http.use(...)` / `http.eject(...)` accept
+[`openapi-fetch` middleware](https://openapi-ts.dev/openapi-fetch/middleware-auth)
+for cross-cutting concerns (logging, tracing, custom headers). The `auth` option
+is implemented as such a middleware internally.
+
+## Options
+
+| Option    | Type                                                           | Description                                                                                        |
+| --------- | -------------------------------------------------------------- | -------------------------------------------------------------------------------------------------- |
+| `baseUrl` | `string`                                                       | Context Engine workspace base URL. Required.                                                       |
+| `fetch`   | `typeof fetch`                                                 | Custom fetch (also used for the token exchange). Defaults to global.                               |
+| `auth`    | `ClientCredentialsConfig \| (() => string \| Promise<string>)` | OAuth2 client-credentials config (common case) **or** a per-request token function (escape hatch). |
+
+## Development
+
+```sh
+pnpm generate   # regenerate types from ../../openapi/context-engine.yaml
+pnpm build      # bundle (tsup) + emit declarations (tsc)
+pnpm typecheck
+```
+
+Tests run from the repo root (Vitest discovers this package's `vitest.config.ts`):
+
+```sh
+pnpm test                                   # whole workspace
+pnpm vitest run --project context-engine-js # this package only
+```
+
+## License
+
+[Apache-2.0](LICENSE) © Clinia Health Inc.

package/dist/auth.d.ts

@@ -0,0 +1,90 @@
+/**
+ * OAuth2 client-credentials helpers for authenticating against a secured
+ * Context Engine workspace.
+ *
+ * The server validates a bearer JWT in the `Authorization` header against a
+ * JWKS. This module provides the client half: a token provider that exchanges
+ * a `client_id`/`client_secret` for an access token, caches it, and refreshes
+ * it before expiry. The token exchange itself is delegated to `oauth4webapi`
+ * (standards-compliant request building + response validation); this module
+ * only adds caching, concurrent-request de-duplication, and a small config
+ * surface. Pass the raw config as {@link HttpClientOptions.auth}, or — for full
+ * control — pass the returned provider as the {@link HttpClientOptions.auth}
+ * token function.
+ */
+/**
+ * Resolves to a currently-valid bearer access token. Called per request; a
+ * well-behaved provider caches internally and only hits the network when the
+ * cached token is missing or about to expire.
+ */
+export type TokenProvider = () => Promise<string>;
+/** Fields common to both ways of locating the authorization server. */
+type ClientCredentialsBase = {
+    clientId: string;
+    clientSecret: string;
+    /**
+     * Optional `resource` indicator (RFC 8707) naming the protected resource the
+     * token is for. This is what the Clinia authorization server expects (e.g.
+     * `https://console.clinia.cloud`).
+     */
+    resource?: string;
+    /** Optional `audience` parameter (used by some IdPs, e.g. Auth0). */
+    audience?: string;
+    /** Optional space-delimited `scope`. */
+    scope?: string;
+    /**
+     * How the client credentials are presented to the token endpoint. `post`
+     * (the default) sends them in the request body — what the Clinia
+     * authorization server expects; `basic` sends them in the `Authorization`
+     * header (RFC 6749 §2.3.1) for IdPs that require it.
+     */
+    authMethod?: "basic" | "post";
+    /**
+     * Custom fetch implementation. Defaults to `globalThis.fetch`. Useful for
+     * injecting a mock in tests.
+     */
+    fetch?: typeof globalThis.fetch;
+    /**
+     * Refresh the token this many milliseconds before it actually expires, to
+     * avoid handing out a token that expires mid-flight. Defaults to 60_000.
+     */
+    expiryMarginMs?: number;
+};
+/**
+ * Client-credentials configuration.
+ *
+ * For a Clinia workspace, `{ clientId, clientSecret }` is enough — the token
+ * endpoint and `resource` indicator default to Clinia's authorization server.
+ * Naming an {@link issuer} instead locates a different authorization server by
+ * OIDC/OAuth2 discovery; naming a {@link tokenUrl} points at one explicitly.
+ */
+export type ClientCredentialsConfig = (ClientCredentialsBase & {
+    /**
+     * Issuer identifier of the authorization server. Its metadata (token
+     * endpoint, etc.) is resolved via discovery on first use.
+     */
+    issuer: string;
+    /** Discovery transformation: `oidc` (default) or `oauth2` (RFC 8414). */
+    discoveryAlgorithm?: "oidc" | "oauth2";
+    tokenUrl?: never;
+}) | (ClientCredentialsBase & {
+    /**
+     * Explicit OAuth2 token endpoint; discovery is skipped. Omit it — along
+     * with `issuer` — to use Clinia's.
+     */
+    tokenUrl?: string;
+    /** Issuer identifier for response validation; defaults to the token URL's origin. */
+    issuer?: string;
+    discoveryAlgorithm?: never;
+});
+/**
+ * Builds a {@link TokenProvider} backed by the OAuth2 client-credentials grant.
+ *
+ * The provider caches the access token and reuses it until it is within
+ * `expiryMarginMs` of expiry. Concurrent calls while a fetch is in flight share
+ * the same request rather than each hitting the token endpoint. When configured
+ * with an {@link ClientCredentialsConfig.issuer}, the authorization server
+ * metadata is discovered once and memoized.
+ */
+export declare function createClientCredentialsTokenProvider(config: ClientCredentialsConfig): TokenProvider;
+export {};

package/dist/context-engine-client.d.ts

@@ -0,0 +1,14 @@
+import { HttpClient, type HttpClientOptions } from "./http-client";
+export type ContextEngineClientOptions = HttpClientOptions;
+/**
+ * Client for the Clinia Context Engine API.
+ *
+ * For now this client only exposes a low-level `http` client for making requests to the API. Higher-level resource methods can be added as the API surface stabilizes.
+ */
+export declare class ContextEngineClient {
+    /**
+     * Low-level http client. Use when a resource method does not cover your use case.
+     */
+    readonly http: HttpClient;
+    constructor(options: ContextEngineClientOptions);
+}