Marketplace

V3 Cloudflare Tunnel capability pack. The callable surface is a by-value cli composition, not a service ingredient: recipes launch `cloudflared tunnel run <tunnel_name>` as a Recued-managed detached job and reconcile marker/log/pid evidence from the declared result directory. Two postures for the long-running tunnel: enroll it from pack-detail as a supervised daemon (the op declares supervision — restart-on-crash + re-launch-on-server-start), or launch it fire-and-forget from a recipe as a D-179 user-space job that records marker/log/pid evidence, with silent death detected by downstream sweeper recipes through missing or non-zero marker evidence. Requires the cloudflared binary on PATH and a pre-created tunnel.

One-install CockroachDB Cloud front door over 4 bounded capability packs and 64 non-chat, uncached, read-only workflows. It reconciles all 144 official operations across 74 paths into 139 current callable capabilities and five exact provider-deprecated exclusions. The mutable latest OpenAPI and the official Cloud API guide are independently hash-locked. A single connection-owned Bearer secret stays pinned to cockroachlabs.cloud. The date-based Cc-Version header is fixed to 2024-09-16 only on /api/v1; SCIM v2 remains standards-shaped. Twenty-one collection operations paginate automatically. Role grants and two raw-body SCIM searches remain explicitly caller-paged where the current follower cannot merge without information loss. All 54 JSON bodies are required and sent verbatim, response integers are preserved exactly, and every mutation requires approval. The POST-shaped restore is explicitly destructive rather than falling through to generic administration. API-key creation is the only response that returns a full recoverable credential and, as a mutation, has no bundled workflow; the formatted connection-string read contains no password and Datadog returns only the last four key digits. No infrastructure, identity, or billing object is misrepresented as a task, note, or user-work project Source.

CockroachDB Cloud API keys, service accounts, role grants, folders, JWT issuers, organization details, billing, and audit logs. Generated from Cockroach Labs' hash-locked 2024-09-16 OpenAPI snapshot and carries 31 of 139 current operations. The enrolled cockroachdb-cloud connection supplies a service-account secret through connection-owned Bearer authentication at cockroachlabs.cloud. Every /api/v1 request fixes Cc-Version to 2024-09-16; SCIM v2 requests deliberately omit that v1-only header. Required JSON bodies are sent verbatim, parsed JSON preserves unsafe integers as exact strings, reads are uncached, every mutation requires approval, and no task, note, or user-work project Source is invented for cloud infrastructure or identity administration.

CockroachDB Cloud clusters, versions, databases, SQL users, backups, restores, maintenance, blackout windows, client CAs, CMEK, disruption, and version deferral. Generated from Cockroach Labs' hash-locked 2024-09-16 OpenAPI snapshot and carries 44 of 139 current operations. The enrolled cockroachdb-cloud connection supplies a service-account secret through connection-owned Bearer authentication at cockroachlabs.cloud. Every /api/v1 request fixes Cc-Version to 2024-09-16; SCIM v2 requests deliberately omit that v1-only header. Required JSON bodies are sent verbatim, parsed JSON preserves unsafe integers as exact strings, reads are uncached, every mutation requires approval, and no task, note, or user-work project Source is invented for cloud infrastructure or identity administration.

CockroachDB Cloud IP allowlists, private endpoints, egress policy, metric and log export, and physical cluster replication. Generated from Cockroach Labs' hash-locked 2024-09-16 OpenAPI snapshot and carries 43 of 139 current operations. The enrolled cockroachdb-cloud connection supplies a service-account secret through connection-owned Bearer authentication at cockroachlabs.cloud. Every /api/v1 request fixes Cc-Version to 2024-09-16; SCIM v2 requests deliberately omit that v1-only header. Required JSON bodies are sent verbatim, parsed JSON preserves unsafe integers as exact strings, reads are uncached, every mutation requires approval, and no task, note, or user-work project Source is invented for cloud infrastructure or identity administration.

