Marketplace

One-install OneSignal REST API front door over app-key messaging/audience operations and a separate organization-key administration leaf. The suite publishes 51 executable operations covering 49 of 59 declared official contracts (46 of 56 distinct routes); the prior root exposed 15 operations. Version 2 preserves all 15 operation IDs and six workflow IDs while adding current message-channel, template, segment, custom-event, user, subscription, legacy-player, Live Activity, in-app-message, audit, app, and API-key metadata capabilities. 10 fail-closed exclusions cover secret-returning key issuance/rotation, credential-bearing app responses, export and history capabilities, URL-carried capability tokens, and one superseded token-registration route. The current official https://api.onesignal.com origin replaces the legacy /api/v1 enrollment base. App and organization keys are distinct connection slots because OneSignal assigns them different authority. The multi-document authority cannot be represented by one honest openapi_source; a hash-pinned generated fixture accounts for every current reference page plus the immutable legacy OpenAPI. Reads are uncached and not approval-gated, every mutation requires approval, unsafe JSON integers remain exact strings, provider credentials stay connection-owned, and no synced Source is claimed without live field-presence proof.

OneSignal organization-key operations for safe app inventory and creation, audit logs, API-key metadata/update/revocation, and cross-app template copy. This leaf carries 7 of the suite's 51 executable operations. App creation accepts only non-secret scalar metadata through a closed schema; push-provider credentials are intentionally unavailable. Key creation and rotation and credential-bearing app reads/updates remain excluded because their successful JSON responses contain secrets. Every read is uncached and not approval-gated, and every mutation requires approval.

No-auth API capability pack for recurring weather lookups through Open-Meteo. The pack exposes fixed current-condition and short forecast calls against https://api.open-meteo.com only; recipes provide latitude and longitude as query parameters, while the pack owns the host, path, weather-variable set, and timezone behavior. No credential is embedded or required.

One-install OpenAI front door over five bounded feature packs and four workflows. It admits 211 of 281 current official method/path operations from the hash-pinned OpenAPI 3.1 document. The compatibility root preserves all 10 prior operation IDs, routes, and argument keys while dependencies add 201 operations. Exact fail-closed exclusions cover the soon-to-shut-down Assistants and Evals platforms, Realtime and client-secret routes, multipart-only request bodies, beta duplicate paths, unsupported POST binary or streaming responses, undocumented or ambiguous content downloads, three API-key creation responses, and one required polymorphic credential-bearing request. Standard and Admin API keys remain separate connections. JSON requests are complete body_raw documents except where closed request subsets prevent streaming, credential-bearing nested tools, or variable binary media. The two legacy compatibility input arrays remain opaque and are therefore marked sensitive-read. Reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and unsafe JSON integers remain exact strings.

Bounded OpenAI files, containers, conversations, vector stores, uploads, videos, skills, and ChatKit thread operations. Generated from the current hash-pinned official OpenAI OpenAPI 3.1 document. This leaf carries 59 of the suite's 211 admitted operations. JSON request documents are sent verbatim except where a closed safe subset is required to prevent streaming, credential-bearing nested tools, or variable binary media. Unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and secret-returning routes stay excluded.

Bounded OpenAI model, Responses, Chat Completions, legacy Completions, embedding, moderation, image, and voice-consent operations. Generated from the current hash-pinned official OpenAI OpenAPI 3.1 document. This leaf carries 17 of the suite's 211 admitted operations. JSON request documents are sent verbatim except where a closed safe subset is required to prevent streaming, credential-bearing nested tools, or variable binary media. Unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and secret-returning routes stay excluded.

Privileged OpenAI organization projects, users, groups, roles, invites, spend alerts, permissions, service accounts, and redacted API-key inventory. Generated from the current hash-pinned official OpenAI OpenAPI 3.1 document. This leaf carries 84 of the suite's 211 admitted operations. JSON request documents are sent verbatim except where a closed safe subset is required to prevent streaming, credential-bearing nested tools, or variable binary media. Unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and secret-returning routes stay excluded.

