Marketplace

Run your day off the warehouse you already have — no CRM, no vendor account, no data leaving the machine. Ten recipes over your own mail and calendar: daily-morning-brief opens the day (today's events, who is waiting on you, your heaviest open loops) and end-of-day-shutdown-review closes it with a ranked top-3 for tomorrow; weekly-review-digest is the Friday retro over stalled projects and threads gone quiet. meeting-prep-brief fires before each event with attendees, prep notes and related threads; travel-day-prep-checklist checks a trip the day before. calendar-conflict-detector compares every pair of events exactly, and unanswered-inbound-radar decides who is waiting on you by comparing each thread's newest message against your last reply — both with no model call at all. commitment-deadline-radar rides the work-entity bus and notifies the moment a commitment turns due_soon or overdue. Everything reads; nothing sends. The two recipes that surface work — focus-block-proposer and post-meeting-follow-up-extractor — only PROPOSE: they render what they found and create nothing, because creating it is your call. The one model call in the pack (post-meeting follow-ups) sits behind deterministic gates and sees PII-aliased text. The five reactive recipes install disarmed — you arm them.

V3 deterministic structured-data path extraction pack. By-value connector composition (service_kind=cli, no separate ingredient): the local dasel CLI reads one trusted local structured-data path and extracts a selector as JSON via structured.extract_path. Dasel selectors are path-oriented and intentionally narrower than exposing an arbitrary jq program. This operation is path-based value output because the selected data is returned on stdout. Requires dasel on PATH (Debian/Ubuntu: apt install dasel). Local and no-egress.

The unauthenticated Datadog IP-range document served from the dedicated US1 ip-ranges host. Generated from Datadog's immutable hash-pinned official v1 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v1 monitors, metrics, dashboards, logs configuration, SLOs, events, hosts, notebooks, snapshots, tags, and usage reads. Generated from Datadog's immutable hash-pinned official v1 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v1 synthetics, organizations, users, key management, and AWS Logs, Azure, PagerDuty, Slack, and webhook integrations. Generated from Datadog's immutable hash-pinned official v1 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 application security, agentless scanning, CSM threats, and sensitive data scanning. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 action connections, action datastores, App Builder, feature flags, report schedules, and workflow automation. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 dashboard lists, downtimes, powerpacks, reference tables, scorecards, service definitions, software catalog, and widgets. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 AWS, Cloudflare, Confluent Cloud, Fastly, GCP, OCI, and Salesforce integrations. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 Google Chat, Microsoft Teams, Okta, Opsgenie, ServiceNow, Slack, Statuspage, and webhook integrations. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 event ingestion through the dedicated US1 event-management intake host. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 cloud cost management, billing-adjacent cost attribution, and usage metering. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 authentication mappings, identity providers, key management, roles, service accounts, teams, and users. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 authentication mappings, identity providers, key management, roles, service accounts, teams, and users. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 case management, incidents, on-call schedules and escalation policies, and status pages. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 JSON log ingestion through the dedicated US1 logs intake host. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog v2 APM, spans, metrics, monitors, containers, processes, events, error tracking, DORA metrics, and network monitoring. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

Datadog On-Call page creation and lifecycle actions through the globally routed navy US1 on-call host. Generated from Datadog's immutable hash-pinned official v2 OpenAPI schema. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, destructive operations are labeled explicitly, and unsafe JSON integers remain exact decimal strings. Provider pagination is walked only when its cursor can be replayed through the original admitted route without changing the documented request shape; nested JSON-body cursors remain explicit.

API capability pack for bounded Cal.com API v2 operations against https://api.cal.com only. Reads the enrolled profile, bookings, booking attendees and calendar links, event types, schedules, connected calendars, calendar events, conferencing apps, and available slots. Adds approval-gated booking lifecycle actions for daily scheduling work: create one booking, reschedule one booking, request attendee rescheduling, cancel one booking, and mark attendance absence. Enroll a Cal.com API key, managed-user access token, or OAuth access token connection as bearer auth; no credential is embedded in the manifest. The pack intentionally excludes confirm/decline/reassign endpoints, availability-bypass flags, calendar mutation endpoints, event-type/admin writes, Stripe endpoints, webhook mutations, and platform/OAuth-client header-auth endpoints.

API capability pack for bounded Calendly scheduling operations against https://api.calendly.com only. Lists the current user, organization memberships, groups, event types, available and busy times, availability schedules, scheduled events, and invitees; retrieves scheduling resources and invitee no-show records; and can approval-gate creating single-use scheduling links, booking an invitee through the Scheduling API, marking an invitee no-show, and canceling a scheduled event. Enroll a Calendly personal access token or OAuth access token connection as bearer auth; no credential is embedded in the manifest. Organization invitations/removals, webhook management, data-compliance deletion, event-type mutation, availability mutation, no-show deletion, and arbitrary API passthrough are intentionally not exposed.

API capability pack for bounded Canva Connect API operations against https://api.canva.com/rest. Enroll a Canva OAuth bearer connection named canva with least-privilege Connect API scopes for the installed operations. The pack reads user profile and capabilities, designs, design pages, export formats, export jobs, folders, folder items, assets, brand templates, brand template datasets, and comment threads/replies for creative operations, campaign review, and design handoff workflows. It bundles a scheduled design operations digest, an AI-assisted design brief, and approval-gated workflows for creating a simple design, starting an export job, replying to a comment thread, and updating asset metadata. Canva marks design pages and comments as preview APIs; the pack exposes them only as explicit read/reply workflows and calls that out in descriptions. The pack intentionally excludes deletes, asset binary uploads/downloads, print-partner APIs, design imports, autofill/merge/resize jobs, folder create/update/move, webhooks, analytics, OAuth token exchange/revoke/introspection, AI credit operations, arbitrary design editing, and arbitrary Canva API passthrough.

Workflow pack for Recued-sent Canva comment replies. It composes the Canva capability pack with a closure ledger: reply once to an existing Canva preview comment thread through the existing approval gate, persist only the connection/design/thread/reply linkage in data.shared, and let a scheduled watcher re-read that exact thread until Canva reports it resolved. This pack does not replace Canva comments, native notifications, comment resolution, design review dashboards, webhook administration, or general design status reporting; it adds Recued-visible closure state for comment replies Recued sent.

V3 Rust Cargo toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local cargo CLI ingredient exposes bounded project operations for readiness, compile checking, test execution, and Clippy diagnostics. Project operations run from an explicit project directory cwd supplied at execution time, use locked dependency resolution, avoid caller-supplied Cargo flags, avoid shell wrappers, and keep diagnostics visible as text or JSONL output. Compile, test, and lint operations are approval-gated because Cargo may compile project code, execute build scripts and proc macros, invoke toolchain helpers, run tests, and write target cache state. Requires cargo on PATH; Clippy operation also requires the clippy component.

API capability pack for bounded Chargebee API v2 Product Catalog 2.0 operations. Enroll a Chargebee HTTP Basic Auth API-key connection named chargebee with base_url set to the tenant API root, for example https://demo.chargebee.com/api/v2 or https://demo-test.chargebee.com/api/v2; the manifest default uses that documented example host but dispatch uses the enrolled connection's base_url. The pack reads customers, subscriptions, invoices, items, item prices, coupons, events, and hosted pages, and supports approval-gated creation of one customer, one item, one item price, or one hosted checkout page at a time using Chargebee's documented form-encoded request bodies. It bundles a scheduled revenue operations digest, customer revenue brief, catalog readiness brief, and guarded creation workflows. The pack intentionally excludes payment-source mutation, card/bank details, refunds, invoice collection/void/write-off, subscription update/cancel/pause/resume/delete, coupon mutation, event/webhook mutation, site/admin settings, exports, custom fields discovery, and arbitrary Chargebee API passthrough. No credential is embedded in the manifest.

Complete callable CircleCI API v2 suite pinned to the official OpenAPI document: all 111 method/path operations with no exclusions. The compatibility root keeps all 25 prior operation IDs and wire routes while four dependency packs carry 86 additional operations. Six compatibility routes retain their safe provider/organization/project wire expansion and prove it explicitly against CircleCI’s documented composite project-slug parameter. JSON int64 values remain exact. Reads are uncached and approval-free; mutations are grant-off and approval-gated, with destructive and administrative changes requiring approval every run. The CircleCI cloud base is the enrollment default; per-organization connections may target a compatible CircleCI Server API v2 base.

CircleCI contexts, context secrets and restrictions, OIDC claims, policy management, decisions, and OpenTelemetry exporters. Generated from the complete hash-pinned official CircleCI API v2 OpenAPI document. The CircleCI cloud base is the enrollment default; per-organization connections may target a compatible CircleCI Server API v2 base. Reads are uncached and approval-free. Mutations are grant-off and approval-gated; destructive and administrative changes require approval every run.

CircleCI insights, deployment environments and components, usage exports, and rollback operations. Generated from the complete hash-pinned official CircleCI API v2 OpenAPI document. The CircleCI cloud base is the enrollment default; per-organization connections may target a compatible CircleCI Server API v2 base. Reads are uncached and approval-free. Mutations are grant-off and approval-gated; destructive and administrative changes require approval every run.

CircleCI pipeline continuation, pipeline-definition mutation, triggers, schedules, user lookup, and job cancellation by project-local number. Generated from the complete hash-pinned official CircleCI API v2 OpenAPI document. The CircleCI cloud base is the enrollment default; per-organization connections may target a compatible CircleCI Server API v2 base. Reads are uncached and approval-free. Mutations are grant-off and approval-gated; destructive and administrative changes require approval every run.

CircleCI projects, project environment variables and checkout keys, organizations, groups, webhooks, settings, and URL orb allow-lists. Generated from the complete hash-pinned official CircleCI API v2 OpenAPI document. The CircleCI cloud base is the enrollment default; per-organization connections may target a compatible CircleCI Server API v2 base. Reads are uncached and approval-free. Mutations are grant-off and approval-gated; destructive and administrative changes require approval every run.

API capability pack for bounded Clerk Backend API operations against https://api.clerk.com/v1 only. Enroll a Clerk secret-key bearer connection named clerk with the narrowest user, session, organization, invitation, role, permission, and domain scopes needed for the installed workflows; no credential is embedded in this manifest. The pack reads users, user counts, sessions, organizations, organization memberships, organization invitations, organization domains, organization roles, organization permissions, instance invitations, and instance domains for SaaS access governance, customer onboarding, B2B organization operations, and support review. It bundles scheduled access hygiene, AI-assisted user access review, approval-gated organization invitation, and approval-gated user ban/unban workflows. Writes are limited to one organization, one organization invitation, one organization membership role change, or one user ban/unban at a time. The pack intentionally excludes user create/update/password/MFA mutation, token creation, OAuth access token fetches, testing tokens, session creation/revocation/refresh, invitation revoke, deletes, bulk endpoints, domain mutation, role/permission administration writes, webhook administration, billing credit adjustments, OAuth token exchange, and arbitrary Clerk API passthrough.

One-install ClickHouse Cloud front door over 6 bounded capability packs and 34 non-chat, uncached, read-only workflows. It admits all 108 nondeprecated operations across 64 official paths and excludes exactly 2 provider-deprecated operations. Organizations, access, API keys, services, settings, networking, backups, metrics, ClickPipes, managed Postgres, and ClickStack are covered. Forty-three admitted operations are provider-marked beta, and each retains that warning in its capability description. The mutable official OpenAPI URL must retain 910,739 bytes and SHA-256 68f34fa22f5994b1332f0f536cc43adec7a8099f3be6cf6e722e3ec8f6fc6893 before regeneration. Calls stay on api.clickhouse.cloud and use organization API key ID/secret Basic authentication supplied only by the selected connection. Both tag-filter arrays preserve their official multi-value repeated-query serialization. The single documented offset collection is automatic. One PEM download becomes a private file_ref. Source schema discovery is the only POST-shaped read. Organization network/diagnostic policy changes, ClickPipe creation, full dashboard replacement, restores, credential/access changes, scaling, state, backup, ingestion, and configuration updates are destructive. All 43 documented JSON bodies are required and sent verbatim because the authority omits requestBody.required. Reads are uncached; every mutation requires approval; unsafe response integers remain exact strings. No task, note, or user-work project Source is claimed for infrastructure tenancy or runtime resources.

ClickHouse Cloud backups, backup buckets and configuration, plus organization, service, and Postgres Prometheus exports. Generated from ClickHouse's hash-locked official ClickHouse Cloud OpenAPI 3.1.2 snapshot (68f34fa22f59…) and carries 12 of the suite's 108 nondeprecated operations. Calls are fixed to api.clickhouse.cloud and use Basic authentication with the organization API key ID and secret supplied only by the selected connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Unsafe response integers remain exact strings, the Postgres CA certificate becomes a private file_ref, reads are uncached, and every mutation requires approval. No infrastructure tenancy or runtime resource is misrepresented as a task, note, or user-work project Source.

ClickHouse Cloud ClickPipes, source schema discovery, scaling, state, settings, CDC capacity, and reverse private endpoints. Generated from ClickHouse's hash-locked official ClickHouse Cloud OpenAPI 3.1.2 snapshot (68f34fa22f59…) and carries 17 of the suite's 108 nondeprecated operations. Calls are fixed to api.clickhouse.cloud and use Basic authentication with the organization API key ID and secret supplied only by the selected connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Unsafe response integers remain exact strings, the Postgres CA certificate becomes a private file_ref, reads are uncached, and every mutation requires approval. No infrastructure tenancy or runtime resource is misrepresented as a task, note, or user-work project Source.

ClickHouse Cloud ClickStack dashboards, alerts, sources, and webhook destinations for observability configuration as code. Generated from ClickHouse's hash-locked official ClickHouse Cloud OpenAPI 3.1.2 snapshot (68f34fa22f59…) and carries 12 of the suite's 108 nondeprecated operations. Calls are fixed to api.clickhouse.cloud and use Basic authentication with the organization API key ID and secret supplied only by the selected connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Unsafe response integers remain exact strings, the Postgres CA certificate becomes a private file_ref, reads are uncached, and every mutation requires approval. No infrastructure tenancy or runtime resource is misrepresented as a task, note, or user-work project Source.

ClickHouse Cloud organizations, BYOC infrastructure, usage costs, roles, members, invitations, activities, and organization API keys. Generated from ClickHouse's hash-locked official ClickHouse Cloud OpenAPI 3.1.2 snapshot (68f34fa22f59…) and carries 27 of the suite's 108 nondeprecated operations. Calls are fixed to api.clickhouse.cloud and use Basic authentication with the organization API key ID and secret supplied only by the selected connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Unsafe response integers remain exact strings, the Postgres CA certificate becomes a private file_ref, reads are uncached, and every mutation requires approval. No infrastructure tenancy or runtime resource is misrepresented as a task, note, or user-work project Source.

ClickHouse Cloud managed Postgres services, replicas, restore, configuration, credentials, certificates, metrics, and slow-query analysis. Generated from ClickHouse's hash-locked official ClickHouse Cloud OpenAPI 3.1.2 snapshot (68f34fa22f59…) and carries 16 of the suite's 108 nondeprecated operations. Calls are fixed to api.clickhouse.cloud and use Basic authentication with the organization API key ID and secret supplied only by the selected connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Unsafe response integers remain exact strings, the Postgres CA certificate becomes a private file_ref, reads are uncached, and every mutation requires approval. No infrastructure tenancy or runtime resource is misrepresented as a task, note, or user-work project Source.

ClickHouse Cloud services, scaling, state, credentials, private endpoints, query endpoints, upgrade windows, schedules, and ClickHouse settings. Generated from ClickHouse's hash-locked official ClickHouse Cloud OpenAPI 3.1.2 snapshot (68f34fa22f59…) and carries 24 of the suite's 108 nondeprecated operations. Calls are fixed to api.clickhouse.cloud and use Basic authentication with the organization API key ID and secret supplied only by the selected connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Unsafe response integers remain exact strings, the Postgres CA certificate becomes a private file_ref, reads are uncached, and every mutation requires approval. No infrastructure tenancy or runtime resource is misrepresented as a task, note, or user-work project Source.

Contract-pinned capability pack for bounded ClickUp Public API operations against https://api.clickup.com only. The primary composition proves v2 work-management calls against ClickUp's official v2 OpenAPI document; the required clickup-v3 companion proves Docs, pages, attachment metadata, and task home-List moves independently against the official v3 document. Reads cover the current user, workspaces, spaces, folders, lists, members, tasks, comments, checklists, tags, custom fields, time entries, goals, Docs, pages, attachments, groups, and webhooks. A read-only, paginated task Source includes visible closed tasks and subtasks so completion fields remain live. Bundled workflows provide a scheduled workspace digest, a read-only task review brief, and an approval-gated task intake. Approval-gated mutations are limited to creating or updating one space, folder, list, task, comment, checklist item, tag, time entry, goal, key result, Doc page, or webhook at a time; retries are explicitly classified, and DELETE operations are destructive/always-confirm. Enroll one ClickUp connection that injects the documented Authorization header using a personal token or OAuth access token; no credential is embedded. The pack excludes OAuth exchange, user and guest invites/removals, ACL/privacy controls, audit logs, arbitrary passthrough, admin/feature configuration, multipart upload bodies, legacy time-tracking endpoints, chat/channel management, bulk imports, and destructive bulk actions.

Workflow pack for Recued-created ClickUp tasks. It composes the ClickUp capability pack with a closure ledger: create one owner-approved task in one live ClickUp List, persist only the connection/list/task linkage in data.shared, and let a scheduled watcher re-read that exact task until ClickUp reports a configured terminal status such as complete, completed, closed, or done. This pack does not replace ClickUp statuses, status workflows, task close controls, dashboards, reminders, automations, webhooks, custom fields, assignments, tags, dependencies, checklists, time tracking, or general project reporting; it adds Recued-visible closure state for ClickUp tasks Recued created.

Workflow pack for Recued-created ClickUp task comments. It composes the ClickUp capability pack with a closure ledger: add one owner-approved comment to an existing ClickUp task, persist only the connection/task/comment linkage in data.shared, and let a scheduled watcher re-read that exact task until ClickUp reports a configured terminal status such as complete, completed, closed, or done. This pack does not replace ClickUp task comments, native notifications, status workflows, task close controls, dashboards, reminders, automations, webhooks, or general project reporting; it adds Recued-visible closure state for task comments Recued created.

Contract-isolated companion capability for the ClickUp pack. It proves the bounded Public API v3 operations used for task home-List moves, Docs, pages, and attachment metadata against ClickUp's separate official v3 OpenAPI document. The companion shares the parent pack's ClickUp Authorization-header connection. Reads never download attachment bytes; writes are approval-gated and explicitly classified for retries. It excludes chat and channel management, ACL/privacy operations, audit logs, attachment uploads, time-estimate administration, arbitrary passthrough, bulk actions, and deletes.

Complete callable Close REST API suite: all 297 method/path operations in the current official OpenAPI plus the official Advanced Filtering search documented outside that explicitly experimental specification. The compatibility root keeps all 26 prior operation IDs, wire routes, and shipped workflows while five dependency packs carry 272 additional operations. The OpenAPI and three pagination/advanced-filter authorities are hash-anchored; generation fails closed on drift. JSON responses preserve unsafe integers as exact decimal strings. Reads are approval-free; mutations are grant-off and approval-gated, with destructive, administrative, communication, automation, enrichment, and bulk changes requiring approval every run.

Close groups, roles, memberships, webhooks, users, and organization administration. Generated from the hash-anchored complete Close OpenAPI document, which Close labels experimental and not guaranteed to cover every request or response schema. JSON responses preserve unsafe integers as decimal strings. Reads are approval-free; mutations are grant-off and approval-gated, with destructive, administrative, and high-impact changes requiring approval every run.

Close Advanced Filtering API search, documented by Close outside its explicitly experimental OpenAPI document. The generator fails closed on the official Markdown document hash because this route is absent from Close's experimental OpenAPI. Reads are approval-free, cursors are kept in the JSON request body, and JSON unsafe integers remain exact decimal strings.

Close scheduling, sequences, templates, bulk actions, playbooks, phone, send-as, connected-account, and enrichment operations. Generated from the hash-anchored complete Close OpenAPI document, which Close labels experimental and not guaranteed to cover every request or response schema. JSON responses preserve unsafe integers as decimal strings. Reads are approval-free; mutations are grant-off and approval-gated, with destructive, administrative, and high-impact changes requiring approval every run.

Close leads, contacts, opportunities, tasks, pipelines, statuses, outcomes, comments, and activity operations not retained in the compatibility root. Generated from the hash-anchored complete Close OpenAPI document, which Close labels experimental and not guaranteed to cover every request or response schema. JSON responses preserve unsafe integers as decimal strings. Reads are approval-free; mutations are grant-off and approval-gated, with destructive, administrative, and high-impact changes requiring approval every run.

Close custom fields, custom objects, exports, reports, smart views, forms, events, files, and integration-link operations. Generated from the hash-anchored complete Close OpenAPI document, which Close labels experimental and not guaranteed to cover every request or response schema. JSON responses preserve unsafe integers as decimal strings. Reads are approval-free; mutations are grant-off and approval-gated, with destructive, administrative, and high-impact changes requiring approval every run.

API capability pack for bounded Cloudflare REST operations against https://api.cloudflare.com/client/v4. Enroll a cloudflare API connection as a bearer-token connection backed by a scoped Cloudflare API token; no credential is embedded in the manifest. The pack verifies the token; reads accounts, zones, DNS records, Pages projects/deployments/domains, Worker script/deployment/route metadata, R2 buckets/object metadata, KV namespaces/key names, D1 database metadata, Queue inventory/metrics, and account audit logs; and supports approval-gated daily operations for creating/updating simple DNS records and purging specific cached URLs. It intentionally does not expose DNS record deletion, purge-everything, purge by tag/host/prefix, zone/account edits, Worker uploads or script content download, Pages deploy/retry/rollback actions, R2 object download/delete/upload, KV value reads/writes, D1 query/export/import, Queue message pull/send/purge, ruleset writes, token management, or arbitrary API passthrough.