CockroachDB Cloud SCIM v2 users, groups, schemas, resource types, and service-provider configuration. Generated from Cockroach Labs' hash-locked 2024-09-16 OpenAPI snapshot and carries 21 of 139 current operations. The enrolled cockroachdb-cloud connection supplies a service-account secret through connection-owned Bearer authentication at cockroachlabs.cloud. Every /api/v1 request fixes Cc-Version to 2024-09-16; SCIM v2 requests deliberately omit that v1-only header. Required JSON bodies are sent verbatim, parsed JSON preserves unsafe integers as exact strings, reads are uncached, every mutation requires approval, and no task, note, or user-work project Source is invented for cloud infrastructure or identity administration.

API capability pack for bounded Coda API v1 operations against https://coda.io/apis/v1 only. Enroll a Coda API token connection that injects the documented Authorization bearer header; no credential is embedded in this manifest. The pack reads token identity, docs, pages, tables, columns, rows, formulas, controls, and mutation status, and it exposes Coda's documented limit and pageToken list parameters for manual pagination. It creates or updates one doc, page, or table row at a time through approval-gated operations, with recipes for doc structure review, table row review, row upsert intake, and page intake. Writes are limited to doc create/update, page create/update, and row insert/upsert/update. The pack intentionally excludes deletes, sharing and ACL changes, publishing controls, page content export/download links, webhooks, packs/admin APIs, arbitrary API passthrough, and bulk destructive actions.

One-install Coder front door over 8 bounded official domain packs and 8 non-chat, uncached, read-only workflows. It admits 330 of 371 operations from the official Coder API v2.34.6 Swagger at commit 660dc564f5217ea9d1489cc0816e661f7ec0d15d. Forty-one exact operations are excluded because their protocol, browser, media, authentication, removal, or no-success semantics cannot be represented faithfully. The surface spans workspaces, builds, templates, agents, runtime files, users, organizations, notifications, audit, insights, AI chats and tasks, enterprise administration, OAuth management, and SCIM provisioning. Enroll the main API with Coder-Session-Token and SCIM separately with Authorization. Raw JSON, decimal-string selectors, and exact-integer response parsing preserve wire values. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. Coder AI tasks are exposed as one documentary-proven, read-only, owner-filtered task Source.

Coder finite agent, application, file-download, Git, initialization, provisioning, and proxy operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 28 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder AI Bridge, provider, finite chat, AI-task, task-log, and task-control operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 38 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder enterprise configuration, licensing, groups, deployment controls, OAuth-provider management, and finite administration operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 76 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder notification, insight, audit, general discovery, health, metrics, and finite debug operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 45 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder SCIM service discovery and finite user provisioning operations using the deployment SCIM shared secret. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 5 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the complete deployment SCIM shared-secret value in Authorization. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder template, template-version, dry-run, parameter, preset, and ACL operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 35 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder user, organization, member, authorization, API-token, preference, and secret operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 68 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

Coder workspace lifecycle, build, port-sharing, and prebuild operations. Generated from Coder API v2.34.6 at an immutable official repository commit. This leaf carries 35 of the suite's 330 admitted operations. Enroll a Coder deployment at its HTTPS origin; store the session token in Coder-Session-Token. JSON request documents are sent verbatim, 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 long-lived protocol modes are excluded or fixed to finite snapshots.

One-install Ashby front door over 7 bounded capability packs and 29 non-chat read workflows. It admits 171 current representable outbound operations from 177 official focus contracts and records 6 directional or deprecated exclusions. 27 inbound webhook pages remain provenance-recorded without being misrepresented as outbound calls. Coverage includes candidates and projects; applications, feedback, approvals, and referrals; jobs, postings, and openings; interviews and scheduling; offers, surveys, and reports; organization structure; custom fields, files, audit events, sources, and webhook settings. Basic API-key credentials remain connection-owned; reads are uncached and permission-scoped, sensitive reads are marked sensitive-read, and every mutation is grant-off and approval-gated.