Privileged OpenAI organization usage, costs, audit logs, certificates, and data-retention operations. Generated from the current hash-pinned official OpenAI OpenAPI 3.1 document. This leaf carries 26 of the suite's 211 admitted operations. JSON request documents are sent verbatim except where a closed safe subset is required to prevent streaming, credential-bearing nested tools, or variable binary media. Unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and secret-returning routes stay excluded.

Bounded OpenAI Batch and fine-tuning lifecycle operations, excluding the deprecated Evals platform and its alpha grader routes. Generated from the current hash-pinned official OpenAI OpenAPI 3.1 document. This leaf carries 15 of the suite's 211 admitted operations. JSON request documents are sent verbatim except where a closed safe subset is required to prevent streaming, credential-bearing nested tools, or variable binary media. Unsafe JSON integers remain exact strings, reads are uncached, sensitive reads are marked sensitive-read, every mutation requires approval, and secret-returning routes stay excluded.

API capability pack for bounded OpenRouter REST API operations against https://openrouter.ai/api/v1 only. Enroll an OpenRouter API key bearer connection named openrouter; no credential is embedded in this manifest. The pack reads model, endpoint, provider, current-key, credit, and generation metadata, and creates non-streaming chat completions for model routing, cost review, and AI operations workflows. It bundles a model routing brief, a chat completion brief, and a current-key usage brief. The pack intentionally excludes streaming, Responses/Messages compatibility routes, embeddings, image/audio/video generation, files, presets, guardrails, observability destinations, workspace and member administration, API key creation/update/delete, BYOK management, tools/plugins/server-tool routing, dynamic callback/webhook routing, arbitrary OpenRouter API passthrough, and any operation outside openrouter.ai/api/v1.

V3 deterministic file-digest capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local OpenSSL CLI ingredient exposes readiness plus fixed SHA-256, SHA-384, and SHA-512 digest operations. Fixed-function and reproducible: the executor materializes the source file and owns the throwaway output directory, while openssl writes fixed digest text files that are captured as result.file_ref. Write-tier but approval=never: openssl writes only to an engine-managed output dir, and source bytes never flow through op-step values. Recipes cannot call arbitrary OpenSSL subcommands, sign or verify files, compute HMAC/MAC values, pass provider/engine/password options, encrypt/decrypt content, or use shell redirection. Requires the openssl binary on PATH (Debian/Ubuntu: apt install openssl; macOS: openssl or LibreSSL is commonly installed with system tools). Local and no-egress.

V3 deterministic certificate-inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local OpenSSL CLI ingredient exposes readiness plus fixed X.509 inspection, subject, issuer/date, and 30-day expiry gate operations. The operations are path-based stdout text because the inspected certificate fields are the requested value output; this intentionally avoids combining file_ref materialization with value capture. Fixed-function and reproducible: no generic OpenSSL passthrough, no key generation, no signing, no certificate conversion, no CA/micro-CA options, no trust mutation, no password/provider/engine inputs, no network, and no arbitrary flags. Requires openssl on PATH (Debian/Ubuntu: apt install openssl; macOS: openssl or LibreSSL is commonly installed with system tools). Local and no-egress.

V3 multi-ecosystem dependency vulnerability scan capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local osv-scanner CLI ingredient exposes bounded project operations for readiness and recursive source dependency vulnerability scanning. The scan accepts one trusted source directory, returns OSV JSON findings, avoids caller-supplied OSV-Scanner flags, avoids shell wrappers, and never exposes guided fix/remediation, container image scan, caller-supplied config paths, HTML server, output-file writes, license-policy scan, call-analysis mode, offline database mutation, or arbitrary command execution. Approval is ask because dependency inventory is matched against OSV vulnerability data. Requires osv-scanner on PATH. Network egress to OSV data services.

End-to-end outbound follow-up workflow pack for one-person companies. It turns Email / Outbox into a repeatable loop: surface outbound threads that may need closure, draft concise follow-ups, send selected drafts through the mail-send approval boundary, and carry loop state through data.shared with links back to the source mail.

