Marketplace

V3 Deno JavaScript/TypeScript runtime capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local deno CLI ingredient exposes bounded project operations for readiness, formatting checks, lint diagnostics, type checks, dependency graph inspection, dependency vulnerability audit, and sandboxed targeted test execution. Project operations run from an explicit project directory cwd supplied at execution time through the native cli_invocation cwd field, avoid caller-supplied deno flags, avoid shell wrappers, and keep diagnostics visible as text or JSON output. Type-check, info, and audit operations use frozen-lockfile mode. Test execution uses cached-only module loading and disables permission prompts while granting no runtime permissions. The pack intentionally excludes deno task, deno run, compile, publish, add/remove/update, fix/write modes, watch mode, arbitrary permission grants, arbitrary import maps, and caller-selected remote URLs. Requires deno on PATH.

V3 deterministic filesystem capacity-inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local df CLI ingredient exposes bounded read-only disk-capacity metadata for readiness, one trusted local path, one executor-supplied project directory, inode usage, and local mounted filesystems. The operations return filesystem capacity rows only; they do not return file content, list child paths, recurse directories, select remote mounts, accept filesystem type filters, expose arbitrary df flags, rely on BLOCKSIZE environment overrides, read stdin, write output files, or use a shell wrapper. Editable paths reject flag-like values, URL-like references, and scp-style remotes. Project operations run from an explicit project directory cwd supplied at execution time. Requires a POSIX-compatible df on PATH. Local and no-egress.

V3 bounded DNS diagnostics capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local dig CLI ingredient exposes fixed operations for readiness plus common DNS lookups: A, AAAA, CNAME, MX, TXT, NS, SOA, CAA, and reverse PTR. DNS lookup operations require approval because they send caller-supplied names or addresses through the executor's local dig resolver selection and can reveal the executor network path. The pack uses short output, one lookup name/address per invocation, fixed timeout and retry caps, explicit command-line overrides for trace, nssearch, search-list, TCP, and responder-identification defaults, and no caller-supplied resolver, query class, arbitrary record type, trace, zone transfer, batch file or config file, environment override, stdin, output-file write, or shell wrapper. Requires dig on PATH, commonly provided by BIND utilities.

API capability pack for bounded DigitalOcean API v2 operations against https://api.digitalocean.com. Enroll a digitalocean API connection as a bearer-token connection backed by a scoped DigitalOcean personal access token or OAuth access token; no credential is embedded in the manifest. The pack reads account metadata, billing balance/history/invoices, Droplets, backups, snapshots, firewalls, domains and DNS records, projects, VPCs, database clusters and backups, Kubernetes clusters, load balancers, volumes, regions, sizes, certificates, monitoring alert policies, and App Platform apps/deployments/events/alerts/health, plus approval-gated DNS record create/update for daily domain maintenance. It intentionally does not expose DNS record deletion, domain mutation, Droplet actions, database user/password endpoints, Kubernetes kubeconfig/credentials, App deploy/retry/rollback/log/exec actions, invoice CSV/PDF downloads, volume actions, load-balancer writes, create/update/delete endpoints outside single DNS records, or arbitrary API passthrough.

API capability pack for bounded Discord HTTP API v10 operations against https://discord.com/api/v10. Reads current user or bot identity, guilds, channels, members, roles, invites, messages, pins, reactions, active and archived threads, guild message search, and scheduled events, and supports approval-gated single message sends and edits, own reactions, pins, thread creation and membership, invite creation, and scheduled event creation or update. Bundles a scheduled channel activity digest, an AI-assisted thread brief, and an approval-gated channel update workflow. Enroll a Discord bot token or OAuth bearer token connection named discord; no credential is embedded in the manifest. Message content can be empty or partial when the app lacks Discord's privileged Message Content intent. The pack intentionally excludes message delete and bulk delete, ban/kick/moderation actions, role/member/guild/channel administration, webhook-token endpoints, file upload, DM creation, application commands, OAuth token exchange, audit log access, and arbitrary API passthrough.