Ashby jobs, job boards and postings, requisition openings, interview-plan metadata, and job templates. Generated from Ashby's complete current outbound API surface in the official machine-readable reference index: every focus page is reconciled to an emitted operation or a concrete directional/deprecation exclusion, with raw Markdown and embedded OpenAPI hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Ashby publishes Markdown-wrapped per-reference contracts rather than one directly fetchable OpenAPI document. Reads are uncached and permission-scoped; reads over sensitive recruiting data are marked sensitive-read. Every mutation is grant-off and approval-gated. Ashby can report application errors as HTTP 200 with success:false, so operations preserve the full response envelope and workflows disclose provider success/error state. No work-entity Source is declared because Ashby's actual Project contract does not prove a mandatory version field.

Ashby offer processes and decisions, survey definitions and submissions, and synchronous or asynchronous reports. Generated from Ashby's complete current outbound API surface in the official machine-readable reference index: every focus page is reconciled to an emitted operation or a concrete directional/deprecation exclusion, with raw Markdown and embedded OpenAPI hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Ashby publishes Markdown-wrapped per-reference contracts rather than one directly fetchable OpenAPI document. Reads are uncached and permission-scoped; reads over sensitive recruiting data are marked sensitive-read. Every mutation is grant-off and approval-gated. Ashby can report application errors as HTTP 200 with success:false, so operations preserve the full response envelope and workflows disclose provider success/error state. No work-entity Source is declared because Ashby's actual Project contract does not prove a mandatory version field.

Ashby users, interviewer availability, departments and teams, locations, hiring teams, and organization structure. Generated from Ashby's complete current outbound API surface in the official machine-readable reference index: every focus page is reconciled to an emitted operation or a concrete directional/deprecation exclusion, with raw Markdown and embedded OpenAPI hashes retained in the audit fixture. A single openapi_source is intentionally omitted because Ashby publishes Markdown-wrapped per-reference contracts rather than one directly fetchable OpenAPI document. Reads are uncached and permission-scoped; reads over sensitive recruiting data are marked sensitive-read. Every mutation is grant-off and approval-gated. Ashby can report application errors as HTTP 200 with success:false, so operations preserve the full response envelope and workflows disclose provider success/error state. No work-entity Source is declared because Ashby's actual Project contract does not prove a mandatory version field.

API capability pack for bounded AssemblyAI REST API operations against https://api.assemblyai.com only. Enroll an AssemblyAI API key connection named assemblyai that injects the Authorization header; no credential is embedded in this manifest. The pack lists transcript jobs, creates one pre-recorded transcript job for an explicit media audio_url, reads transcript status and results, exports sentences and paragraphs, searches transcript words, exports subtitles, and retrieves redacted-audio metadata for meeting notes, call analytics, media intelligence, podcast review, accessibility, and RAG preparation. Writes are limited to submitting one transcription job and require approval. The pack intentionally excludes binary upload, transcript deletion, webhooks and callback URLs, streaming WebSocket APIs, streaming-token generation, voice-agent APIs, agent/webhook management, separate LLM Gateway host calls, EU-region host switching, arbitrary AssemblyAI API passthrough, dynamic outbound callbacks, and any operation outside api.assemblyai.com.

One-install Attio REST API v2 suite with 79 declared operations covering 73 of 75 official method/path routes from the hash-locked public OpenAPI 3.1 contract. The 20-operation compatibility surface and all nine shipped workflows remain addressable; six create workflows move to version 2 because their formerly dotted nested body keys were serialized literally and could not produce Attio's required data object. Records, schema, lists, entries, members, notes, tasks, comments, meetings, call recordings, transcripts, file metadata, webhooks, SQL, and workspace identity are admitted. Multipart binary upload and a signed-download redirect whose target origin is not contractually pinned fail closed because the current REST transport cannot represent them without weakening byte fidelity or origin-pinning security. Reads are approval-free at the read floor and newly admitted mutations require approval every run; JSON bodies remain exact through body_raw, documented pagination is bounded, and unsafe JSON integers remain exact strings.