API capability pack for bounded Outlook mailbox-control operations through Microsoft Graph at https://graph.microsoft.com/v1.0 only. Enroll a Microsoft Graph OAuth bearer connection named microsoft with the narrowest Graph scopes needed for the installed operations. Reads the current user, mailbox settings, mail folders, inbox rules, Outlook categories, and Focused Inbox inference overrides. Writes are approval-gated and limited to automatic replies, locale/time/working-hours settings, mail-folder creation/rename/move/copy, inbox rule creation/update/delete with non-forwarding actions, Outlook category creation/update/delete, and Focused Inbox sender override creation/update/delete. The pack intentionally excludes generic message read/search/send/reply/forward/draft flows covered by first-class mail, attachment reads or writes, mailbox delete/permanentDelete, folder delete, rule forwarding/redirect/copy/delete/permanentDelete actions, shared-mailbox admin surfaces, subscriptions/webhooks, extended properties, and arbitrary Microsoft Graph passthrough.

One-install Outreach front door over three bounded domain packs and eight existing revenue-engagement workflows. The suite admits all 253 current method/path operations published in the hash-locked official OpenAPI contract: the 21-operation compatibility root preserves every prior ID and effective route while dependencies add 232 operations. Outreach does not include tenant custom-object schemas or CRUD routes in this public OpenAPI file, so the suite makes no custom-object completeness claim. All collection reads use the documented cursor links with bounded same-route replay. Legacy read filters are repaired to query.* wire keys, and every JSON:API mutation now takes a structured body.data object instead of non-buildable nested dotted keys. Bulk operations require an explicit filter, every mutation requires approval, sensitive new reads are marked sensitive-read, all reads are uncached, and response integers remain exact strings. Enroll an Outreach OAuth or S2S bearer connection at https://api.outreach.io.

Outreach accounts, prospects, opportunities, products, purchases, contact points, notes, stages, personas, and recipient records. Generated from the current hash-pinned official Outreach OpenAPI document and the first-party JSON:API request conventions. Reads are uncached; sensitive administrative reads are marked sensitive-read. Every mutation is grant-off and approval-gated, bulk actions require an explicit filter, JSON:API bodies are structured at body.data, and response integers remain exact strings.

Outreach tasks, mailboxes, sequences, sequence states and steps, calls, mailings, templates, snippets, rulesets, events, and Kaia activity. Generated from the current hash-pinned official Outreach OpenAPI document and the first-party JSON:API request conventions. Reads are uncached; sensitive administrative reads are marked sensitive-read. Every mutation is grant-off and approval-gated, bulk actions require an explicit filter, JSON:API bodies are structured at body.data, and response integers remain exact strings.

Outreach batches, imports, content governance, roles, teams, users, profiles, settings, audit logs, favorites, and webhooks. Generated from the current hash-pinned official Outreach OpenAPI document and the first-party JSON:API request conventions. Reads are uncached; sensitive administrative reads are marked sensitive-read. Every mutation is grant-off and approval-gated, bulk actions require an explicit filter, JSON:API bodies are structured at body.data, and response integers remain exact strings.

V3 deterministic PNG optimization capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local oxipng CLI writes an optimized PNG to a fixed engine-owned output path via image.optimize_png. This pack deliberately avoids in-place mutation by using oxipng's --out option. Write-tier but approval=never: oxipng writes only under {out_dir} and the optimized PNG is captured as result.file_ref. Requires oxipng on PATH (Alpine: apk add oxipng; Rust environments: cargo install oxipng). Local and no-egress.

API capability pack for bounded Paddle Billing REST operations against https://api.paddle.com. Enroll a paddle API connection as a bearer API-key connection with the narrowest Paddle permissions needed for the installed operations; no credential is embedded in this manifest. Reads catalog products/prices, customers, addresses, businesses, credit balances, discounts, subscriptions, transactions, adjustments, saved payment methods, reports, events, notifications, notification logs, and Paddle IP addresses. Writes are approval-gated and limited to product/price/customer/address/business/discount/discount-group maintenance and asynchronous report creation. Pricing, transaction, subscription-update, and subscription-charge preview endpoints are exposed as read-only preview calls because they do not mutate Paddle state. The pack intentionally excludes transaction creation/update/revision, adjustment/refund creation, subscription update/cancel/pause/resume/activate/charge, saved-payment-method deletion, customer auth tokens, customer portal sessions, client-side tokens, notification setting mutation, notification replay, simulations, webhook simulator replay, checkout-domain mutation, metrics, arbitrary API passthrough, and Paddle Classic APIs.

