@zackbart/connecta 0.29.0 → 0.31.0

package/dist/providers/notion/skill.generated.js

@@ -1,10 +1,11 @@
 // Generated by scripts/generate-providers.mjs; do not edit.
 export const skill = {
-    "content": "\n## Identity before routing\n\nThis explicit `surface: \"api\"` connection acts as an internal integration.\nIts `integration_*` tools are canonical for bot-scoped/headless operations.\nHosted MCP is the default and acts as its OAuth-authorized user. Authorization\nis not equivalent: an integration token cannot authorize hosted MCP, and user\nOAuth cannot reproduce the integration bot's ownership/sharing boundary.\nConfigure each under a separate connector id and authorize it independently.\nDo not switch to a user identity to recover a failed integration operation.\n\nUse the bot tools when the task requires that integration identity. Use hosted\n`notion-search`, `notion-fetch`, `notion-get-users`, `notion-get-comments`,\n`notion-create-pages`, `notion-update-page`, and `notion-create-comment` for\nuser-owned content work. Hosted MCP additionally covers sessions, agents,\nattachments and broader workspace operations. REST tool names are not MCP aliases.\n\n\n\n## Databases contain data sources\n\nA Notion database is a container; the rows and the schema live in a *data\nsource* inside it. The two ids are not interchangeable and Notion rejects the\nwrong one.\n\n- The id in a Notion database URL is a **database id**.\n- `integration_get_database` turns it into the `data_sources` list — usually one entry.\n- `integration_get_data_source_schema` and `integration_query_data_source` take that\n  **data_source_id**, and so does `integration_create_page` when adding a row.\n\nSo the sequence for \"find rows in this database\" is `integration_get_database` →\n`integration_get_data_source_schema` → `integration_query_data_source`. `integration_search` returns data\nsources directly and skips the first step.\n\n## Property quirks that break writes\n\n- Property names in filters, sorts, and writes must match the schema exactly,\n  including case. Read `integration_get_data_source_schema` before composing one.\n- `select` and `status` writes must use an existing option name; inventing\n  one fails. The schema lists the valid options.\n- Writes **replace** a property. Sending one item to a `multi_select` or\n  `relation` drops the others, so send the complete intended value.\n- `rollup`, `formula`, `unique_id`, and the created/edited fields are\n  computed. They cannot be written.\n- A page's title column is rarely called \"title\" — pass `title_property` from\n  the schema when creating or updating a row.\n- Notion truncates `title`, `rich_text`, `relation`, and `people` at 25\n  entries. `integration_get_page` reports each one in `truncated_properties` as\n  `{ name, id }`; pass that `id` as `property_id` to\n  `integration_get_page_property` for the complete value.\n\n## Reading page content\n\n`integration_get_page` returns properties. `integration_get_page_content` returns the body as flat\nblocks. Nested blocks (toggles, list children, table rows) need `depth`, and\neach level multiplies requests — a deep read stops at an internal ceiling and\nreports `truncated: true` rather than spending the whole rate-limit budget.\n\n## Appending is append-only\n\n`integration_append_blocks` adds children and nothing else. It cannot move, reorder, or\nreplace an existing block, and a block appended through the API can never be\nrelocated by it afterwards. Get the position right the first time with\n`position` and `after_block_id`. Notion caps one call at 100 blocks.\n\n## Lean by default, raw on request\n\nEvery read projects Notion's payload down to ids, plain text, and flattened\nproperty values. Where the dropped detail can matter — `integration_search`, `integration_get_page`,\n`integration_get_page_content`, `integration_get_page_property`, `integration_get_data_source_schema`,\n`integration_query_data_source`, `integration_list_comments` — pass `raw: true` to get Notion's\nuntouched response instead. It is much larger; reach for it only when a\nspecific field is missing. Narrow `integration_query_data_source` and `integration_get_page` with\n`properties` instead whenever the goal is fewer fields, not more.\n\n`integration_get_page_content` with `raw: true` returns one level exactly as Notion\nsent it and does not walk nested children, so `depth` is ignored alongside\nit. A block type this projection does not model keeps its payload under\n`raw` on the block itself, so nothing silently flattens to an empty string.\n\n## Failures worth reading carefully\n\n- **404** means \"no such object\" *or* \"not shared with this integration\", and\n  Notion will not say which. Never conclude a page was deleted from it; check\n  that the page is shared with the integration in Notion.\n- **403** is not an expired token. The integration is missing a capability\n  (comment capabilities are off by default) or the object was never shared.\n  Re-authorizing cannot fix it; an operator must change it in Notion.\n- **429** carries a retry window. Notion allows roughly three requests per\n  second per integration, so wait it out rather than retrying immediately.\n\n## No escape hatch\n\nThis connection has no guarded raw-REST tool, deliberately. Notion's public\nAPI is small and slow-moving enough for the named surface to cover it, so\nthere is no `notion_api_*` to reach for — an operation absent from the tool\nlist is absent from this connection, not hidden behind a generic call.\n\n## Writes and pagination\n\n- Notion has **no idempotency key**. A retried `integration_create_page` or\n  `integration_add_comment` creates a duplicate. Confirm with `integration_search` before repeating\n  a write that may have partially succeeded.\n- List tools take `page_size` (max 100) and return `has_more` with\n  `next_cursor`. Pass a cursor back verbatim — it is opaque and must never be\n  parsed or constructed. Follow pages inside `execute_code` and reduce there.\n# Notion MCP usage\n\nOfficial MCP interface: tool names, descriptions, argument schemas, and result\nschemas come from Notion's live server. Connecta preserves that catalog and\napplies release-reviewed classification. Reviewed writes stay writes even when Notion claims they only read.\n\nWorkspace purpose: \n\n- This connection acts as its OAuth-authorized user. The separately configured\n  `surface: \"api\"` connection retains required internal-integration operations\n  under `integration_*` names, including headless content writes, cursor-complete\n  queries, exact JSON blocks and property items. No identity fallback occurs.\n- Discover the live catalog before assuming a tool exists. Notion can gate\n  tools by workspace, account, client, and rollout independently of Connecta.\n- Start broad discovery with `notion-search`, then use `notion-fetch` on\n  the exact page, database, data source, or object before changing it.\n- Use the live input schema as the contract. Notion owns these MCP schemas;\n  the REST schemas in Connecta's API interface do not apply to MCP tools with\n  similar names.\n- Session and agent tools can launch asynchronous work. Read session state and\n  events before sending another message, waiting, or stopping a session.\n- File uploads and attachment tools create durable workspace state. Keep\n  downloads inside the requested task and do not expose signed attachment URLs.\n- An `auth_required` failure means this connector's OAuth grant is missing or\n  expired. Run `authorize_connector` for this connector id, then retry.\n",
+    "content": "\n## Notion's data model\n\n- A database is a container; its rows and schema live in a *data source*\n  inside it. Queries, schema reads, and new rows take the data source, and\n  Notion rejects a database id in its place.\n- Property names in filters, sorts, and writes must match the schema exactly,\n  including case. Read the schema before composing one.\n- `select` and `status` writes must use an existing option name; inventing\n  one fails. The schema lists the valid options.\n- Writes **replace** a property. Sending one item to a `multi_select` or\n  `relation` drops the others, so send the complete intended value.\n- `rollup`, `formula`, `unique_id`, and the created and edited fields are\n  computed. They cannot be written.\n- A data source's title column is rarely called \"title\". Read its name from\n  the schema before creating or renaming a row.\n- Notion has **no idempotency key**. A retried page create or comment makes a\n  duplicate. Confirm with a search before repeating a write that may have\n  partially succeeded.\n",
     "instructionsHeading": "Workspace instructions",
     "fragments": {
-        "guide_0": "\n## Identity before routing\n\nThis explicit `surface: \"api\"` connection acts as an internal integration.\nIts `integration_*` tools are canonical for bot-scoped/headless operations.\nHosted MCP is the default and acts as its OAuth-authorized user. Authorization\nis not equivalent: an integration token cannot authorize hosted MCP, and user\nOAuth cannot reproduce the integration bot's ownership/sharing boundary.\nConfigure each under a separate connector id and authorize it independently.\nDo not switch to a user identity to recover a failed integration operation.\n\nUse the bot tools when the task requires that integration identity. Use hosted\n`notion-search`, `notion-fetch`, `notion-get-users`, `notion-get-comments`,\n`notion-create-pages`, `notion-update-page`, and `notion-create-comment` for\nuser-owned content work. Hosted MCP additionally covers sessions, agents,\nattachments and broader workspace operations. REST tool names are not MCP aliases.\n\n\n\n## Databases contain data sources\n\nA Notion database is a container; the rows and the schema live in a *data\nsource* inside it. The two ids are not interchangeable and Notion rejects the\nwrong one.\n\n- The id in a Notion database URL is a **database id**.\n- `integration_get_database` turns it into the `data_sources` list — usually one entry.\n- `integration_get_data_source_schema` and `integration_query_data_source` take that\n  **data_source_id**, and so does `integration_create_page` when adding a row.\n\nSo the sequence for \"find rows in this database\" is `integration_get_database` →\n`integration_get_data_source_schema` → `integration_query_data_source`. `integration_search` returns data\nsources directly and skips the first step.\n\n## Property quirks that break writes\n\n- Property names in filters, sorts, and writes must match the schema exactly,\n  including case. Read `integration_get_data_source_schema` before composing one.\n- `select` and `status` writes must use an existing option name; inventing\n  one fails. The schema lists the valid options.\n- Writes **replace** a property. Sending one item to a `multi_select` or\n  `relation` drops the others, so send the complete intended value.\n- `rollup`, `formula`, `unique_id`, and the created/edited fields are\n  computed. They cannot be written.\n- A page's title column is rarely called \"title\" — pass `title_property` from\n  the schema when creating or updating a row.\n- Notion truncates `title`, `rich_text`, `relation`, and `people` at 25\n  entries. `integration_get_page` reports each one in `truncated_properties` as\n  `{ name, id }`; pass that `id` as `property_id` to\n  `integration_get_page_property` for the complete value.\n\n## Reading page content\n\n`integration_get_page` returns properties. `integration_get_page_content` returns the body as flat\nblocks. Nested blocks (toggles, list children, table rows) need `depth`, and\neach level multiplies requests — a deep read stops at an internal ceiling and\nreports `truncated: true` rather than spending the whole rate-limit budget.\n\n## Appending is append-only\n\n`integration_append_blocks` adds children and nothing else. It cannot move, reorder, or\nreplace an existing block, and a block appended through the API can never be\nrelocated by it afterwards. Get the position right the first time with\n`position` and `after_block_id`. Notion caps one call at 100 blocks.\n\n## Lean by default, raw on request\n\nEvery read projects Notion's payload down to ids, plain text, and flattened\nproperty values. Where the dropped detail can matter — `integration_search`, `integration_get_page`,\n`integration_get_page_content`, `integration_get_page_property`, `integration_get_data_source_schema`,\n`integration_query_data_source`, `integration_list_comments` — pass `raw: true` to get Notion's\nuntouched response instead. It is much larger; reach for it only when a\nspecific field is missing. Narrow `integration_query_data_source` and `integration_get_page` with\n`properties` instead whenever the goal is fewer fields, not more.\n\n`integration_get_page_content` with `raw: true` returns one level exactly as Notion\nsent it and does not walk nested children, so `depth` is ignored alongside\nit. A block type this projection does not model keeps its payload under\n`raw` on the block itself, so nothing silently flattens to an empty string.\n\n## Failures worth reading carefully\n\n- **404** means \"no such object\" *or* \"not shared with this integration\", and\n  Notion will not say which. Never conclude a page was deleted from it; check\n  that the page is shared with the integration in Notion.\n- **403** is not an expired token. The integration is missing a capability\n  (comment capabilities are off by default) or the object was never shared.\n  Re-authorizing cannot fix it; an operator must change it in Notion.\n- **429** carries a retry window. Notion allows roughly three requests per\n  second per integration, so wait it out rather than retrying immediately.\n\n## No escape hatch\n\nThis connection has no guarded raw-REST tool, deliberately. Notion's public\nAPI is small and slow-moving enough for the named surface to cover it, so\nthere is no `notion_api_*` to reach for — an operation absent from the tool\nlist is absent from this connection, not hidden behind a generic call.\n\n## Writes and pagination\n\n- Notion has **no idempotency key**. A retried `integration_create_page` or\n  `integration_add_comment` creates a duplicate. Confirm with `integration_search` before repeating\n  a write that may have partially succeeded.\n- List tools take `page_size` (max 100) and return `has_more` with\n  `next_cursor`. Pass a cursor back verbatim — it is opaque and must never be\n  parsed or constructed. Follow pages inside `execute_code` and reduce there.\n",
-        "guide_1": "# Notion MCP usage\n\nOfficial MCP interface: tool names, descriptions, argument schemas, and result\nschemas come from Notion's live server. Connecta preserves that catalog and\napplies release-reviewed classification. Reviewed writes stay writes even when Notion claims they only read.\n\nWorkspace purpose: ",
-        "guide_2": "\n\n- This connection acts as its OAuth-authorized user. The separately configured\n  `surface: \"api\"` connection retains required internal-integration operations\n  under `integration_*` names, including headless content writes, cursor-complete\n  queries, exact JSON blocks and property items. No identity fallback occurs.\n- Discover the live catalog before assuming a tool exists. Notion can gate\n  tools by workspace, account, client, and rollout independently of Connecta.\n- Start broad discovery with `notion-search`, then use `notion-fetch` on\n  the exact page, database, data source, or object before changing it.\n- Use the live input schema as the contract. Notion owns these MCP schemas;\n  the REST schemas in Connecta's API interface do not apply to MCP tools with\n  similar names.\n- Session and agent tools can launch asynchronous work. Read session state and\n  events before sending another message, waiting, or stopping a session.\n- File uploads and attachment tools create durable workspace state. Keep\n  downloads inside the requested task and do not expose signed attachment URLs.\n- An `auth_required` failure means this connector's OAuth grant is missing or\n  expired. Run `authorize_connector` for this connector id, then retry.\n"
+        "oauth_head": "# Notion MCP usage\n\nOfficial MCP interface: tool names, descriptions, argument schemas, and result\nschemas come from Notion's live server. Connecta preserves that catalog and\napplies release-reviewed classification. Reviewed writes stay writes even when Notion claims they only read.\n\nWorkspace purpose: ",
+        "oauth": "\n\n- This connection acts as its OAuth-authorized user and reaches what that user\n  can. It holds no integration token. An internal integration (bot) is a\n  separate connector with `auth: { type: \"token\" }` under another id; never\n  switch to it to recover a failed call here.\n- Discover the live catalog before assuming a tool exists. Notion can gate\n  tools by workspace, account, client, and rollout independently of Connecta.\n- Start broad discovery with `notion-search`, then use `notion-fetch` on\n  the exact page, database, data source, or object before changing it.\n- Use the live input schema as the contract. Notion owns these MCP schemas;\n  the REST schemas of Connecta's token connector do not apply to MCP tools with\n  similar names.\n- Session and agent tools can launch asynchronous work. Read session state and\n  events before sending another message, waiting, or stopping a session.\n- File uploads and attachment tools create durable workspace state. Keep\n  downloads inside the requested task and do not expose signed attachment URLs.\n- Connecta's generic REST tools (`notion_api_*`) and the `integration_*`\n  helpers exist only on a token connector.\n- An `auth_required` failure means this connector's OAuth grant is missing or\n  expired. Run `authorize_connector` for this connector id, then retry.\n",
+        "key": "\n## Identity and tools\n\nThis is Connecta's REST connector to `api.notion.com`, acting as one internal\nintegration (a bot) with an operator-managed integration token. It reaches\nexactly the pages and data sources shared with that integration, and the\nintegration's capabilities decide which calls succeed: comment and\nuser-information capabilities are off by default. It never acts as a person.\nHosted Notion MCP is a separate OAuth connector.\n\n- Named tools cover the common path and flatten Notion's payloads:\n  `integration_search` (titles), `integration_get_page` (properties),\n  `integration_get_page_content` (blocks as text),\n  `integration_get_data_source_schema`, and `integration_query_data_source`\n  (rows). `integration_create_page` and `integration_append_blocks` author\n  Notion's rich-text and block shapes from plain text, Markdown, or checklists.\n- Four generic tools reach every other operation in the pinned API index.\n  `notion_api_search` finds operations, not content. `notion_api_details`\n  returns one operation's parameters. `notion_api_read` calls GETs plus the\n  read-only POST queries: search, data source and meeting note queries, and\n  agent, session, and session event queries. `notion_api_write` calls every\n  other POST, PATCH, and DELETE with `method` and `path` stated.\n- Every generic call is checked against the index before it is sent. An\n  unknown path returns the nearest operations, and an unknown or missing\n  parameter returns `validation.issues` with the accepted names. Nothing\n  reached Notion, so fix the call from that answer.\n- The generic set replaces the old one-operation tools. Read a database\n  container with `GET /v1/databases/{database_id}`, users with `GET /v1/users`\n  or `GET /v1/users/me`, comments with `GET /v1/comments`, and a page as\n  Markdown with `GET /v1/pages/{page_id}/markdown`. Update properties, trash or\n  restore (`in_trash`) with `PATCH /v1/pages/{page_id}`, and comment with\n  `POST /v1/comments`.\n- Refused by design: Notion's OAuth token endpoints (`/v1/oauth/*`) and\n  multipart file sends. Import a file with `POST /v1/file_uploads` and\n  `mode: \"external_url\"` instead.\n- Notion-hosted file URLs in pages and blocks are pre-signed: Connecta\n  withholds their signature, credential, and security-token parameters, so a\n  returned URL names the file but does not download it. Credential-named\n  fields read as `\"[redacted]\"`, a database property named like a credential\n  (`API token`) included. Failures of the OAuth, file upload, bot user, and\n  agent operations carry Notion's code, not its message.\n- Not here: the hosted MCP's user identity, its search across connected\n  apps, page duplication, team and skill search, attachment downloads, and\n  page-to-skill conversion. Those need an OAuth connector.\n\n## Databases contain data sources\n\n- The id in a Notion database URL is a **database id**.\n  `GET /v1/databases/{database_id}` through `notion_api_read` lists its\n  `data_sources`, usually one. `integration_search` returns data sources\n  directly and skips that step.\n- `integration_get_data_source_schema` and `integration_query_data_source`\n  take the **data_source_id**, and so does `integration_create_page` when\n  adding a row.\n\nSo the sequence for \"find rows in this database\" is the database read, then\n`integration_get_data_source_schema`, then `integration_query_data_source`.\n\n## Reading\n\n- `integration_get_page` returns properties. `integration_get_page_content`\n  returns the body as flat blocks. Nested blocks (toggles, list children,\n  table rows) need `depth`, and each level multiplies requests. A deep read\n  stops at an internal ceiling and reports `truncated: true` rather than\n  spending the whole rate-limit budget.\n- Notion truncates `title`, `rich_text`, `relation`, and `people` at 25\n  entries. `integration_get_page` reports each in `truncated_properties` as\n  `{ name, id }`; read the complete value with `notion_api_read`\n  `GET /v1/pages/{page_id}/properties/{property_id}` and follow its cursor.\n- Every named read projects Notion's payload to ids, plain text, and\n  flattened property values. Pass `raw: true` for Notion's untouched response\n  when a specific field is missing. It is much larger. Narrow\n  `integration_query_data_source` and `integration_get_page` with `properties`\n  when the goal is fewer fields. `integration_get_page_content` with\n  `raw: true` returns one level and ignores `depth`.\n\n## Appending is append-only\n\n`integration_append_blocks` adds children and nothing else. It cannot move,\nreorder, or replace an existing block, and a block appended through the API can\nnever be relocated by it afterwards. Get the position right the first time with\n`position` and `after_block_id`. Notion caps one call at 100 blocks.\n\n## Pagination\n\n- Named list tools take `page_size` (max 100) and return `has_more` with\n  `next_cursor`; pass it back as `start_cursor`.\n- Generic results arrive as `{ status, data, page? }`. On a list,\n  `page.next` is the cursor and `page.param` is `start_cursor`: send it in\n  `query` for a GET, and in `body` when `page.in` is `body`, as on the POST\n  queries. Pass `select` dot paths relative to `data`, such as `results.id`;\n  `page` survives any `select`.\n- A view query is created with `notion_api_write`\n  `POST /v1/views/{view_id}/queries`, a write because Notion stores it until\n  `expires_at`. Its first page names the continuation in `page.path`: read\n  `GET /v1/views/{view_id}/queries/{query_id}` with `start_cursor` in `query`.\n- Meeting-note queries have no cursor. `limit` caps at 50, and\n  `page.hasMore` without `page.next` means more notes exist: narrow the\n  filter (for example by `created_time`) rather than paging.\n- Cursors are opaque: never parse or construct one. Follow pages inside\n  `execute_code` and reduce there.\n\n## Failures worth reading carefully\n\n- **404** means \"no such object\" *or* \"not shared with this integration\", and\n  Notion will not say which. Never conclude a page was deleted from it; check\n  that the page is shared with the integration in Notion.\n- **403** is not an expired token. The integration is missing a capability\n  (comment capabilities are off by default) or the object was never shared.\n  Re-authorizing cannot fix it; an operator must change it in Notion.\n- **429** carries a retry window. Notion allows an average of three requests\n  per second per integration; Connecta admits 180 calls a minute, three at a\n  time, per runtime. Wait out the window rather than retrying immediately.\n",
+        "shared": "\n## Notion's data model\n\n- A database is a container; its rows and schema live in a *data source*\n  inside it. Queries, schema reads, and new rows take the data source, and\n  Notion rejects a database id in its place.\n- Property names in filters, sorts, and writes must match the schema exactly,\n  including case. Read the schema before composing one.\n- `select` and `status` writes must use an existing option name; inventing\n  one fails. The schema lists the valid options.\n- Writes **replace** a property. Sending one item to a `multi_select` or\n  `relation` drops the others, so send the complete intended value.\n- `rollup`, `formula`, `unique_id`, and the created and edited fields are\n  computed. They cannot be written.\n- A data source's title column is rarely called \"title\". Read its name from\n  the schema before creating or renaming a row.\n- Notion has **no idempotency key**. A retried page create or comment makes a\n  duplicate. Confirm with a search before repeating a write that may have\n  partially succeeded.\n"
     }
 };

