@grepr/cli 1.12.7 → 1.14.3-5fb972a

package/build/dist/docs-index/fe7b90fb-df65-470b-90f9-33666add9bbe.txt

@@ -1,229 +0,0 @@
-Connect Claude, Claude Code, Cursor, Codex, or ChatGPT to the Grepr MCP server with OAuth sign-in, or connect any MCP client with a service account token.
-
-# Connect to the Grepr MCP server
-
-Grepr provides a remote Model Context Protocol server, or MCP server, that lets AI assistants work with your Grepr organization. The server provides tools to list pipelines, browse datasets and templates, query logs, validate SQL and Grok rules, and propose pipeline changes. Every tool call is authorized with the same role-based permissions as the Grepr UI and REST APIs.
-
-The MCP server is available at the following endpoints:
-
-| Region | Endpoint |
-| --- | --- |
-| US | `https://app.grepr.ai/mcp` |
-| EU | `https://app.euc1.grepr.ai/mcp` |
-
-The examples on this page use the US endpoint. If your organization is in the EU region, replace the endpoint and use the EU client ID.
-
-You can authenticate in two ways:
-
-* OAuth sign-in: You sign in interactively with your Grepr user account. Use this for Claude, Claude Code, Cursor, Codex, and ChatGPT.
-* Service account credentials: Your client authenticates as a Grepr service account. Use this for Claude Tag in Slack, for automation, and for MCP clients that do not support the OAuth sign-in flow.
-
-## Sign in with OAuth
-
-Grepr registers a dedicated OAuth client for each supported MCP client. To connect, configure your MCP client with the Grepr endpoint and the matching client ID from the following table, then sign in with your Grepr user account. When the sign-in page prompts for an organization, enter your Grepr organization name.
-
-| MCP client | US client ID | EU client ID |
-| --- | --- | --- |
-| Claude | `us3sBOgZj6hERktG9yZEVwujaJe3j9L0` | `HOnxCPNGnzdGlfXBM2sff0twoolRnDj9` |
-| Claude Code | `jlCTdLYzDkkTSc2I7MdI0SBw48AOdJM6` | `GlEIcfSbge5gqN4o918fLXKVONP2twBh` |
-| Cursor | `ol2iI3MgbY4gDMT1SbCDQHj5OA8K4bAg` | `XHHImmxqr9EihBqVOettpLhS6CxDBhoB` |
-| Codex | `QPTtqmepPCvjvAs4rJHfBwXC4HklKefA` | `V0JSLGp1GmySuCj8tJPGqTXXMuP6unRx` |
-| ChatGPT | `R3rgytuEh03CzvNrasYj8R3eeAaYVcAP` | `7GCueSSV94VNsv2TkLGnWiWlyoS3DQrA` |
-
-### Claude
-
-These steps apply to Claude on the web, the Claude desktop apps, and the Claude mobile apps.
-
-1. In Claude, go to **Settings** > **Connectors** and click **Add custom connector**.
-2. Enter `https://app.grepr.ai/mcp` as the URL.
-3. Under **Advanced settings**, enter `us3sBOgZj6hERktG9yZEVwujaJe3j9L0` as the **OAuth Client ID**. Leave the client secret empty.
-4. Complete the sign-in flow with your Grepr user account.
-
-### Claude Code
-
-Add the server with the Grepr client ID and the fixed callback port:
-
-```bash
-claude mcp add --transport http --client-id jlCTdLYzDkkTSc2I7MdI0SBw48AOdJM6 --callback-port 6280 grepr https://app.grepr.ai/mcp
-```
-
-The `--callback-port 6280` flag is required. Without it, Claude Code picks a random port and the sign-in fails with a callback URL mismatch.
-
-Then open Claude Code, run `/mcp`, select `grepr`, and complete the sign-in flow in your browser with your Grepr user account.
-
-### Cursor
-
-Add the server with the Grepr client ID to `~/.cursor/mcp.json`, or to `.cursor/mcp.json` in a project:
-
-```json
-{
-  "mcpServers": {
-    "grepr": {
-      "url": "https://app.grepr.ai/mcp",
-      "auth": {
-        "CLIENT_ID": "ol2iI3MgbY4gDMT1SbCDQHj5OA8K4bAg"
-      }
-    }
-  }
-}
-```
-
-The `auth` block with `CLIENT_ID` is required. Without it, Cursor tries dynamic client registration, which Grepr does not support, and the sign-in fails. Do not add a client secret. Cursor uses fixed callback URLs that Grepr registers, so you do not need to set a callback port.
-
-Save the file and restart Cursor. The `grepr` server shows in **Customize** > **MCPs**. When Cursor prompts you to sign in, complete the sign-in flow in your browser with your Grepr user account.
-
-### Codex
-
-Add the server with the Grepr client ID and the fixed callback port to `~/.codex/config.toml`:
-
-```toml
-[mcp_servers.grepr]
-url = "https://app.grepr.ai/mcp"
-
-[mcp_servers.grepr.oauth]
-client_id = "QPTtqmepPCvjvAs4rJHfBwXC4HklKefA"
-callback_port = 6280
-```
-
-The `callback_port = 6280` setting is required. Without it, Codex picks a random port and the sign-in fails with a callback URL mismatch. Use the endpoint for your region exactly as the endpoint table writes it, with no trailing slash, because Codex builds its callback URL from the endpoint URL.
-
-Then sign in:
-
-```bash
-codex mcp login grepr
-```
-
-Complete the sign-in flow in your browser with your Grepr user account.
-
-### ChatGPT
-
-Your ChatGPT plan or workspace settings must allow custom MCP servers.
-
-1. In ChatGPT, go to **Plugins**, click **Add**, and select **Add custom MCP server**.
-2. Enter a name such as `Grepr`, and enter `https://app.grepr.ai/mcp` as the **Server URL**. Enter the endpoint for your region exactly as the endpoint table writes it, because ChatGPT builds its callback URL from it. Keep **OAuth** as the **Authentication**.
-3. Open **Advanced OAuth settings** and keep **User-Defined OAuth Client** as the **Registration method**. Enter `R3rgytuEh03CzvNrasYj8R3eeAaYVcAP` as the **OAuth client ID**, leave the client secret empty, and keep `none` as the **Token endpoint auth method**.
-4. Select **I understand and want to continue** and click **Create as a plugin**.
-5. When ChatGPT prompts you to sign in, complete the sign-in flow with your Grepr user account.
-
-## Connect Claude Tag in Slack
-
-Claude Tag is Claude in Slack channels. In a channel, Claude acts as a shared identity that an Owner of your Claude organization configures, not as the person who sends the message. Everyone in a channel that the configuration covers gets the same Grepr access, so connect a dedicated Grepr service account with the narrowest role that fits the channel. Direct messages with Claude in Slack run on your own Claude account and use the Claude connector described earlier on this page.
-
-Before you start, you need:
-
-* The Owner role in your Claude organization. Claude Tag is available on the Claude Team and Enterprise plans.
-* A Grepr service account and its client ID and client secret. See [Manage Grepr service accounts](/admin/service-accounts).
-* The Grepr plugin for Claude Tag: [grepr-claude-tag-plugin.zip](/plugins/grepr-claude-tag-plugin.zip). Claude Tag reaches an MCP server only through a plugin. The plugin contains two files: a manifest, and an `.mcp.json` file that names the US and EU Grepr MCP endpoints.
-
-### Upload the plugin
-
-1. In Claude, go to **Admin settings** > **Plugins** and click **Add plugins**.
-2. Select **Upload a file** and upload `grepr-claude-tag-plugin.zip`.
-
-The plugin is now in your organization's catalog. It does nothing until you turn it on in an access bundle.
-
-### Turn on the plugin and add the credential
-
-An access bundle is the set of credentials and plugins that Claude uses in the channels the bundle covers. The **Default Slack** scope covers every channel in your Slack workspace. To limit Grepr access to one channel, select that channel's scope instead.
-
-1. Go to **Admin settings** > **Claude Tag** and, under **Claude Tag's access**, select the **Slack** tab.
-
-2. Select the **Default Slack** scope, or the channel to connect.
-
-3. Next to **Access bundles**, click the **+** button and select **Create new bundle**, or open the existing bundle.
-
-4. On the **Plugins** tab, turn on **grepr-mcp**.
-
-5. On the **Credentials** tab, click **Connect** next to **Custom tool** and enter the following values:
-
-   \| Field | Value | | --- | --- | | Name | `Grepr` | | Credential type | **OAuth 2.0 client credentials** | | Token URL | `https://auth.grepr.ai/oauth/token`, or `https://auth.eu.grepr.ai/oauth/token` for the EU region | | Client ID | The service account client ID | | Client secret | The service account client secret | | Audience | `service` | | Allowed websites | `app.grepr.ai`, or `app.euc1.grepr.ai` for the EU region |
-
-6. Save the connection and confirm that its status is **Active** on the **Access bundles** page.
-
-> A bundle on a public channel gives its access to anyone who joins the channel. Keep a service account with edit permissions in a bundle on a private channel.
-
-### Test the connection
-
-In a channel the bundle covers, start a new thread and send:
-
-```text
-@Claude list the Grepr pipelines
-```
-
-Threads that started before you turned on the plugin do not pick it up. If Claude reports that a host was blocked by the network egress proxy, add the host it names to the **Allowed websites** of the Grepr connection.
-
-## Authenticate with a service account token
-
-For automation, and for MCP clients that are not in the table and do not support OAuth 2.0 client credentials, authenticate with a service account access token. The MCP endpoint accepts the same access tokens as the Grepr REST APIs.
-
-1. Create a service account. See [Manage Grepr service accounts](/admin/service-accounts).
-
-2. Obtain an access token. See [Authenticate to Grepr REST APIs](/apis/authentication).
-
-3. Configure your MCP client to send the token in the `Authorization` header. Most clients accept a headers object in their MCP server configuration:
-
-   ```json
-   {
-     "headers": {
-       "Authorization": "Bearer <access-token>"
-     }
-   }
-   ```
-
-> The access token expires after 24 hours and has no refresh token, so your client cannot renew it automatically. When the token expires, obtain a new token and update your client configuration. For scheduled automation, obtain a new token at the start of each run.
-
-## Use Grepr skills through the MCP server \[#skills]
-
-The MCP server also provides *skills*: instructions that teach an AI assistant how to work with Grepr efficiently. The server lists each skill in the instructions it sends when your client connects, and serves each skill's files as MCP resources at `skill://<skill-name>/SKILL.md`. MCP clients that read resources, such as Claude Code, load a skill when your request matches it.
-
-The server provides the following skills:
-
-* `cli`: Installs, configures, and signs in to the Grepr CLI, and points to the other Grepr skills.
-* `query`: Queries logs and spans with the Grepr CLI, scoped so that each query reads as little data as possible.
-* `query-predicate`: Translates a request into a Grepr query predicate.
-* `recover-reduced-logs`: Explains the summary logs that Grepr sends to your observability vendor in place of repeated logs, and finds the original logs behind a summary in the Grepr data lake.
-* `backfill-logs`: Sends original logs from the Grepr data lake to your observability vendor.
-
-When your AI assistant can run shell commands, the skills use the Grepr CLI instead of the MCP tools, because the CLI writes results to a file and has no page limit. To install the CLI, see [Grepr CLI](/cli). The [coding assistant plugins](/cli#agent-skills) include these skills and the rest of the Grepr skills.
-
-## Frequently Asked Questions
-
-### Does the Grepr MCP server provide skills?
-
-Yes. The server lists its skills in the instructions it sends when a client connects and serves each skill as an MCP resource at skill://\<skill-name>/SKILL.md. The skills cover setting up the Grepr CLI, querying logs and spans, building query predicates, recovering the original logs behind a Grepr summary, and backfilling logs to your observability vendor.
-
-### What is the Grepr MCP server URL?
-
-The MCP endpoint is https\://app.grepr.ai/mcp for the US region and https\://app.euc1.grepr.ai/mcp for the EU region.
-
-### How do I connect Claude to Grepr?
-
-Add a custom connector in Claude with the URL https\://app.grepr.ai/mcp, and enter the Grepr client ID for Claude under Advanced settings. Then sign in with your Grepr user account.
-
-### How do I connect Cursor to Grepr?
-
-Add the server to your Cursor mcp.json file with the URL https\://app.grepr.ai/mcp and an auth block that contains the Grepr client ID for Cursor. Then restart Cursor and, when it prompts you, sign in with your Grepr user account.
-
-### How do I connect Codex to Grepr?
-
-Add the server to your Codex config.toml file with the URL https\://app.grepr.ai/mcp, the Grepr client ID for Codex, and callback_port = 6280. Then run codex mcp login grepr and sign in with your Grepr user account.
-
-### How do I connect ChatGPT to Grepr?
-
-Add a custom MCP server in ChatGPT with the URL https\://app.grepr.ai/mcp and OAuth authentication. Under Advanced OAuth settings, keep User-Defined OAuth Client as the registration method and enter the Grepr client ID for ChatGPT. Then sign in with your Grepr user account.
-
-### Why does the MCP sign-in fail with a callback URL mismatch?
-
-Grepr registers exact OAuth callback URLs. Claude Code and Codex must use port 6280. In Claude Code, set it with the --callback-port 6280 flag. In Codex, set callback_port = 6280 in config.toml. Cursor and ChatGPT use callback URLs that Grepr registers, so they need no callback setting. Codex and ChatGPT build the callback URL from the server URL, so enter the endpoint for your region exactly as the endpoint table writes it.
-
-### Can I use the Grepr MCP server without OAuth?
-
-Yes. The MCP endpoint accepts the same service account access tokens as the Grepr REST APIs. Send the token in the Authorization header as a Bearer token.
-
-### Can I use Grepr from Claude in Slack?
-
-Yes. Upload the Grepr plugin for Claude Tag, turn it on in an access bundle, and add an OAuth 2.0 client credentials connection for app.grepr.ai with a Grepr service account, the token URL https\://auth.grepr.ai/oauth/token, and the audience service.
-
-### Which organization does an MCP session use?
-
-The organization you enter at sign-in, or the organization of the service account that issued the token. The MCP session is scoped to that organization.

package/build/dist/docs-index/fec0fad7-e3c6-4a66-b6b2-f5d97a9056b8.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/fec0fad7-e3c6-4a66-b6b2-f5d97a9056b8.txt

@@ -1,23 +0,0 @@
-# PromotedAttribute
-
-Attribute paths the table indexes, with the policy applied to each.
-
-**Type**: `object`
-
-## Properties
-
-- name: excluded (required)
-  type: boolean
-  description: Whether the stored policy leaves this path's columns NULL.
-
-- name: numeric (required)
-  type: boolean
-  description: Whether the path also has an n_ numeric index column.
-
-- name: path (required)
-  type: string
-  description: The attribute path this column indexes.
-
-- name: valueColumn (required)
-  type: string
-  description: The a_ value index column for the path.

package/build/dist/docs-index/fecf5d2c-23a5-4dba-a804-509f579256ff.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/fecf5d2c-23a5-4dba-a804-509f579256ff.txt

@@ -1,43 +0,0 @@
-# Replace a dataset table promotion policy
-
-**PUT** `/v1/datasets/{id}/tables/{tableKey}/promotion`
-
-**Operation ID**: `putTablePromotion`
-**Summary**: Replace a dataset table promotion policy
-Validates and stores the complete promotion policy on the table. Newly included tag columns, and the columns of exact attribute includes the attribute cap has room for, are added synchronously before the request returns, in the same commit as the policy. Send back the revision the policy was read at to be refused rather than overwrite a change made since; omit it to replace whatever is stored.
-
-## Tags
-- Datasets
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-- **tableKey** (required) - path
-  - Type: string
-
-## Request Body
-
-The complete promotion policy document. It is decoded by the same strict codec that reads the stored policy: every field is typed exactly, no unknown field is accepted at any depth, and no value is coerced. It replaces the stored policy rather than patching it, and both groups are required -- a body that omits "tags" or "attributes" is rejected, not read as a request to stop discovery for that group. The cap is the switch: send a group with "cap": 0 to stop it promoting fields it has not seen before, which for attributes includes the paths it includes. That does not blank the group -- the columns the table already carries keep being written. A field is stopped by naming it in that group's exclude list, or, for attributes, by setting "excludeAllByDefault", which stops every path the include list does not cover. Read the current policy and send it back whole, changing only what you mean to change.
-
-**Content-Type**: `application/json`
-
-**Schema**: `PromotionPolicy`
-
-## Responses
-
-### 200
-
-The persisted promotion policy.
-
-- **Content-Type**: `application/json` / `PromotionPolicy`
-### 400
-
-Invalid promotion policy.
-
-### 404
-
-Dataset or table not found.
-
-### 409
-
-The policy changed since the revision the request was made against; read it again and reapply the change. Or the table kept changing under the request, which a running writer's own evolution can cause; retry.

package/build/dist/docs-index/fee64942-b6fb-436a-9b9f-78d0082ff75c.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/fee64942-b6fb-436a-9b9f-78d0082ff75c.txt

@@ -1,30 +0,0 @@
-# Removes a user from the team
-
-**DELETE** `/v1/teams/{id}/users/{userId}`
-
-**Operation ID**: `removeUserFromTeam`
-**Summary**: Removes a user from the team
-Remove a user from the team.
-
-## Tags
-- Teams
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-- **userId** (required) - path
-  - Type: string
-
-## Responses
-
-### 204
-
-User removed from team successfully
-
-### 401
-
-Unauthorized
-
-### 404
-
-Not Found

package/build/dist/docs-index/ff139441-9190-45ec-99e6-a95e1c28fc2d.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/ff139441-9190-45ec-99e6-a95e1c28fc2d.txt

@@ -1,18 +0,0 @@
-# ExceptionUsageResponse
-
-Usage the vendor reports for an integration's parsed queries
-
-**Type**: `object`
-
-## Properties
-
-- name: reportedTypes (required)
-  type: array of string
-  description: The parsed query exception types (values of a parsed query's exceptionType) the vendor reports usage for. Empty when the vendor reports none; a query of any other type has no usage to show.
-
-- name: status (required)
-  type: `UsageStatus`
-
-- name: usage (required)
-  type: object
-  description: Usage keyed by composite exception id (integrationId:vendorResourceId:exceptionType), the key the impacts endpoint uses. A query the vendor reported nothing for is absent, which is not the same as never viewed.

package/build/dist/docs-index/ff425978-9e7b-4349-a841-bf9e0d6556ee.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/ff425978-9e7b-4349-a841-bf9e0d6556ee.txt

@@ -1,39 +0,0 @@
-# Update a webhook integration
-
-**PUT** `/v1/integrations/webhooks/{id}`
-
-**Operation ID**: `update_11`
-**Summary**: Update a webhook integration
-Updates a webhook integration. The version should be increased by one for every new update in order for the write to succeed. Otherwise, a '409 Conflict' will be returned.
-
-## Tags
-- Webhook Integration
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-
-## Request Body
-
-**Content-Type**: `application/json`
-
-**Schema**: `WriteWebhookIntegration`
-
-## Responses
-
-### 200
-
-Integration updated successfully
-
-- **Content-Type**: `application/json` / `ReadWebhookIntegration`
-### 401
-
-Unauthorized
-
-### 404
-
-Integration not found.
-
-### 409
-
-Integration was modified or deleted concurrently.

package/build/dist/docs-index/ff5891aa-d054-4e00-90a3-ce9d45f486dc.json

@@ -1 +0,0 @@
-{"docType":"schema"}

package/build/dist/docs-index/ff5891aa-d054-4e00-90a3-ce9d45f486dc.txt

@@ -1,11 +0,0 @@
-# ErrorDetails
-
-**Type**: `object`
-
-## Properties
-
-- name: exception (optional)
-  type: string
-
-- name: message (optional)
-  type: string

package/build/dist/docs-index/ff5927e0-5dee-4891-8821-0d764331fca4.json

@@ -1 +0,0 @@
-{"docType":"doc"}

package/build/dist/docs-index/ff5927e0-5dee-4891-8821-0d764331fca4.txt

@@ -1,73 +0,0 @@
-Automate Grepr data processing with REST APIs for job management, authentication, rule engine control, and job lifecycle tracking.
-
-# Automate Grepr processing with the Grepr REST APIs
-
-The Grepr REST APIs provide programmatic access to create and manage data processing jobs, configure authentication, control rule engines, and monitor job lifecycles. These APIs enable you to automate observability pipelines, integrate Grepr into existing workflows, and build custom applications that process log data at scale. All APIs follow REST conventions, return JSON responses, and require HTTPS authentication.
-
-For documentation of the endpoints in the Grepr REST API, see the [OpenAPI 3.0 specification](/apis/api-spec).
-
-## Authenticate to Grepr REST APIs
-
-Learn how to obtain and use access tokens for Grepr API authentication. This page covers the OAuth 2.0 client credentials flow using Auth0, including how to request credentials from Grepr support, obtain access tokens, and include Bearer tokens in API requests. The authentication system uses organization-specific client IDs and secrets to generate time-limited access tokens that provide access to all Grepr APIs.
-
-See [Authenticate to Grepr REST APIs](/apis/authentication).
-
-## Create and manage Grepr jobs
-
-Comprehensive guide for creating and managing Grepr processing jobs through the REST API. This page covers both synchronous and asynchronous job execution modes, batch and streaming processing types, and how to construct job graphs with vertices and edges. Learn how to submit jobs, poll for status updates, handle job versioning, and implement best practices for production deployments.
-
-See [Create and manage jobs with the Grepr REST API](/apis/job-creation-guide).
-
-## Track the lifecycle of Grepr jobs
-
-Detailed documentation of job lifecycle management and state transitions for Grepr processing jobs. This page explains the different states that jobs can enter during creation, updates, and deletion, including pending, running, stopped, and failed states. Learn how to monitor job health, understand state diagrams for different job types, and handle job rollbacks and version management.
-
-See [Track the lifecycle of jobs with the Grepr REST API](/apis/job-states).
-
-## Use conditions and triggers to control log processing
-
-API documentation for configuring and managing Grepr's rule engine to dynamically control log processing based on defined conditions and triggers. This page covers how to create event-based triggers, configure conditional actions, and implement automated responses to log events. Use the rule engine to implement incident response workflows, dynamic log filtering, and context-aware processing rules.
-
-See [Control log processing with the rule engine REST API](/apis/rule-engine).
-
-## Frequently Asked Questions
-
-### How do I authenticate to Grepr REST APIs?
-
-Grepr uses OAuth 2.0 client credentials flow with Auth0. You need to request API credentials from Grepr support, then use those credentials to obtain access tokens. Include the Bearer token in the Authorization header of API requests.
-
-### What types of jobs can I create with the Grepr API?
-
-The Grepr API supports creating ASYNCHRONOUS STREAMING jobs (long-running pipelines), ASYNCHRONOUS BATCH jobs (short-lived queries on scoped data), and SYNCHRONOUS BATCH jobs (real-time queries that stream results back to the client).
-
-### How do I monitor the status of a job I submitted via API?
-
-Use the GET /jobs endpoint to retrieve job details including the state field, which indicates the current lifecycle state of the job (PENDING, RUNNING, STOPPED, FAILED, FINISHED, etc.). Poll this endpoint to track state transitions.
-
-### Can I update a job after it's running?
-
-Yes, you can submit job updates via API. Updates are versioned, so Grepr maintains the old version while deploying the new version. You can also specify rollbackEnabled to automatically rollback to the previous version if the update fails.
-
-### What are the benefits of using asynchronous job execution?
-
-Asynchronous jobs return a 202 Accepted response immediately and allow you to poll for status updates. This is ideal for long-running processes and allows your application to remain responsive while the job executes in the background.
-
-### How do I delete a job via API?
-
-Submit a DELETE request to the jobs endpoint with the job ID. The job will transition through a deletion lifecycle with states like PENDING_DELETE and FINISHED to ensure a clean shutdown.
-
-### What is a job graph and how do I construct one?
-
-A job graph is a JSON structure that defines the data processing pipeline with vertices (operations like source, sink, grok parsing) and edges (connections between operations). Each vertex has a name, type, and configuration specific to that operation type.
-
-### Can I use the rule engine to trigger automated actions?
-
-Yes, the rule engine supports event-based triggers, conditions, and actions. You can configure the engine to automatically execute backfill jobs, modify log tags, or take other actions when specified conditions are met.
-
-### How do I handle job failures detected via API?
-
-Monitor the job state field in API responses. If a job enters the FAILED state, check the job details for error information. You can then resubmit the job with corrected configuration or use the rollback feature if an update caused the failure.
-
-### What API rate limits should I be aware of?
-
-Consult the OpenAPI 3.0 specification at /apis/api-spec for detailed information about rate limits, required headers, and API behavior. Each endpoint has specific constraints documented in the specification.

package/build/dist/docs-index/ff878bd8-48be-43a6-8fb1-5dd2a60c7d3e.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/ff878bd8-48be-43a6-8fb1-5dd2a60c7d3e.txt

@@ -1,26 +0,0 @@
-# Get dataset impact estimation configuration
-
-**GET** `/v1/datasets/{id}/estimation-config`
-
-**Operation ID**: `getDatasetEstimationConfig`
-**Summary**: Get dataset impact estimation configuration
-Returns the impact-estimation configuration for the dataset, or null when the dataset is not opted in for estimation. The presence of a configuration is the per-dataset opt-in for impact estimation.
-
-## Tags
-- Datasets
-## Parameters
-
-- **id** (required) - path
-  - Dataset ID to get configuration for
-  - Type: string
-
-## Responses
-
-### 200
-
-Configuration retrieved, or null if the dataset is not opted in
-
-- **Content-Type**: `application/json` / `DatasetEstimationConfig`
-### 404
-
-Dataset not found.

package/build/dist/docs-index/ffa49cd7-774f-40c3-aa82-1565e85922c5.json

@@ -1 +0,0 @@
-{"docType":"api"}

package/build/dist/docs-index/ffa49cd7-774f-40c3-aa82-1565e85922c5.txt

@@ -1,31 +0,0 @@
-# Get a dataset table config
-
-**GET** `/v1/datasets/{id}/{tableKey}/config`
-
-**Operation ID**: `getTableConfig`
-**Summary**: Get a dataset table config
-Returns the configuration for one of the dataset's tables (e.g. logs_raw), including the system-controlled effective partition spec. Without an override, the spec's editable rows are the table's defaults.
-
-## Tags
-- Datasets
-## Parameters
-
-- **id** (required) - path
-  - Type: string
-- **tableKey** (required) - path
-  - Type: string
-
-## Responses
-
-### 200
-
-The table config, with effectiveSpec always populated.
-
-- **Content-Type**: `application/json` / `TableConfigRead`
-### 400
-
-Unsupported table key.
-
-### 404
-
-Dataset not found.

package/build/dist/lib/transformers-embeddings.d.ts

@@ -1,76 +0,0 @@
-import { EmbeddingsModel, EmbeddingsResponse } from 'vectra';
-/**
- * Embeddings provider for Vectra using Transformers.js.
- *
- * This class implements Vectra's EmbeddingsModel interface using Transformers.js,
- * a pure JavaScript implementation of transformer models. This approach provides:
- * - Zero external dependencies (no Docker, no server startup)
- * - Automatic model caching (~90MB downloaded once, reused thereafter)
- * - Cross-platform compatibility (works on any Node.js environment)
- *
- * The model generates dense vector embeddings for text, enabling semantic similarity
- * search. The embeddings are generated using mean pooling and normalization, which
- * is standard for sentence similarity tasks.
- *
- * Design decision: We chose Transformers.js over alternatives like Ollama because:
- * 1. No runtime server dependency (Ollama requires Docker container)
- * 2. Faster startup time (no container initialization)
- * 3. Smaller distribution size (model cached by npm, not bundled)
- * 4. Better integration with Node.js ecosystem
- */
-export declare class TransformersEmbeddings implements EmbeddingsModel {
-    private pipeline;
-    /**
-     * Maximum number of tokens the model can process per input.
-     * This is exposed publicly so Vectra can use it for chunking decisions.
-     */
-    readonly maxTokens: number;
-    private readonly modelName;
-    /**
-     * Creates a new TransformersEmbeddings instance.
-     *
-     * @param modelName - HuggingFace model identifier (e.g., 'Xenova/all-MiniLM-L6-v2')
-     *                    Default model produces 384-dimensional embeddings and is ~90MB.
-     *                    See https://huggingface.co/models?library=transformers.js&pipeline_tag=feature-extraction
-     *                    for other compatible models.
-     * @param maxTokens - Maximum tokens per input. Should match model's configuration.
-     *                    Used by Vectra for automatic document chunking.
-     */
-    constructor(modelName?: string, maxTokens?: number);
-    /**
-     * Initializes the embedding model pipeline.
-     *
-     * This method is lazy - it only loads the model when first called. The model
-     * is downloaded from HuggingFace on first run and cached locally by Transformers.js
-     * in ~/.cache/huggingface/ (or platform equivalent).
-     *
-     * Subsequent calls to this method are no-ops if the pipeline is already initialized.
-     *
-     * @throws Error if model download or initialization fails (e.g., network issues,
-     *         unsupported model architecture)
-     */
-    initialize(): Promise<void>;
-    /**
-     * Generates vector embeddings for one or more text inputs.
-     *
-     * This is the main method called by Vectra to generate embeddings for documents
-     * and queries. The implementation:
-     * 1. Initializes the pipeline if not already initialized (lazy loading)
-     * 2. Normalizes input to always be an array
-     * 3. Generates embeddings for each input sequentially
-     * 4. Returns embeddings as a 2D array of numbers
-     *
-     * Important: We use mean pooling and normalization for the embeddings. This is
-     * standard practice for sentence similarity tasks:
-     * - Mean pooling: Averages token embeddings to get a single vector per sentence
-     * - Normalization: Scales vectors to unit length, enabling cosine similarity
-     *                   via simple dot product
-     *
-     * @param inputs - Single text string or array of strings to embed
-     * @returns Promise resolving to EmbeddingsResponse with either:
-     *          - success status and array of embedding vectors
-     *          - error status and error message
-     */
-    createEmbeddings(inputs: string | string[]): Promise<EmbeddingsResponse>;
-}
-//# sourceMappingURL=transformers-embeddings.d.ts.map

package/build/dist/lib/transformers-embeddings.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"transformers-embeddings.d.ts","sourceRoot":"","sources":["../../../src/main/typescript/lib/transformers-embeddings.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,eAAe,EAAE,kBAAkB,EAAE,MAAM,QAAQ,CAAC;AAgB7D;;;;;;;;;;;;;;;;;;GAkBG;AACH,qBAAa,sBAAuB,YAAW,eAAe;IAC5D,OAAO,CAAC,QAAQ,CAA0C;IAE1D;;;OAGG;IACH,SAAgB,SAAS,EAAE,MAAM,CAAC;IAElC,OAAO,CAAC,QAAQ,CAAC,SAAS,CAAS;IAEnC;;;;;;;;;OASG;gBACS,SAAS,SAA4B,EAAE,SAAS,SAAM;IAKlE;;;;;;;;;;;OAWG;IACG,UAAU,IAAI,OAAO,CAAC,IAAI,CAAC;IAMjC;;;;;;;;;;;;;;;;;;;;OAoBG;IACG,gBAAgB,CAAC,MAAM,EAAE,MAAM,GAAG,MAAM,EAAE,GAAG,OAAO,CAAC,kBAAkB,CAAC;CA8B/E"}