API capability pack for bounded Auth0 Management API v2 operations. Enroll an auth0 API connection with base_url set to the tenant Management API root, for example https://example.auth0.com/api/v2, and authenticate with a Management API bearer token scoped to the installed operations. The pack reads users, user roles, user permissions, user organizations, tenants roles, clients, organizations, organization members, and logs for access governance, account triage, and identity incident review. It bundles a scheduled access hygiene digest, an AI-assisted user access brief, and approval-gated workflows for blocking/unblocking one user and assigning/removing roles for one user. The pack intentionally excludes user creation, deletion, password changes, MFA/enrollment/recovery flows, refresh-token/session revocation, connection/client/organization/role creation or deletion, resource-server and tenant mutation, domain/email-template/branding/actions/rules/jobs/key/secret administration, log export, Guardian/attack-protection mutation, and arbitrary API passthrough.

ACC account companies, account users, imports, roles, products, and business-unit structure operations. Generated from Autodesk's immutable commit-pinned official Autodesk Construction Cloud Account Administration OpenAPI schema. This leaf carries 18 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

ACC issue profiles, types, attributes, root causes, issues, comments, and attachment-reference operations. Generated from Autodesk's immutable commit-pinned official Autodesk Construction Cloud Issues OpenAPI schema. This leaf carries 14 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

ACC project portfolio, project details, project membership, product access, and project-role operations. Generated from Autodesk's immutable commit-pinned official Autodesk Construction Cloud Account Administration OpenAPI schema. This leaf carries 10 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

One-install Autodesk front door over 8 bounded official domain packs and 8 non-chat, uncached, read-only workflows. It admits 105 of 146 operations from all 8 schemas in Autodesk's official OpenAPI repository at commit 84312395ae1912104e6b52813df0900fb4ed4818. Forty-one explicit exclusions cover OAuth/secret lifecycle, one unsupported HEAD binding, two binary image uploads, and application-only OSS, Secure Service Account, and app-wide webhook operations that cannot run honestly through the current user-delegated connection. The admitted surface covers ACC project/account administration and issues plus APS identity, Data Management, Model Derivative, and webhook administration. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval, unsafe JSON integers remain exact, and every leaf is pinned to its immutable official schema. No task, note, or project Source is claimed without live field-path proof.

Autodesk item, version, relationship, reference, download-format, and command operations. Generated from Autodesk's immutable commit-pinned official Autodesk Platform Services Data Management OpenAPI schema. This leaf carries 21 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

Autodesk hubs, projects, top folders, folder contents, storage, downloads, and folder relationship operations. Generated from Autodesk's immutable commit-pinned official Autodesk Platform Services Data Management OpenAPI schema. This leaf carries 20 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

Current-user identity plus public OpenID configuration and signing-key discovery. Generated from Autodesk's immutable commit-pinned official Authentication OpenAPI schema. This leaf carries 3 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

Model translation, views, object trees, properties, thumbnails, manifests, derivative access, and references. Generated from Autodesk's immutable commit-pinned official Autodesk Platform Services Model Derivative OpenAPI schema. This leaf carries 11 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

Autodesk webhook inventory, detail, creation, update, and deletion operations without secret-token lifecycle exposure. Generated from Autodesk's immutable commit-pinned official Autodesk Platform Services Webhooks OpenAPI schema. This leaf carries 8 of the suite's 105 admitted user-delegated operations. Reads are uncached; sensitive reads are marked sensitive-read and require approval unless session-granted, while ordinary reads remain unheld. Every mutation requires approval. Unsafe JSON integers remain exact strings, documented pagination is followed only through the original route, and no application-only or credential-lifecycle surface is represented as callable.