V3 bounded Docker daemon diagnostics capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local docker CLI ingredient exposes fixed operations for client readiness, context inventory, daemon info, container/image/volume/network inventory, disk-usage summary, stats snapshot, and explicit container/image inspection. Docker daemon and context operations require approval because Docker socket access can reveal host paths, image names, container names, labels, environment, network endpoints, and other sensitive local runtime metadata. The pack exposes no run, exec, attach, cp, logs, build, pull, push, login, start, stop, restart, kill, rm, rmi, prune, system mutation, plugin, compose, arbitrary Docker flags, environment override, stdin, output-file write, or shell wrapper. Requires Docker CLI on PATH and a reachable Docker daemon for daemon operations.

V3 deterministic container-orchestration capability pack. By-value cli composition (service_kind=cli, no separate service ingredient): one local docker CLI ingredient exposes bounded Docker Compose readiness, config inspection, stack launch, stack teardown, and stack status operations. The read path covers docker_compose.version plus compose.config_json / compose.config_validate / compose.config_services / compose.config_images / compose.config_profiles / compose.config_variables; up/down remain admin-risk and approval=ask because they start or stop a container stack. NOT a Recued-supervised daemon: `docker compose up -d` launches the stack into Docker's OWN lifecycle and returns immediately; Recued records the one-shot launch, it does not health-check or restart the containers. The compose file is a validated local path on the server the user points at; Docker Compose resolves relative paths from the first compose file by default. Requires Docker Engine + the compose plugin on PATH (rootless Docker supported). Replaces the retired docker-compose-{linux,macos,win} service templates.