PagerDuty analytics, audit, IP allow lists, maintenance windows, session configuration, and standards. Generated from the complete hash-pinned official PagerDuty REST OpenAPI document. The US API base is the enrollment default; per-organization connections may target PagerDuty’s documented EU API base. Reads are uncached. Mutations are grant-off and approval-gated; administrative and destructive changes require approval every run.

Mollie balances, reports, transactions, settlements, invoices, and payout lifecycle operations. This feature pack is generated from the complete OpenAPI 3.1 document embedded in Mollie’s official list-balances reference page and hash-locked in the generated audit fixture as dc8f97e15f8efb2f2334e8d8b1665492d00c052270c20e9b9fc949c12bd6c1a6. The installed family carries 124 catalog operations covering 124 of 143 unique official routes with 19 exact fail-closed exclusions. New reads are uncached, mutations are grant-off and approval-gated, every new POST requires a caller-owned Idempotency-Key, JSON inputs are bounded, and unsafe response integers remain exact strings. Beta capabilities retain an explicit warning. No financial or control-plane object is misrepresented as a task, note, or project Source.

MongoDB Atlas federation, identity providers, LDAP, X.509, database users and roles, encryption at rest, auditing, and organization resource policies. Generated from MongoDB's hash-locked official Atlas Admin API v2 OpenAPI 3.0.1 snapshot (5040b0d3973e…) and carries 51 of the suite's 429 nondeprecated operations. Calls are fixed to cloud.mongodb.com and preserve each operation's exact versioned Accept and Content-Type media types. Use a MongoDB Atlas bearer connection containing a current OAuth2 service-account access token; the documented token lifetime is one hour, and this pack does not claim automatic client-credential exchange. Legacy Digest API keys are deliberately unsupported. JSON bodies remain verbatim, unsafe response integers remain exact strings, downloads become private file_refs, reads are uncached and not approval-gated, and every mutation requires approval. No infrastructure tenancy container is misrepresented as a task, note, or user-work project Source.

MongoDB Atlas service accounts, legacy programmatic API keys, AI model API keys and rate limits, and platform rate-limit inspection. Generated from MongoDB's hash-locked official Atlas Admin API v2 OpenAPI 3.0.1 snapshot (5040b0d3973e…) and carries 52 of the suite's 429 nondeprecated operations. Calls are fixed to cloud.mongodb.com and preserve each operation's exact versioned Accept and Content-Type media types. Use a MongoDB Atlas bearer connection containing a current OAuth2 service-account access token; the documented token lifetime is one hour, and this pack does not claim automatic client-credential exchange. Legacy Digest API keys are deliberately unsupported. JSON bodies remain verbatim, unsafe response integers remain exact strings, downloads become private file_refs, reads are uncached and not approval-gated, and every mutation requires approval. No infrastructure tenancy container is misrepresented as a task, note, or user-work project Source.

MongoDB Atlas dedicated and Flex clusters, global writes, cluster settings, maintenance, outage simulations, rolling indexes, and cloud migrations. Generated from MongoDB's hash-locked official Atlas Admin API v2 OpenAPI 3.0.1 snapshot (5040b0d3973e…) and carries 49 of the suite's 429 nondeprecated operations. Calls are fixed to cloud.mongodb.com and preserve each operation's exact versioned Accept and Content-Type media types. Use a MongoDB Atlas bearer connection containing a current OAuth2 service-account access token; the documented token lifetime is one hour, and this pack does not claim automatic client-credential exchange. Legacy Digest API keys are deliberately unsupported. JSON bodies remain verbatim, unsafe response integers remain exact strings, downloads become private file_refs, reads are uncached and not approval-gated, and every mutation requires approval. No infrastructure tenancy container is misrepresented as a task, note, or user-work project Source.