package/dist/providers/notion/value-safety.js

@@ -0,0 +1,31 @@
+// Notion's reviewed value-safety table (#801), on the shared mechanism in
+// `../_shared/rest/value-safety.ts`: every operation the detector flags in
+// the pinned spec (`value-safety.candidates.json`) has one verdict here, and
+// `value-safety.node.test.ts` runs the shared harness over it.
+//
+// Notion's API returns little that is a credential: an integration token
+// never appears in a response. The OAuth endpoints mint, introspect, and
+// revoke tokens with a public integration's client secret and are refused.
+// A file upload's `upload_url` is Notion's own send endpoint and needs the
+// integration token, so it is kept. Notion-hosted file URLs in pages and
+// blocks are pre-signed: the shared URL rule withholds their signature,
+// credential, and security-token query parameters on every response, so a
+// returned URL names the file without granting access to it.
+import { refuse, safe } from "../_shared/rest/value-safety.js";
+const OAUTH = "Notion's OAuth token endpoints are not reachable through Connecta: they mint and revoke credentials with a public integration's client secret, which this connector never holds.";
+const UPLOAD = "A file upload's upload_url is Notion's own send endpoint, which needs the integration token; it grants nothing alone.";
+const AGENT = "Custom agents name their connected MCP server's host, never its URL or credentials.";
+const OPERATIONS = {
+    "POST /v1/oauth/token": refuse(OAUTH),
+    "POST /v1/oauth/introspect": refuse(OAUTH),
+    "POST /v1/oauth/revoke": refuse(OAUTH),
+    "GET /v1/users/me": safe("Answers the integration's bot user; no token."),
+    "GET /v1/file_uploads": safe(UPLOAD, ["results.upload_url"]),
+    "POST /v1/file_uploads": safe(UPLOAD, ["upload_url"]),
+    "GET /v1/file_uploads/{file_upload_id}": safe(UPLOAD, ["upload_url"]),
+    "POST /v1/file_uploads/{file_upload_id}/complete": safe(UPLOAD, ["upload_url"]),
+    "POST /v1/file_uploads/{file_upload_id}/send": safe(UPLOAD, ["upload_url"]),
+    "POST /v1/agents/query": safe(AGENT, ["results.connections.account.server_host"]),
+    "GET /v1/agents/{agent_id}": safe(AGENT, ["connections.account.server_host"]),
+};
+export const NOTION_VALUE_SAFETY = { title: "Notion", operations: OPERATIONS };