API capability pack for bounded Azure DevOps Services REST API operations against https://dev.azure.com only. Reads projects, repositories, commits, pull requests, pull request threads, builds, WIQL work item queries, work items, and work item comments, and supports approval-gated pull request thread comments and work item comments. Bundles a scheduled project triage digest, an AI-assisted pull request review brief, an approval-gated pull request comment workflow, and an approval-gated work item comment workflow. Enroll an Azure DevOps OAuth or PAT-backed connection named azure-devops with the narrowest scopes needed for the installed operations. The pack intentionally excludes repository or branch mutation, file writes, pull request completion/abandon/vote/reviewer mutation, work item creation/update/delete, build queue/cancel, release/deployment APIs, service hooks, variable groups, permissions/admin APIs, test plans, and arbitrary API passthrough.

Workflow pack for Recued-created Azure DevOps pull request comments. It composes the Azure DevOps capability pack with a closure ledger: add one owner-approved top-level thread comment to an existing Azure DevOps pull request, persist only the connection/organization/project/repository/pull-request/thread linkage in data.shared, and let a scheduled watcher re-read that exact pull request until Azure DevOps reports it completed or abandoned. This pack does not replace Azure DevOps pull request comments, native notifications, review approvals, completion or abandon controls, branch policies, builds, service hooks, or general code review reporting; it adds Recued-visible closure state for pull request comments Recued created.

Workflow pack for Recued-created Azure DevOps work item comments. It composes the Azure DevOps capability pack with a closure ledger: add one owner-approved comment to an existing work item, persist only the connection/organization/project/work-item/comment linkage in data.shared, and let a scheduled watcher re-read that exact work item until Azure DevOps reports a configured terminal state such as done, closed, removed, or completed. This pack does not replace Azure DevOps work item comments, native notifications, state transitions, assignments, boards, queries, service hooks, or general work-item reporting; it adds Recued-visible closure state for work item comments Recued created.

API capability pack for bounded BambooHR v1 operations against a customer subdomain such as https://companySubDomain.bamboohr.com/api/v1. Enroll a BambooHR API key Basic Auth connection or OAuth bearer connection named bamboohr with employee, field, report, and time-off access. The pack reads employee directory records, employee detail fields, employee table rows, custom reports, field metadata, time-off types, time-off policies, who's-out coverage, and time-off requests for people operations digests, employee record briefs, onboarding checks, manager handoffs, and absence coverage review. It bundles a scheduled people-operations digest, AI-assisted employee and time-off coverage briefs, and approval-gated workflows for creating one employee profile and creating one non-superseding time-off request. Writes are limited to one employee or time-off request at a time. The pack intentionally excludes employee updates, table row mutation, file/photo upload or download, dependent/benefit/payroll mutation, time-off approvals/denials/history overrides/policy assignment, previous-request supersede, webhook administration, OAuth token generation, report definition mutation, and arbitrary BambooHR API passthrough.

V3 Python security-lint capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local bandit CLI ingredient exposes bounded project operations for readiness and Python security linting. Scans run from an explicit project directory cwd supplied at execution time, inspect one trusted Python file or directory for common security issues, and return JSON findings via the python.security_lint catalog operation. Fixed-function and reproducible: recursive scan, JSON output, low severity/confidence threshold, no caller-supplied config/profile/test/skip list, no baseline comparison, no output-file write, no stdin, no custom formatter/template, no shell wrapper, and no network egress. Findings are represented as successful JSON output; real invocation failures still fail. Requires bandit on PATH. Local and no-egress.

One-install Basecamp front door over four bounded domain packs and ten operating workflows. It admits all 200 JSON or bodyless routes from the 203-operation commit-pinned official contract. The three explicit exclusions are binary account-logo, attachment, and Campfire-upload bodies, which the current static JSON REST composition cannot serialize; their metadata, document, upload-record, and text-chat companions remain available. Basecamp documents int64 identifiers beyond JavaScript's safe-number range, so every JSON response preserves unsafe integer literals as exact decimal strings and int64 request identifiers travel from string-shaped inputs to exact JSON integer literals. A documentary read-only Todo Source walks active Todo recording references through safe RFC Link pagination and hydrates every row with a fresh flat Todo read before projection. Enroll Basecamp OAuth at launchpad.37signals.com, select the bc3 account returned by authorization, and store its numeric id in connection config as account_id for Source sync; workflows request the same account id explicitly. The connection owns bearer credentials and every call sends an identifying Recued User-Agent. Reads are uncached; every read except Source operations and bounded search/category metadata discovery is marked sensitive-read and requires approval unless session-granted. The remaining reads are unheld. Every mutation is grant-off and approval-gated. Two chat workflows use unmarked metadata reads only; project, Campfire, content, and activity reviews plus all writes are non-chat.