MongoDB Atlas cloud and Flex snapshots, restore and export jobs, backup compliance, collection restores, and online archives. Generated from MongoDB's hash-locked official Atlas Admin API v2 OpenAPI 3.0.1 snapshot (5040b0d3973e…) and carries 51 of the suite's 429 nondeprecated operations. Calls are fixed to cloud.mongodb.com and preserve each operation's exact versioned Accept and Content-Type media types. Use a MongoDB Atlas bearer connection containing a current OAuth2 service-account access token; the documented token lifetime is one hour, and this pack does not claim automatic client-credential exchange. Legacy Digest API keys are deliberately unsupported. JSON bodies remain verbatim, unsafe response integers remain exact strings, downloads become private file_refs, reads are uncached and not approval-gated, and every mutation requires approval. No infrastructure tenancy container is misrepresented as a task, note, or user-work project Source.

API capability pack for bounded monday.com Platform API GraphQL operations against https://api.monday.com. Enroll a monday connection that injects the documented Authorization bearer token and keep API-Version pinned to 2026-04; this manifest also pins API-Version as a static header on every operation. Reads the current user/account context, workspaces, users, teams, boards, board structure, groups, activity logs, items, item pages, and updates. Bundles a scheduled board digest, an AI-assisted item/board brief, and an approval-gated item intake workflow. Writes are approval-gated and limited to creating one board item, updating one item's column values, moving one item to a group, archiving one item, creating one item update/reply, or creating one board group at a time. The pack intentionally excludes arbitrary GraphQL passthrough, deletes, board creation/deletion, column/schema mutation, automation mutation, app/admin APIs, WorkForms, dashboards/widgets, docs mutation, file upload, bulk import/backfill jobs, notification sends, user invites/removals, permission edits, and account administration.

Workflow pack for Recued-created monday.com item updates. It composes the monday.com capability pack with a closure ledger: add one owner-approved update/comment to an existing monday.com item, persist only the connection/board/item/update linkage in data.shared, and let a scheduled watcher re-read that exact item until monday.com reports the item archived, deleted, or moved into a configured terminal group. Archived or terminal-group items close the Recued row; deleted items are marked for owner review. This pack does not replace monday.com item updates, native automations, notifications, dashboards, groups, status columns, item archive controls, board permissions, WorkForms, docs, or general board reporting; it adds Recued-visible closure state for item updates Recued created.

V2 one-install Mollie front door over six bounded feature packs and seven official OpenAPI 3.1 documents. The visible compatibility root grows from 19 to 58 operations while preserving every established operation ID, route, argument, entity, risk, approval, result-path, cache, and recipe reference contract; compatibility calls gain lossless response parsing and only type-faithful closed request schemas. The installed family publishes 124 catalog operations covering 124 of 143 unique official routes; 19 deprecated, different-auth, or unbuildable signed routes fail closed. Root additions are action-only so the established read surface does not silently widen default grants; remaining reads and one reserved action per domain stay in the dependency leaves. Every new mutation requires approval, reads are uncached, money movement and irreversible lifecycle actions are destructive, and every new POST requires a caller-owned Mollie Idempotency-Key. Bearer authorization remains connection-owned, JSON inputs are bounded, opaque HAL pagination remains explicit and manual, and unsafe response integers stay exact strings. The official ReadMe host exposes each complete schema in public server-rendered page data rather than at a stable raw OpenAPI URL, so the root and leaves omit misleading openapi_source fields while the generated fixture hash-locks every extracted document. No financial or control-plane object is claimed as a task, note, or project Source.

Mollie sales invoice creation, listing, retrieval, updates, and deletion. This feature pack is generated from the complete OpenAPI 3.1 document embedded in Mollie’s official create-sales-invoice reference page and hash-locked in the generated audit fixture as 09254cb73aea39a7c0134c8d1ce0755929d8a32c35c73049329bc4e32bf74668. The installed family carries 124 catalog operations covering 124 of 143 unique official routes with 19 exact fail-closed exclusions. New reads are uncached, mutations are grant-off and approval-gated, every new POST requires a caller-owned Idempotency-Key, JSON inputs are bounded, and unsafe response integers remain exact strings. Beta capabilities retain an explicit warning. No financial or control-plane object is misrepresented as a task, note, or project Source.