package/dist/providers/stripe/index.d.ts

@@ -1,10 +1,10 @@
-import { type RemoteMcpAuth } from "../../connectors/remote-mcp.js";
-/** Which Stripe environment a static credential reaches. */
-export type StripeMode = "production" | "sandbox";
+import { type StripeMode } from "./rest.js";
+export type { StripeMode } from "./rest.js";
+export { STRIPE_API_BASE_URL } from "./rest.js";
 /** Stripe publishes one hosted MCP endpoint for every account and mode. */
 export declare const STRIPE_MCP_ENDPOINT = "https://mcp.stripe.com/";
 interface StripeCommonOptions {
-    /** Human-readable display name; defaults to "Stripe" for OAuth. */
+    /** Human-readable display name; defaults to "Stripe" for OAuth and the mode for a key. */
     title?: string;
     /** Downstream auth ownership. Defaults to one shared deployment grant. */
     authScope?: "shared" | "personal";
@@ -15,33 +15,39 @@ interface StripeCommonOptions {
     /** Connector-specific inline result limit; omit to inherit the deployment. */
     maxResultBytes?: number;
 }
-/** OAuth sessions discover account and mode together from Stripe's live tools. */
+/**
+ * Stripe's hosted MCP server over OAuth. One session can reach live and
+ * sandbox accounts; Stripe returns the mode with each account.
+ */
 export interface StripeOAuthOptions extends StripeCommonOptions {
-    auth?: {
+    auth: {
         type: "oauth";
     };
+    /** Refused: OAuth reaches live and sandbox accounts, and Stripe returns mode with each. */
     mode?: never;
+    /** Refused: a Connect account needs an API-key connector. */
     connectedAccount?: never;
 }
 /**
- * Static credentials have one fixed mode, including Stripe Connect calls.
- *
- * Both static shapes belong here: a key the deployment supplies as a literal
- * header, and one the operator pastes into the connection in the operator UI.
- * Neither can discover its own mode, since a restricted key answers for
- * exactly one, so both declare it.
+ * Connecta's REST connector to `api.stripe.com` with one operator-managed
+ * secret or restricted key, pasted into the connection in the operator UI.
+ * A key reaches exactly one mode, so the connector declares it, and a key
+ * whose prefix says otherwise is refused before any request leaves.
  */
-export interface StripeHeaderOptions extends StripeCommonOptions {
-    auth: Exclude<RemoteMcpAuth, {
-        type: "oauth" | "request";
-    }>;
+export interface StripeApiKeyOptions extends StripeCommonOptions {
+    auth: {
+        type: "apiKey";
+    };
     mode: StripeMode;
-    /** Act as one Connect account by sending Stripe's `Stripe-Account` header. */
+    /** Act as one Connect account: `Stripe-Account` on v1, `Stripe-Context` on v2. */
     connectedAccount?: string;
 }
-export type StripeOptions = StripeOAuthOptions | StripeHeaderOptions;
-/** A maintained Stripe hosted-MCP connection. */
+export type StripeOptions = StripeOAuthOptions | StripeApiKeyOptions;
+/**
+ * A maintained Stripe connection. `auth` selects the implementation: OAuth
+ * reaches Stripe's hosted MCP server; an API key reaches Connecta's REST
+ * connector to `api.stripe.com`.
+ */
 export declare const stripe: import("../../provider.js").ProviderFactory<StripeOptions>;
 /** @deprecated Read `stripe.definition.classify` instead. Kept for existing imports. */
 export declare const STRIPE_VETTED_CATALOG: import("../../catalog-drift.js").VettedCatalog;
-export {};

package/dist/providers/stripe/index.js

@@ -1,18 +1,21 @@
 import { skill } from "./skill.generated.js";
-import { remoteMcp, withCredentialDefaults } from "../../connectors/remote-mcp.js";
+import { apiConnector } from "../../connectors/api-connector.js";
 import { reviewedCatalog } from "../../catalog-drift.js";
-import { keys, optionsOf, strings, variants } from "../../config-schema.js";
-import { CREDENTIAL } from "../../connectors/option-shapes.js";
+import { keys, optionsOf, variants } from "../../config-schema.js";
 import { defineProvider } from "../../provider.js";
+import { byAuth, hostedOAuth } from "../_shared/rest/dispatch.js";
+import { restTools } from "../_shared/rest/tools.js";
+import { stripeRest } from "./rest.js";
+export { STRIPE_API_BASE_URL } from "./rest.js";
 /** Stripe publishes one hosted MCP endpoint for every account and mode. */
 export const STRIPE_MCP_ENDPOINT = "https://mcp.stripe.com/";
 /**
  * Stripe documents no MCP-specific limit, so these transcribe the account limit
- * MCP traffic spends: 100 requests per second live, 25 in a sandbox. OAuth takes
- * the sandbox rule (`mode ?? "sandbox"` below) because one session can reach
- * either mode and the policy is fixed before the account-scoped call begins.
- * The `maxConcurrency` figures are Connecta's own choice — Stripe says
- * per-account and per-endpoint concurrency limits exist but publishes no number.
+ * every request spends: 100 requests per second live, 25 in a sandbox. OAuth
+ * takes the sandbox rule because one session can reach either mode and the
+ * policy is fixed before the account-scoped call begins. The `maxConcurrency`
+ * figures are Connecta's own choice — Stripe says per-account and per-endpoint
+ * concurrency limits exist but publishes no number.
  */
 const STRIPE_ADMISSION = {
     production: {
@@ -40,7 +43,9 @@ const STRIPE_ADMISSION = {
  * Reviewed in #705's provider audit against https://docs.stripe.com/mcp.
  * Retains the release-reviewed inventory, including names absent from today's
  * public reference. Live annotations were not reverified without credentials.
- * No schema digest is asserted without a captured schema to review.
+ * No schema digest is asserted without a captured schema to review. This
+ * classifies the hosted OAuth catalog only; the REST connector annotates each
+ * tool it authors.
  */
 const STRIPE_CLASSIFICATION = {
     tools: {
@@ -109,158 +114,126 @@ const STRIPE_CLASSIFICATION = {
         },
     },
 };
-/** Stripe key prefixes carry their own mode; only a clear reading counts. */
-const LIVE_KEY = /\b(?:sk|rk|pk)_live_/;
-const TEST_KEY = /\b(?:sk|rk|pk)_test_/;
-/**
- * Refuse a recognizable key/mode mismatch. This is the only mode guard Connecta
- * can offer, and it needs the key as a literal header to read the prefix: an
- * operator-managed key is not in the deployment file, so its declared mode
- * stands alone and a key pointed at the other environment fails at Stripe.
- */
-function assertModeMatchesKey(id, mode, auth) {
-    if (auth.type !== "headers")
-        return;
-    for (const value of Object.values(auth.headers)) {
-        const keyMode = LIVE_KEY.test(value) ? "production" : TEST_KEY.test(value) ? "sandbox" : undefined;
-        if (keyMode !== undefined && keyMode !== mode) {
-            throw new Error(`stripe("${id}") declares mode "${mode}" but its auth headers carry a ` +
-                `${keyMode === "production" ? "live" : "test"}-mode Stripe key.`);
-        }
-    }
-}
-function resolveAuth(id, options) {
-    const auth = withCredentialDefaults(options.auth ?? { type: "oauth" }, {
-        credential: {
-            label: "Secret or restricted API key",
-            description: "A Stripe secret or restricted API key for this connector's declared mode. Stripe sends it as a bearer token; it is stored encrypted and never displayed.",
-            placeholder: "sk_… or rk_…",
-        },
-    });
-    const connectedAccount = options.connectedAccount?.trim();
-    if (connectedAccount === undefined || connectedAccount === "")
-        return auth;
-    if (!connectedAccount.startsWith("acct_")) {
-        throw new Error(`stripe("${id}") connectedAccount must be a Stripe account id ("acct_...").`);
-    }
-    if (auth.type === "oauth") {
-        throw new Error(`stripe("${id}") cannot reach a connected account over OAuth; Stripe ` +
-            `requires a restricted API key for Stripe-Account calls.`);
-    }
-    if (auth.type === "credential" || auth.type === "request") {
-        // `Stripe-Account` is a second header beside the credential's own, and the
-        // credential shape assembles exactly one. A Connect connector therefore
-        // still takes its restricted key as a literal header.
-        throw new Error(`stripe("${id}") cannot reach a connected account with an ` +
-            `operator-managed credential; Stripe-Account is a second static ` +
-            `header, so declare auth: { type: "headers" } for this connector.`);
-    }
-    return {
-        type: "headers",
-        headers: { ...auth.headers, "Stripe-Account": connectedAccount },
-    };
+function instructionsSection(instructions) {
+    const text = instructions?.trim();
+    return text ? `\n## ${skill.instructionsHeading}\n\n${text}\n` : "";
 }
 function oauthUsageGuide(purpose, instructions) {
-    const accountInstructions = instructions?.trim();
+    const { oauth, shared, oauth_limits } = skill.fragments;
     return `# Stripe usage
 
-Scope: live and sandbox accounts. Connector purpose: ${purpose}${skill.fragments.guide_0}${sharedUsageGuide("100 requests per second in live mode and 25 in sandbox mode")}
-${accountInstructions ? `\n## ${skill.instructionsHeading}\n\n${accountInstructions}\n` : ""}`;
+Scope: live and sandbox accounts. Connector purpose: ${purpose}${oauth}${shared}${oauth_limits}
+${instructionsSection(instructions)}`;
 }
 const MODE_COPY = {
     production: {
         title: "Stripe (production)",
         blurb: "production — live money and real customers",
         warning: "This is a PRODUCTION Stripe connection. Every write moves real money against real customers, and a refund cannot be undone. If a request could plausibly be a rehearsal, route it to a sandbox connector instead.",
+        rate: "100 requests per second",
     },
     sandbox: {
         title: "Stripe (sandbox)",
         blurb: "sandbox — test data, no real money",
         warning: "This is a SANDBOX Stripe connection. Nothing here is real money and none of these objects exist in production, so never answer a question about live revenue, payouts, or a named customer from this connector.",
+        rate: "25 requests per second",
     },
 };
-function fixedModeUsageGuide(mode, purpose, instructions) {
+function keyUsageGuide(mode, purpose, connectedAccount, instructions) {
     const copy = MODE_COPY[mode];
-    const accountInstructions = instructions?.trim();
+    const { key, shared, key_limits, key_tail } = skill.fragments;
+    const connect = connectedAccount
+        ? `\n\nConnected account: \`${connectedAccount}\`. Every call acts as this Connect account; the platform account's own objects are out of reach here.`
+        : "";
     return `# Stripe usage
 
 Mode: ${mode}. Connector purpose: ${purpose}
 
-${copy.warning}${skill.fragments.guide_1}${sharedUsageGuide(`${mode === "production" ? "100" : "25"} requests per second`)}
-${accountInstructions ? `\n## ${skill.instructionsHeading}\n\n${accountInstructions}\n` : ""}`;
-}
-function sharedUsageGuide(rate) {
-    return `${skill.fragments.guide_2}${rate}${skill.fragments.guide_3}`;
+${copy.warning}${connect}${key}${shared}${key_limits}${copy.rate}${key_tail}
+${instructionsSection(instructions)}`;
 }
-/** The closed options stripe() accepts; see `assertKnownOptions`. */
-const STRIPE_OPTIONS = optionsOf()({
-    ...keys("title", "authScope", "purpose", "instructions", "maxResultBytes", "mode", "connectedAccount"),
-    auth: variants("type", {
-        oauth: keys("type"),
-        headers: optionsOf()({ ...keys("type"), headers: strings() }).shape,
-        credential: optionsOf()({
-            ...keys("type", "header", "scheme"),
-            credential: CREDENTIAL,
-        }).shape,
-    }),
+const COMMON = keys("title", "authScope", "purpose", "instructions", "maxResultBytes");
+/** The closed options stripe() accepts, selected by `auth.type`; see `assertKnownOptions`. */
+const STRIPE_OPTIONS = variants(["auth", "type"], {
+    // The never-typed keys stay out of the shape, so the walk refuses them by name.
+    oauth: optionsOf()({
+        ...COMMON,
+        auth: optionsOf()(keys("type")),
+    }).shape,
+    apiKey: optionsOf()({
+        ...COMMON,
+        ...keys("mode", "connectedAccount"),
+        auth: optionsOf()(keys("type")),
+    }).shape,
 });
-/** A maintained Stripe hosted-MCP connection. */
+function stripeOAuth(id, options, provider) {
+    return hostedOAuth(id, provider, {
+        url: STRIPE_MCP_ENDPOINT,
+        title: options.title ?? "Stripe",
+        description: `Stripe payments (live and sandbox accounts) — ${options.purpose}`,
+        callAdmission: STRIPE_ADMISSION.sandbox,
+        usageGuide: {
+            content: oauthUsageGuide(options.purpose, options.instructions),
+            // Explicit rather than derived: OAuth must lead with its account-scoped selector pair.
+            summary: "Live and sandbox Stripe accounts. List accounts; carry the returned stripe_context and livemode before acting.",
+        },
+    });
+}
+function stripeApiKey(id, options, provider) {
+    const mode = options.mode;
+    if (mode !== "production" && mode !== "sandbox") {
+        throw new Error(`stripe("${id}") requires mode "production" or "sandbox" with apiKey auth.`);
+    }
+    let connectedAccount;
+    if (options.connectedAccount !== undefined) {
+        connectedAccount = typeof options.connectedAccount === "string" ? options.connectedAccount.trim() : "";
+        if (!/^acct_[A-Za-z0-9]+$/.test(connectedAccount)) {
+            throw new Error(`stripe("${id}") connectedAccount must be a Stripe account id ("acct_...").`);
+        }
+    }
+    const copy = MODE_COPY[mode];
+    const live = mode === "production" ? "live" : "test";
+    const rest = stripeRest(mode, connectedAccount);
+    return apiConnector(id, {
+        ...provider.connectorOptions,
+        title: options.title ?? copy.title,
+        description: `Stripe payments (${copy.blurb}) — ${options.purpose}`,
+        credential: {
+            label: `Stripe ${live}-mode secret or restricted key`,
+            description: `A ${live}-mode secret (sk_${live}_…) or restricted (rk_${live}_…) key; prefer a restricted key with only the permissions this connector needs. It is sent only to api.stripe.com and files.stripe.com, stored encrypted, and never displayed.`,
+            placeholder: `rk_${live}_…`,
+        },
+        testCredential: rest.testCredential,
+        callAdmission: STRIPE_ADMISSION[mode],
+        usageGuide: {
+            content: keyUsageGuide(mode, options.purpose, connectedAccount, options.instructions),
+            // Explicit rather than derived: a key connector must lead with its one mode.
+            summary: mode === "production"
+                ? "PRODUCTION: real money. One live-mode key over REST; search operations, read details, then read or write."
+                : "Sandbox: test data only. One test-mode key over REST; search operations, read details, then read or write.",
+        },
+        tools: [...restTools(rest.vendor), ...rest.tools],
+    });
+}
+/**
+ * A maintained Stripe connection. `auth` selects the implementation: OAuth
+ * reaches Stripe's hosted MCP server; an API key reaches Connecta's REST
+ * connector to `api.stripe.com`.
+ */
 export const stripe = defineProvider({
     name: "stripe",
     title: "Stripe",
-    kind: "mcp",
+    kind: "dual",
     readme: "Stripe",
-    bundle: { "baselineGzip": 129103, "maxGzip": 189103 },
+    bundle: {
+        "baselineGzip": 232089,
+        "maxGzip": 292089,
+        "note": "./providers/stripe remeasures at 232,089 B gzip (#801), from 170,771 B on main: auth now selects the implementation, so the entry carries the hosted MCP client and Connecta's REST connector (api(), the schema validator, guarded transport, the shared REST module) plus the pinned Stripe operation index (638 operations; request details to depth 2, without descriptions or enums over 50 values; 37,918 B gzip as source). Details were shrunk before the cap moved: the first full index measured 81 KB gzip. The cap uses the existing baseline + 60,000 B policy.",
+    },
     skill,
     options: STRIPE_OPTIONS,
     classify: STRIPE_CLASSIFICATION,
-    create: stripeConnector,
+    create: byAuth({ oauth: stripeOAuth, apiKey: stripeApiKey }),
 });
-function stripeConnector(id, options, provider) {
-    const purpose = options.purpose.trim();
-    const auth = resolveAuth(id, options);
-    const mode = "mode" in options ? options.mode : undefined;
-    if (auth.type === "oauth" && mode !== undefined) {
-        throw new Error(`stripe("${id}") cannot declare a connector-wide mode for OAuth; Stripe returns mode with each account.`);
-    }
-    if (auth.type !== "oauth" && mode !== "production" && mode !== "sandbox") {
-        throw new Error(`stripe("${id}") with headers or credential auth requires mode ` + `"production" or "sandbox".`);
-    }
-    // Only a literal header can be inspected. An operator-managed credential is
-    // not readable at construction — there is nothing in the deployment file to
-    // read — so the declared mode stands alone, and a key pointed at the other
-    // one is Stripe's own refusal to report.
-    if (auth.type === "headers") {
-        assertModeMatchesKey(id, mode, auth);
-    }
-    const copy = mode === undefined ? undefined : MODE_COPY[mode];
-    const connector = remoteMcp(id, {
-        url: STRIPE_MCP_ENDPOINT,
-        ...provider.connectorOptions,
-        title: options.title ?? copy?.title ?? "Stripe",
-        description: mode === undefined
-            ? `Stripe payments (live and sandbox accounts) — ${purpose}`
-            : `Stripe payments (${copy?.blurb}) — ${purpose}`,
-        auth,
-        requireHttps: true,
-        classify: provider.classify,
-        callAdmission: STRIPE_ADMISSION[mode ?? "sandbox"],
-        usageGuide: {
-            content: mode === undefined
-                ? oauthUsageGuide(purpose, options.instructions)
-                : fixedModeUsageGuide(mode, purpose, options.instructions),
-            // Explicit rather than derived: fixed credentials must lead with mode,
-            // while OAuth must lead with its account-scoped selector pair.
-            summary: mode === undefined
-                ? "Live and sandbox Stripe accounts. List accounts; carry the returned stripe_context and livemode before acting."
-                : mode === "production"
-                    ? "PRODUCTION: real money. This static credential has one fixed live-mode scope."
-                    : "Sandbox: test data only. This static credential has one fixed sandbox scope.",
-            // Not `required`. The four generic tools are the routing decision; a
-            // guide forced into every call would pay for the same prose repeatedly.
-        },
-    });
-    return connector;
-}
 /** @deprecated Read `stripe.definition.classify` instead. Kept for existing imports. */
 export const STRIPE_VETTED_CATALOG = reviewedCatalog(stripe.definition.classify, 'defineProvider("stripe")');