API capability pack for bounded DocuSign eSignature REST API v2.1 operations. Enroll a docusign OAuth bearer connection with the signature scope, set base_url to the account REST API root returned from /oauth/userinfo (such as https://demo.docusign.net/restapi or https://www.docusign.net/restapi), and store that account's account_id in connection config for the envelope Source. The pack reads accounts, settings, users, groups, permission profiles, brands, folders, envelopes, recipients, tabs, document metadata, templates, custom fields, bulk-send metadata, contacts, audit events, notifications, and form data. It adds a read-only, paginated task Source for envelope lifecycle work and bundles a scheduled envelope status digest, a read-only envelope evidence brief, and an approval-gated send-from-template workflow. Writes are approval-gated and limited to one envelope/template/contact/custom-field/notification action at a time; envelope status changes are always-confirm destructive operations because the same endpoint can void an in-process envelope. It intentionally excludes arbitrary endpoint passthrough, Connect/webhook administration, permission or user administration writes, group and signing-group writes, billing plan changes, bulk-send execution, purges, deletes, locks, document binary downloads, signature image downloads, multipart uploads, recipient/signing ceremony URL creation, and arbitrary template/envelope correction URLs.

Workflow pack for Recued-sent DocuSign template envelopes. It composes the DocuSign capability pack with a closure ledger: send one template envelope through the existing DocuSign approval gate, persist only the envelope/template/account linkage in data.shared, and let a scheduled watcher re-read that exact envelope until DocuSign reports completed, declined, voided, deleted, or expired. This pack does not duplicate DocuSign reminders, expiration settings, recipient notifications, Connect/webhook administration, or general envelope status dashboards; it adds Recued-visible closure state for envelopes Recued sent.

V3 .NET CLI toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local dotnet CLI ingredient exposes bounded project operations for readiness, build checking, and test execution. Project operations run from an explicit project directory cwd supplied at execution time, disable implicit restore, suppress the logo, avoid caller-supplied dotnet/MSBuild/test-runner flags, avoid shell wrappers, and keep diagnostics visible as text output. Build and test operations are approval-gated because dotnet may compile project code, load SDK/MSBuild targets, run test adapters and test code, and write bin/obj/TestResults or other project-controlled artifacts. Requires dotnet on PATH.

API capability pack for bounded Dropbox metadata operations against https://api.dropboxapi.com only. Reads the current account, reads file/folder metadata, lists folder entries, continues a folder cursor, searches files/folders, lists revisions and shared links, and supports approval-gated daily organization actions: create folders, move or rename files/folders, copy files/folders, restore one file revision, and create or revoke one basic shared link. File upload/download and temporary content links are intentionally not exposed because Dropbox content endpoints use separate hosts outside this pack's egress allowlist. Delete/trash, arbitrary sharing settings, member permissions, ownership transfer, batch mutation, webhooks, and arbitrary passthrough are intentionally excluded. Enroll a Dropbox OAuth access token connection as bearer auth; no credential is embedded in the manifest.

One-install Dropbox Sign API v3 front door over two bounded domain packs and seven existing e-signature workflows. The suite publishes 73 executable catalog operations covering 68 of 73 unique operations from Dropbox Sign's immutable official OpenAPI at commit 31136f9035133acb5f055a94f24e006857210fdb. This 13-operation compatibility root preserves every prior ID, effective URL, result shape, and single-page bound while dependencies add 60 operations, including five sensitive-read-marked aliases for complete page walks and the nested bulk-job request collection. Five fail-closed exclusions cover two OAuth credential exchanges, two base64-document JSON responses that bypass file isolation, and one mandatory DELETE body the REST transport cannot serialize. Coverage includes accounts, API apps, signing requests, templates, embedded signing and editing, bulk sends, reports, unclaimed drafts, teams, fax lines, fax delivery, and isolated file downloads. The upgrade repairs origin/path composition, stale entity claims, team-member extraction on its full-walk alias, binary file capture, JSON alternatives, and exact integer parsing. API-key credentials remain connection-owned; a manually enrolled OAuth bearer connection can satisfy the same ingredient. Existing workflow reads and writes retain their approval behavior, new sensitive reads are marked sensitive-read, and every new mutation requires approval. No Source is claimed without live field-presence proof.

Dropbox Sign accounts, API apps, teams, fax lines, fax delivery, and isolated fax document downloads. Generated from Dropbox Sign's immutable official OpenAPI at commit 31136f9035133acb5f055a94f24e006857210fdb. This leaf carries 28 of the suite's 73 catalog operations over 68 unique admitted official routes. Full-page aliases are separate from single-page compatibility IDs, so existing workflow bounds stay stable. The ingredient uses the origin-only API base and explicit /v3 wire paths; the documentary alias reconciles that prefix to the official path table. JSON alternatives are selected instead of multipart bodies, binary request fields are omitted in favor of URL/structured alternatives, binary GET responses become private file_refs, unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, and every mutation is approval-gated.

Dropbox Sign signature requests, templates, embedded signing and editing, bulk send jobs, reports, and unclaimed drafts. Generated from Dropbox Sign's immutable official OpenAPI at commit 31136f9035133acb5f055a94f24e006857210fdb. This leaf carries 32 of the suite's 73 catalog operations over 68 unique admitted official routes. Full-page aliases are separate from single-page compatibility IDs, so existing workflow bounds stay stable. The ingredient uses the origin-only API base and explicit /v3 wire paths; the documentary alias reconciles that prefix to the official path table. JSON alternatives are selected instead of multipart bodies, binary request fields are omitted in favor of URL/structured alternatives, binary GET responses become private file_refs, unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, and every mutation is approval-gated.

V3 deterministic filesystem size-inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local du CLI ingredient exposes bounded read-only disk-usage metadata for one trusted local path. The operations return summary size output only: KiB disk usage, human-readable disk usage, apparent-size KiB, and a fixed readiness probe. They do not return file content, list child paths, emit per-file recursive rows, read stdin, accept file lists, follow symlinks explicitly, cross-device-control flags, ignore masks, caller-supplied thresholds, environment overrides, arbitrary du flags, write files, or use a shell wrapper. Editable paths reject flag-like values, URL-like references, and scp-style remotes. Requires a POSIX-compatible du on PATH. Local and no-egress.

Self-contained Microsoft Dynamics 365 (Dataverse) CRM vendor pack — the D-192 'de-hardcode, prefer-as-pack' forcing function. Declares the Dataverse Web API (OData v4) surface as a by-value composition. Native entities map into the canonical CRM vocabulary: contact -> contact. The activity entities (email, appointment, phonecall, task) carry the D-192 engagement facet with sync_kind 'delta_cursor' (Dataverse change-tracking / $deltatoken) — a pack-declared engagement plane that reconciles through the generic engagement reconciler with no bespoke dispatch. Entra/Microsoft OAuth (reused from the OneDrive lane). Reads resolve after connection grant.

E2B team discovery and metrics plus user access-token and team API-key lifecycle operations. Generated from the immutable official spec/openapi.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 9 of the suite's 72 admitted operations. Pick the E2B account connection whose AuthProvider bearer access token is stored as a complete Bearer value in Authorization. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

E2B node inspection and state control plus team-wide sandbox, build, and API-key administration operations. Generated from the immutable official spec/openapi.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 7 of the suite's 72 admitted operations. Pick the privileged E2B cluster connection whose administrative token is stored in X-Admin-Token. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

Finite E2B sandbox-local envd health, resource metrics, environment-variable, and file-download operations. Generated from the immutable official spec/envd/envd.yaml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 4 of the suite's 72 admitted operations. Pick the sandbox-scoped E2B envd connection carrying X-Access-Token and E2b-Sandbox-Id. Re-enroll it when the sandbox or access token changes. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

Finite E2B Connect-JSON filesystem and process inspection, mutation, watcher, input, signal, and stdin-control operations. Generated from the immutable official filesystem and process protobuf contracts at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab; the official SDK's Connect JSON mode supplies the audited HTTP wire mapping. This leaf carries 13 of the suite's 72 admitted operations. Pick the sandbox-and-user-scoped E2B RPC connection carrying X-Access-Token, E2b-Sandbox-Id, and Authorization as Basic base64(username:). Use Basic dXNlcjo= for the default user. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

E2B sandbox creation, discovery, logs, metrics, pause, reconnect, timeout, network, refresh, snapshot, and deletion operations. Generated from the immutable official spec/openapi.yml contract at E2B commit 7474d904a2f6056f9528e73baf697368e03bf6ab. This leaf carries 16 of the suite's 72 admitted operations. Pick the E2B control-plane connection whose E2B API key is stored in X-API-Key. JSON request documents are sent verbatim, scalar integer selectors use exact decimal strings, unsafe JSON response integers remain exact strings, reads are uncached, private reads are marked sensitive-read, every mutation requires approval, and no sandbox or infrastructure object is misrepresented as a task, note, or project Source.

API capability pack for bounded Cohere REST API operations against https://api.cohere.com only. Enroll a Cohere API key bearer connection named cohere; no credential is embedded in this manifest. The pack reads API-key status, model metadata, datasets, dataset usage, embed jobs, tokenization results, rerank results, and text embedding responses for semantic search, retrieval, RAG evaluation, and embedding operations. It bundles a rerank review brief, an embedding readiness brief, a scheduled model/dataset operations digest, and approval-gated workflows for creating or canceling one async embed job. Writes are limited to creating one embed job for an existing dataset or canceling one embed job. The pack intentionally excludes streaming-only chat and generate endpoints, deprecated classify/connectors surfaces, OAuth connector authorization, fine-tuning create-update-delete, dataset upload/create/delete, audio transcription uploads, batch create/cancel, model deletion or mutation, arbitrary Cohere API passthrough, and any dynamic outbound callback or tool-execution routing.

V3 PHP Composer toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local composer CLI ingredient exposes bounded project operations for readiness, composer.json validation, test script execution, and dependency policy audit. Project operations run from an explicit project directory cwd supplied at execution time, use non-interactive/no-ANSI output, avoid caller-supplied Composer flags, avoid shell wrappers, and keep diagnostics visible as text or JSON output. Test execution is approval-gated because Composer scripts execute project-defined code. Dependency audit is approval-gated because Composer checks installed packages against Packagist or configured repository advisory data. Requires composer on PATH.

API capability pack for bounded Confluence Cloud REST API v2 operations through Atlassian OAuth at https://api.atlassian.com only. Lists accessible Atlassian resources to discover cloud IDs, then reads and manages Confluence spaces, pages, blog posts, labels, attachments, comments, tasks, content properties, hierarchy, versions, and custom content for daily company knowledge-base work. All 39 cursor-bearing list operations walk Confluence pagination through the admitted OAuth-proxy path, and every included contract parameter that stays inside the bounded policy is exposed. The read-only task Source requests storage bodies while excluding blank tasks. Bundles a scheduled space activity brief, an AI-assisted page review brief, and an approval-gated page draft/create workflow. Enroll an Atlassian OAuth access token connection as bearer auth; no credential is embedded in the manifest. Writes are approval-gated and limited to one page, blog post, comment, task, space, or content property at a time. All delete operations are always-confirm destructive: comment and property deletion is permanent, and draft page/blog-post deletion is permanent even though purge is not exposed. The pack intentionally excludes user invites/access checks, admin-key endpoints, space permission/role/access-configuration changes and private-space creation, page ownership transfer, server-authored task audit fields, response-metadata writes, classification-level changes, redactions, file upload/download bodies, attachment deletion, custom-content mutation, whiteboard/database/smart-link mutation, purge parameters, bulk permission transitions, GraphQL/CQL passthrough, and arbitrary endpoint passthrough.

Workflow pack for Recued-created replies to existing Confluence inline comments. It composes the Confluence capability pack with a closure ledger: add one owner-approved storage-format reply to an existing inline comment on a configured page, persist only the connection/cloud/page/comment/reply linkage in data.shared, and let a scheduled watcher re-read that page's inline comments until Confluence reports the root comment resolved, no longer returns the comment, or the page reaches a configured terminal status. This pack does not replace Confluence inline comments, resolved-state controls, native notifications, tasks, page/blog workflows, page properties, automations, labels, permissions, or space governance; it adds Recued-visible closure state for inline-comment replies Recued created.

One-install Confluent Cloud front door over 11 bounded capability packs and 89 non-chat, uncached, read-only workflows. It reconciles all 497 official operations across 293 paths into 489 current callable capabilities, seven exact provider-deprecated exclusions, and one exact binary-upload transport exclusion. Control-plane identity, networking, clusters, quotas, connectors, artifacts, notifications, sharing, billing, Tableflow, RTCE, Kafka, Schema Registry, Data Catalog, Flink SQL, Partner APIs, and STS are covered. The mutable official OpenAPI URL must retain 2,653,460 bytes and SHA-256 0803fa3bd07e311d202b878cda9cb02e5ac9cab414a02cbe22910ab67e492e95 before regeneration. Seven separate connection profiles preserve Confluent's Cloud-key, resource-key, partner-bearer, no-auth STS, and dynamic Kafka, Schema Registry, and Flink endpoint boundaries. Seventy-one opaque-token collections paginate automatically without inventing provider page-size limits; page_size is withheld because Confluent says it is first-request-only and dynamically bounded. Two image downloads become private file_refs. Nine exporter responses that advertise only vendor +json remain explicit text. All 164 JSON bodies are required and sent verbatim; STS form fields are structured with fixed RFC 8693 constants. Parameter arrays use an explicit Recued 256-item safety ceiling without claiming a vendor maximum. Reads are uncached and not approval-gated, every mutation requires approval, unsafe integers remain exact strings, and no task, note, or user-work project Source is invented for infrastructure or streaming resources.

Confluent Cloud Kafka, ksqlDB, Schema Registry, and Flink control-plane clusters, compute pools, regions, client and service quotas, and BYOK keys. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 37 of the suite's 489 admitted current operations. The enrolled confluent-cloud connection supplies Cloud API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent managed connectors, connector lifecycle and offsets, Connect clusters and artifacts, custom plugins and runtimes, Flink artifacts, custom-code logging, and presigned uploads. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 55 of the suite's 489 admitted current operations. The enrolled confluent-cloud connection supplies Cloud API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Cloud API keys, users, service accounts, invitations, role bindings, SSO group mappings, identity providers and pools, certificate authorities, JWKS, IP groups, and IP filters. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 60 of the suite's 489 admitted current operations. The enrolled confluent-cloud connection supplies Cloud API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Cloud networks, access points, gateways, DNS, peerings, transit gateways, network links, PrivateLink access, and private-link attachments. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 64 of the suite's 489 admitted current operations. The enrolled confluent-cloud connection supplies Cloud API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent organizations and environments, notifications, integrations and subscriptions, Cluster Linking data exchange and shared tokens, provider and consumer shares, and billing costs. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 63 of the suite's 489 admitted current operations. The enrolled confluent-cloud connection supplies Cloud API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Flink SQL statements, results and exceptions, connections, materialized tables and versions, agents, and tools. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 29 of the suite's 489 admitted current operations. The enrolled confluent-flink connection supplies Flink resource API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Kafka cluster metadata, topics, partitions, records, ACLs, dynamic configs, consumer groups and lag, cluster links and mirrors, share groups, and Kafka Streams groups. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 75 of the suite's 489 admitted current operations. The enrolled confluent-kafka connection supplies Kafka resource API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Partner API signup, organizations, and entitlements using a separately enrolled partner OAuth bearer token. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 8 of the suite's 489 admitted current operations. The enrolled confluent-partner connection supplies partner OAuth access token through connection-owned Bearer authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Tableflow regions, topics, and catalog integrations plus Real-Time Context Engine regions and topics, using a resource API key at the control-plane origin. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 17 of the suite's 489 admitted current operations. The enrolled confluent-resource connection supplies resource API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Schema Registry subjects, schemas, compatibility, modes and configs, exporters, KEKs and DEKs, plus Data Catalog entities, tags, metadata definitions, and search. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 80 of the suite's 489 admitted current operations. The enrolled confluent-schema-registry connection supplies Schema Registry resource API key ID and secret through connection-owned HTTP Basic authentication and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

Confluent Security Token Service exchange of an external identity-provider JWT for a short-lived Confluent access token. Generated from Confluent's hash-locked aggregate OpenAPI 3.0.0 snapshot (0803fa3bd07e…) and carries 1 of the suite's 489 admitted current operations. The enrolled confluent-sts connection supplies an unauthenticated origin-pinning connection; token material stays in the request body and fixes the runtime origin; credentials never enter this pack. JSON bodies are required and sent verbatim, the one STS form owns its fixed token-type constants, unbounded integer parameters become exact strings, and parameter arrays carry a Recued 256-item safety ceiling that is not presented as a provider limit. Reads are uncached and not approval-gated; every mutation requires approval. Token collections walk automatically without inventing a stable provider page-size maximum. Vendor-only +json responses remain honest text, binary image reads become private file_refs, seven deprecated operations and one unsupported binary upload are absent, and no infrastructure or streaming resource is misrepresented as a task, note, or user-work project Source.

One-install Contentful CMA suite covering 319 of 320 unique official method/path routes from 320 hash-locked endpoint OpenAPI fragments. The 21-operation compatibility root preserves five shipped workflows and intentionally retains separate create-with-ID and update contracts over their shared official PUT route; five bounded dependency packs expose 299 additional routes. One raw-binary upload route fails closed because the REST transport cannot preserve arbitrary bytes. The endpoint corpus is generation evidence rather than a single-document OpenAPI pin; every new mutation requires approval, mutations preserve JSON through body_raw, proved pagination is bounded, and JSON integers are parsed losslessly.

Spaces, environments, organizations, security contacts, roles, memberships, credentials, usage, and observability. Generated from 320 hash-locked official endpoint OpenAPI fragments; no single-document OpenAPI pin is claimed.

App definitions, uploads, bundles, signing, keys, grants, installations, actions, functions, and logs. Generated from 320 hash-locked official endpoint OpenAPI fragments; no single-document OpenAPI pin is claimed.

AI actions and providers, automation, webhooks, comments, tasks, workflow definitions, and workflow execution. Generated from 320 hash-locked official endpoint OpenAPI fragments; no single-document OpenAPI pin is claimed.

Entries, assets, uploads, locales, tags, snapshots, scheduled actions, releases, timelines, and bulk content operations. Generated from 320 hash-locked official endpoint OpenAPI fragments; no single-document OpenAPI pin is claimed.

Content types, editor and UI configuration, templates, external references, taxonomy, and semantic content capabilities. Generated from 320 hash-locked official endpoint OpenAPI fragments; no single-document OpenAPI pin is claimed.

V3 deterministic CSV column-selection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local csvcut CLI returns selected columns from one trusted local CSV path via the csv.select catalog operation. This is the reproducible csvkit-backed fallback for qsv select while qsv lacks a Debian-stable package. Path-based by design: selected CSV rows are stdout value output, so this operation does not combine file_ref materialization with stdout capture. Requires csvkit on PATH (Debian/Ubuntu: apt install csvkit; Python environments: pip install csvkit). Local and no-egress.

V3 deterministic CSV row-search capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local csvgrep CLI returns rows from one trusted local CSV path where a named column matches a literal string via the csv.search catalog operation. This is the reproducible csvkit-backed fallback for qsv search while qsv lacks a Debian-stable package. Path-based by design: matching CSV rows are stdout value output, so this operation does not combine file_ref materialization with stdout capture. Requires csvkit on PATH (Debian/Ubuntu: apt install csvkit; Python environments: pip install csvkit). Local and no-egress.

V3 deterministic CSV validation capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local csvclean CLI validates one CSV file via the csv.validate catalog operation. This pack deliberately exposes a safe validator only: csvkit's transform tools mostly write transformed content to stdout, which is not a good fit for file_ref materialization and content-isolation. The operation materializes the source file, runs fixed csvclean structural checks, and captures no stdout/stderr value. Requires csvkit on PATH (Debian/Ubuntu: apt install csvkit; Python environments: pip install csvkit). Local and no-egress.

V3 deterministic CSV statistics capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local csvstat CLI summarizes one trusted local CSV path as JSON via the csv.stats catalog operation. This is the reproducible csvkit-backed fallback for qsv stats while qsv lacks a Debian-stable package. Path-based by design: stats are stdout value output, so this operation does not combine file_ref materialization with stdout capture. Requires csvkit on PATH (Debian/Ubuntu: apt install csvkit; Python environments: pip install csvkit). Local and no-egress.

V3 bounded HTTP inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local curl CLI ingredient exposes fixed operations for version readiness, HTTP status/timing, response headers, bounded text body retrieval, and bounded JSON body retrieval. Network operations require approval because they contact a caller-supplied URL, disclose executor network metadata to the remote host, and may reach private network services from the executor environment. The pack permits only http/https URLs, restricts curl and redirect protocols to http/https, disables curl config-file loading and URL glob expansion, caps redirects, connection time, total time, and advertised response size, and does not expose arbitrary methods, request headers, request bodies, uploads, output files, config files, local/file protocols, proxy settings, cookies, credentials, shell wrappers, or arbitrary curl flags. Requires curl on PATH.