Mollie customers, customer payments, mandates, subscriptions, and subscription payment history. This feature pack is generated from the complete OpenAPI 3.1 document embedded in Mollie’s official create-customer reference page and hash-locked in the generated audit fixture as b8b44a106b3d6936fe65484ff88d3f68abcde735d1a4fa7a88a654c5a1111b5c. The installed family carries 124 catalog operations covering 124 of 143 unique official routes with 19 exact fail-closed exclusions. New reads are uncached, mutations are grant-off and approval-gated, every new POST requires a caller-owned Idempotency-Key, JSON inputs are bounded, and unsafe response integers remain exact strings. Beta capabilities retain an explicit warning. No financial or control-plane object is misrepresented as a task, note, or project Source.

Mollie permissions, organizations, profiles, clients, webhooks, events, onboarding status, capabilities, and Connect balance transfers. This feature pack is generated from the complete OpenAPI 3.1 document embedded in Mollie’s official get-organization reference page and hash-locked in the generated audit fixture as f1d8fb8f39a893d882e495044a020215ccadc925efa85311db08d8c3b03c5b5a. The installed family carries 124 catalog operations covering 124 of 143 unique official routes with 19 exact fail-closed exclusions. New reads are uncached, mutations are grant-off and approval-gated, every new POST requires a caller-owned Idempotency-Key, JSON inputs are bounded, and unsafe response integers remain exact strings. Beta capabilities retain an explicit warning. No financial or control-plane object is misrepresented as a task, note, or project Source.

Mollie business accounts, account transactions, transfer status, and Verification of Payee. This feature pack is generated from the complete OpenAPI 3.1 document embedded in Mollie’s official list-business-accounts reference page and hash-locked in the generated audit fixture as c723df47567e2907365fcc84955b6a1ca39a1ae01894f8445ecf3f0656f55370. The installed family carries 124 catalog operations covering 124 of 143 unique official routes with 19 exact fail-closed exclusions. New reads are uncached, mutations are grant-off and approval-gated, every new POST requires a caller-owned Idempotency-Key, JSON inputs are bounded, and unsafe response integers remain exact strings. Beta capabilities retain an explicit warning. No financial or control-plane object is misrepresented as a task, note, or project Source.

Mollie payments, methods, refunds, captures, payment links, terminals, payment routes, unmatched transfers, and checkout sessions. This feature pack is generated from the complete OpenAPI 3.1 document embedded in Mollie’s official create-payment reference page and hash-locked in the generated audit fixture as e1938893664e6df907ceab731f42e10cb49666ad22e423f9709d537bb6d99911. The installed family carries 124 catalog operations covering 124 of 143 unique official routes with 19 exact fail-closed exclusions. New reads are uncached, mutations are grant-off and approval-gated, every new POST requires a caller-owned Idempotency-Key, JSON inputs are bounded, and unsafe response integers remain exact strings. Beta capabilities retain an explicit warning. No financial or control-plane object is misrepresented as a task, note, or project Source.

API capability pack for bounded Mistral AI REST API operations against https://api.mistral.ai only. Enroll a Mistral API key bearer connection named mistral; no credential is embedded in this manifest. The pack reads model metadata, non-streaming chat completion responses, text embeddings, moderation results, classification results, file metadata, batch jobs, fine-tuning jobs, and agent metadata for AI model evaluation, prompt review, safety checks, retrieval preparation, and operations monitoring. It bundles a chat completion brief, a safety and classification brief, a scheduled model/job operations digest, and approval-gated workflows for canceling one batch job or one fine-tuning job. Writes are limited to canceling one existing batch job or one existing fine-tuning job. The pack intentionally excludes streaming endpoints, file upload/content/url/delete operations, OCR and audio upload/speech endpoints, workflow execution and scheduling, admin APIs, connectors and connector credentials, observability dataset mutation, RAG index mutation, library/document mutation, agent creation or update, fine-tuning create/start/archive/delete, batch job creation, arbitrary tool-bearing chat arguments, arbitrary Mistral API passthrough, and dynamic outbound callback routing.

API capability pack for bounded Miro REST API operations against https://api.miro.com only. Enroll a miro OAuth bearer connection; no credential is embedded in this manifest. The pack reads OAuth token context, boards, board members, board items, sticky notes, text, shapes, cards, app cards, frames, connectors, document/image/embed URL items, tags, and groups for collaborative planning, workshop capture, and design-to-execution workflows. Approval-gated writes are limited to creating/copying/updating boards, sharing or changing access for explicit board members, moving items, creating/updating common board items, creating/updating connectors, creating/updating tags, and creating/updating URL-backed document/embed/image items. Deletes, local file uploads, bulk item creation from files, OAuth token revocation, SCIM, org/team/user/group administration, enterprise audit/content logs, board exports, legal holds, data-classification administration, app metrics, experimental APIs, webhooks, and arbitrary Miro endpoints are intentionally not exposed.