Basecamp people, profile, account, search, recording, questionnaire, template, webhook, tool, notification, lineup, and progress-report operations. Generated from Basecamp's commit-pinned official OpenAPI 3.1 contract. The OAuth connection owns the bearer token and fixed https://3.basecampapi.com origin; every operation requires an explicit numeric accountId target and sends Basecamp's mandatory identifying User-Agent. Read caching is disabled. Only bounded search metadata is unmarked and unheld; every other read is marked sensitive-read and requires approval unless session-granted. Unsafe 64-bit JSON identifiers are preserved as exact decimal strings, and int64 request identifiers are accepted as strings and serialized without numeric rounding. Every mutation is grant-off and approval-gated.

Basecamp messages, comments, Campfire chat, boosts, client collaboration, inbox forwards, and message-type operations. Generated from Basecamp's commit-pinned official OpenAPI 3.1 contract. The OAuth connection owns the bearer token and fixed https://3.basecampapi.com origin; every operation requires an explicit numeric accountId target and sends Basecamp's mandatory identifying User-Agent. Read caching is disabled. Only the bounded message-type directory read is unmarked and unheld; every other read is marked sensitive-read and requires approval unless session-granted. Unsafe 64-bit JSON identifiers are preserved as exact decimal strings, and int64 request identifiers are accepted as strings and serialized without numeric rounding. Every mutation is grant-off and approval-gated.

Basecamp document, upload metadata, version, folder, and vault operations over JSON-representable routes. Generated from Basecamp's commit-pinned official OpenAPI 3.1 contract. The OAuth connection owns the bearer token and fixed https://3.basecampapi.com origin; every operation requires an explicit numeric accountId target and sends Basecamp's mandatory identifying User-Agent. Read caching is disabled. Every document, upload-metadata, version, folder, and vault read is marked sensitive-read and requires approval unless session-granted. Unsafe 64-bit JSON identifiers are preserved as exact decimal strings, and int64 request identifiers are accepted as strings and serialized without numeric rounding. Every mutation is grant-off and approval-gated.

Basecamp project, to-do, assignment, schedule, timesheet, gauge, card-table, timeline, and work-report operations. Generated from Basecamp's commit-pinned official OpenAPI 3.1 contract. The OAuth connection owns the bearer token and fixed https://3.basecampapi.com origin; every operation requires an explicit numeric accountId target and sends Basecamp's mandatory identifying User-Agent. Read caching is disabled. Only the installed Todo Source list/read operations are unmarked and unheld; every other read is marked sensitive-read and requires approval unless session-granted. Unsafe 64-bit JSON identifiers are preserved as exact decimal strings, and int64 request identifiers are accepted as strings and serialized without numeric rounding. Every mutation is grant-off and approval-gated.

API capability pack for bounded Beehiiv Data API v2 calls against https://api.beehiiv.com/v2 only. Reads publications, posts, aggregate post stats, email blasts, post templates, subscriptions, custom fields, automations, automation journeys, segments, referral milestones, tiers, and webhook metadata for daily newsletter operations. Approval-gates one-subscriber create/update, subscriber tag add, custom-field create/update, and adding one existing or new subscriber to an automation journey. Enroll a Beehiiv API-key or OAuth bearer connection named beehiiv; no credential is embedded in the manifest. The pack intentionally excludes post create/update/delete/send/test, bulk subscription imports or status sweeps, subscription delete, subscriber JWT login tokens, tier mutation, webhook mutation/test, segment create/delete/recalculate, newsletter-list beta APIs, privacy/data-deletion flows, and arbitrary API passthrough.