V3 deterministic Minisign verification capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local minisign CLI ingredient exposes readiness plus fixed detached-signature verification with an inline public key, a trusted public-key file, or strict prehashed-signature mode. This pack is verification-only: no signing, key generation, key recreation, password changes, secret-key access, arbitrary flags, content output passthrough, or shell wrappers. Verification operations are exit-code-only; a zero exit code means the signature verified. Requires minisign on PATH (Debian/Ubuntu: apt install minisign; macOS: brew install minisign). Local and no-egress.

API capability pack for bounded Microsoft To Do operations through Microsoft Graph at https://graph.microsoft.com/v1.0 only. Enroll a Microsoft Graph OAuth bearer connection named microsoft with the narrowest Graph Tasks scopes needed for the installed operations. Reads the current user, To Do task lists, tasks, checklist items, and linked resources. Bundles a scheduled task-list digest, an AI-assisted task brief, and an approval-gated task intake workflow with optional checklist items and linked source metadata. Writes are approval-gated and limited to creating a task list, creating/updating one task, creating/updating checklist items, and creating linked resources. The pack intentionally excludes task/list/checklist deletes, attachments, open extensions, delta-sync cursors, shared-mailbox/user impersonation routes, Outlook category mutation, reminders/recurrence templates beyond raw task fields, and arbitrary Microsoft Graph passthrough.

Workflow pack for Recued-created Microsoft To Do tasks. It composes the Microsoft To Do capability pack with a closure ledger: create one owner-approved task in an existing task list, persist only the connection/list/task linkage in data.shared, and let a scheduled watcher re-read that exact task until Microsoft To Do reports completion. This pack does not replace Microsoft To Do reminders, categories, checklist items, linked resources, daily digests, Outlook task surfaces, shared-list permissions, attachments, open extensions, or general task dashboards; it adds Recued-visible closure state for To Do tasks Recued created.

API capability pack for bounded Microsoft Intune endpoint-management operations through Microsoft Graph at https://graph.microsoft.com/v1.0 only. Enroll a Microsoft Graph OAuth bearer connection named microsoft with least-privilege Intune Graph scopes for the installed operations. The pack reads managed devices, detected apps, compliance policies, device configuration profiles, mobile apps, and Intune audit events for device compliance triage, endpoint inventory review, and help-desk action context. It bundles a scheduled device compliance digest, an AI-assisted device brief, and approval-gated workflows for syncing one managed device or remotely locking one managed device. The pack intentionally excludes wipe, retire, delete, reboot, shutdown, passcode recovery or reset, activation-lock bypass, lost-mode, remote assistance, Windows Defender scan/signature actions, Autopilot mutation, app or policy mutation, role/admin changes, beta endpoints, arbitrary Graph passthrough, and credential-bearing fields in operation arguments.

API capability pack for bounded Microsoft Entra ID operations through Microsoft Graph at https://graph.microsoft.com/v1.0 only. Enroll a Microsoft Graph OAuth bearer connection named microsoft with least-privilege Graph scopes for the installed operations. The pack reads users, groups, group members, applications, service principals, directory audit logs, and sign-in logs for access governance, offboarding review, and identity incident triage. It bundles a scheduled access hygiene digest, an AI-assisted user access brief, and approval-gated workflows for disabling/enabling one user and adding/removing one user from one group. The pack intentionally excludes user creation/deletion, password reset/change, MFA/authentication method mutation, role/admin assignment, app credential/secret/key mutation, application/service-principal creation or deletion, conditional access/policy mutation, device deletion, license assignment, mailbox/file/calendar surfaces, arbitrary Graph passthrough, and beta endpoints.

API capability pack for bounded Microsoft Defender for Endpoint operations against https://api.security.microsoft.com. Enroll a Microsoft Defender for Endpoint OAuth bearer connection named microsoft-defender with least-privilege WindowsDefenderATP API permissions for the installed operations. The pack reads alerts, machines, machine-related alerts, logon users, machine actions, exposure score, security recommendations, and vulnerability information for endpoint security triage, vulnerability review, and incident response context. It bundles a scheduled endpoint security digest, an AI-assisted machine investigation brief, and approval-gated workflows for isolating one machine, releasing one machine from isolation, or updating one alert. The pack intentionally excludes advanced hunting query passthrough, live response, offboarding, antivirus scan actions, file quarantine/stop actions, package collection, cancel action, machine tag mutation, indicator creation/deletion, alert creation, bulk alert update, raw tenant export/download endpoints, arbitrary Defender API passthrough, and credential-bearing fields in operation arguments.

One-install Mercury API capability pack over accounts, balances, transactions, statements and PDF capture, credit and Treasury, cards, recipients and approval requests, accounts receivable, categories, events, users, SAFEs, and Mercury Books. Read groups install by default; every mutation needs an explicit capability grant, all mutations still ask for approval, and money movement, payment requests, deletions, and cancellations require approval every run. The pack uses Mercury's bearer-token flow, supports cursor, offset, and page-token pagination, and bundles seven operating briefs plus four guarded intakes/actions. It intentionally excludes multipart attachment upload, partner onboarding, and webhook endpoints whose documented responses expose signing secrets; it never accepts credentials or arbitrary paths as arguments.

V3 deterministic media-metadata capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local mediainfo CLI ingredient exposes readiness, supported-parameter discovery, human-readable media inspection, and JSON metadata for one trusted local media/document path. The metadata operations are read-only and path-based stdout values because the metadata itself is the requested output; they intentionally do not combine file_ref materialization with stdout capture. Requires mediainfo on PATH (Debian/Ubuntu: apt install mediainfo; macOS: brew install media-info). Local and no-egress; no shell wrapper, arbitrary MediaInfo flags, recursive directory scan, remote URL fetch, or file output path is exposed.

API capability pack for bounded Maxio Advanced Billing REST operations. Enroll a maxio connection with base_url set to the tenant site host, for example https://acme.chargify.com for US sites or https://acme.ebilling.maxio.com for EU sites; the manifest uses https://example.chargify.com as the template host following the tenant-host pack pattern. The connection must use Maxio Basic Auth with API key as username and x as password. Reads site settings, revenue stats, MRR, customers, subscriptions, products, product families, components, subscription components, allocations, usages, invoices, credit notes, coupons, and events for billing operations, subscription support, usage billing, and revenue review. Approval-gated writes are limited to creating one customer, creating one subscription, previewing or creating one invoice, creating one usage record, creating one component allocation, applying one coupon, or removing one coupon at a time. The pack intentionally excludes arbitrary endpoint passthrough, payment profile and raw card/bank handling, refunds, external payment recording, invoice void/reopen/issue/send actions, customer/subscription/product/component/coupon deletion or archival, site clearing, webhooks, API key administration, event-based-billing bulk ingestion, subscription purge, and destructive cleanup workflows.

V3 Maven CLI toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local mvn CLI ingredient exposes bounded project operations for readiness, compile checking, and test execution. Project operations run from an explicit project directory cwd supplied at execution time, use Maven batch mode, suppress transfer progress and snapshot update checks, avoid caller-supplied Maven goals/profiles/properties/settings/toolchains/module selectors, avoid wrapper scripts and shell wrappers, and keep diagnostics visible as text output. Compile and test operations are approval-gated because Maven may resolve dependencies and plugins, execute build plugins, compile project code, run tests, and write target directories or local Maven cache entries. Requires mvn on PATH.

V3 deterministic document-to-Markdown capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local markitdown CLI converts one source document into Markdown via the document.to_markdown catalog operation. This is a lighter alternative to docling for simple office/document inputs. Write-tier but approval=never: markitdown writes only to an engine-managed throwaway output dir and the Markdown is captured as result.file_ref; source bytes and converted text never flow through op-step stdout values. Requires markitdown on PATH (Python environments: pip install markitdown==0.1.3 or a compatible installed CLI). Local and no-egress; Document Intelligence and plugin flags are not exposed.