API capability pack for bounded BigCommerce Store Management API operations. The default egress base is https://api.bigcommerce.com/stores/example; enroll a bigcommerce API connection with base_url set to the actual store root, for example https://api.bigcommerce.com/stores/{store_hash}, and header auth injecting X-Auth-Token. Reads store metadata, catalog summary, products, variants, categories, brands, orders, order statuses, order line items, shipments, coupons, messages, customers, channels, and price lists. Bundles a scheduled store operations digest, an AI-assisted order/customer brief, and approval-gated product listing and order status workflows. Writes are approval-gated and limited to one product listing update, one variant price/inventory update, or one order status update at a time. The pack intentionally excludes destructive deletes, batch endpoints, refunds, payment capture, order creation, shipment mutation, tax/shipping/payment settings, webhooks, scripts, checkout/cart mutation, customer password or stored-payment operations, arbitrary API passthrough, and credential-bearing fields in operation arguments.

V3 JavaScript/TypeScript web-code quality capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local biome CLI ingredient exposes bounded project operations for readiness and formatter/linter/import-sorting diagnostics. Quality checks run from an explicit project directory cwd supplied at execution time, accept one trusted file or directory target, return JSON diagnostics, avoid caller-supplied Biome flags, avoid shell wrappers, and never write files. Fixed-function and reproducible: CI check mode only, JSON reporter, colors disabled, diagnostics capped, no write/fix/unsafe mode, no init/migrate/upgrade/search/LSP/daemon command, no stdin, no caller-supplied config path, no reporter file, no staged/changed/VCS selector, no watch mode, no environment override, no arbitrary command execution, and no network egress. Requires biome on PATH. Local and no-egress.

API capability pack for bounded Bitbucket Cloud REST API 2.0 operations against https://api.bitbucket.org/2.0 only. Reads current user, workspaces, repositories, commits, pull requests, pull request comments, pull request commit statuses, issues, and pipelines, and supports approval-gated pull request comments and issue creation. Bundles a scheduled repository triage digest, an AI-assisted pull request review brief, an approval-gated issue intake workflow, and an approval-gated pull request comment workflow. Enroll a Bitbucket OAuth or API-token connection named bitbucket with the narrowest scopes needed for the installed operations. The pack intentionally excludes repository create/update/delete, branch restrictions, default reviewer mutation, pull request merge/decline/approve/request-changes, comment edit/delete/resolve, issue update/delete, pipeline runs/stops/configuration, variables, runners, SSH keys, downloads, webhooks, admin APIs, and arbitrary API passthrough.

Workflow pack for Recued-created Bitbucket pull request comments. It composes the Bitbucket capability pack with a closure ledger: add one owner-approved top-level comment to an existing Bitbucket pull request, persist only the connection/workspace/repository/pull-request/comment linkage in data.shared, and let a scheduled watcher re-read that exact pull request until Bitbucket reports it merged, declined, or superseded. This pack does not replace Bitbucket pull request comments, native notifications, review approvals, merge or decline controls, branch policies, pipelines, webhooks, or general code review reporting; it adds Recued-visible closure state for pull request comments Recued created.

V3 Python Black format-check capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local black CLI ingredient exposes bounded project operations for readiness and format-check diagnostics. Format checks inspect one trusted Python file or directory from one explicit project directory cwd and return Black text/diff diagnostics via the python.black_format_check catalog operation. Fixed-function and non-writing: check mode, diff output, no color, no cache reads or writes, no stdin, code string, line-range selector, target-version override, config path override, include/exclude override, worker override, preview/unstable style, required-version override, arbitrary flags, environment override, or shell wrapper. Would-reformat results are represented as successful text diagnostics; internal Black errors still fail. Requires black on PATH.