Recued Core

V3 deterministic XML validation and formatting capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local xmllint CLI ingredient exposes readiness, well-formedness validation, captured XML formatting, and ordered two-file XSD/RelaxNG validation operations. Fixed-function and reproducible: file inputs are materialized by the executor, formatted output is written only to an engine-managed output directory, schema validation returns only exit status, and recipes cannot pass arbitrary parser flags, DTD URLs, network fetches, shell wrappers, or caller-controlled output paths. Requires xmllint on PATH (Debian/Ubuntu: apt install libxml2-utils; macOS: xmllint ships with libxml2/system tools). Local and no-egress.

V3 deterministic YAML lint capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local yamllint CLI checks one trusted local YAML file or directory and returns parsable text diagnostics via the yaml.lint catalog operation. Fixed-function and reproducible: no arbitrary yamllint flags, no caller-supplied config path, no stdin stream, no strict-mode toggle, no shell wrapper, and no network egress. The built-in relaxed profile is pinned through argv so ambient .yamllint files, user config files, and YAMLLINT_CONFIG_FILE do not change pack behavior. Lint findings are represented as text output instead of failing the op; real invocation errors still fail. Requires yamllint on PATH. Local and no-egress.

V3 Yarn toolchain capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local yarn CLI ingredient exposes bounded project operations for readiness and package test execution. Project operations run from an explicit project directory cwd supplied at execution time, avoid caller-supplied Yarn flags, avoid shell wrappers, and keep diagnostics visible as text output. Test execution is approval-gated because package scripts execute project-defined code and Yarn lifecycle behavior. The pack exposes no caller-supplied script name, package-manager flags, workspace selectors, install/update/audit command, registry, env override, stdin, or arbitrary command execution. Requires yarn on PATH.

API capability pack for bounded YouTube Data API v3 calls against https://youtube.googleapis.com only. Reads channel, video, search, playlist, playlist-item, comment, caption, subscription, category, region, and language metadata for daily creator and small-business content workflows. Approval-gates playlist creation/update/deletion, adding/reordering/removing one playlist item, posting one top-level comment or reply, moderating one comment, and deleting one comment. It also bundles a scheduled channel content digest, an AI-assisted video and comment review brief, and approval-gated playlist creation workflow. The bundled recipes only use playlist.create and playlist_item.add as writes. Enroll a Google OAuth bearer connection named google with the narrowest YouTube Data API scopes required for the installed operations; no credential is embedded in the manifest. The pack intentionally excludes video upload/update/delete/rating/reporting, thumbnail and caption media upload/download, live broadcast/live chat controls, channel branding/sections/watermarks, subscription writes, partner/content-owner administration, arbitrary part passthrough for audit details, arbitrary Google APIs, and arbitrary YouTube API passthrough.

V3 deterministic media-download capability pack. By-value cli composition (service_kind=cli, no separate service ingredient): one local yt-dlp CLI ingredient exposes readiness, URL metadata JSON, available format listing, and detached media download. Metadata and format inspection are read-tier but approval=ask because yt-dlp contacts the remote URL; they do not download media or write output files. The media.download operation is launched as a Recued-managed DETACHED one-shot job (NOT a supervised daemon): a download realistically runs for many minutes past the foreground execution cap, so the launcher detaches the child, redirects output to {result_dir}/{key}.log, and writes {result_dir}/{key}.pid + the {result_dir}/{key}.exit.<code> completion marker. The downloaded media lands at {result_dir}/{key}.<ext> and a downstream D-179 sweeper recipe reconciles marker/log evidence; the log carries the exact `[download] Destination:` path. All URL operations ignore user config files, browser cookies, cookie files, and persistent cache by default so pack behavior is bounded and does not silently inherit local account state. Requires the yt-dlp binary on PATH (pip install --user yt-dlp). Replaces the retired yt-dlp-{linux,macos,win} service templates.

API capability pack for the bounded Zapier Workflow API at https://api.zapier.com. Enroll a zapier API connection as an OAuth bearer token for user-scoped operations, or pass query.client_id for client-id endpoints where Zapier allows it. The pack reads profile, apps, categories, templates, Zaps, Zap runs, actions, dynamic fields, choices, output fields, authentications, action-run results, and Zap guesses; it creates Zaps, app authentications, action runs, and action tests with approval. It intentionally excludes the browser OAuth authorize redirect, White Label external JWT flows, hosted Zapier MCP server control, Zapier Tables/Interfaces private product APIs, arbitrary API-by-Zapier passthrough, and unbounded webhooks.

V3 deterministic barcode/QR image scan capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local zbarimg CLI reads one trusted local image path and returns decoded barcode payload text via the image.scan_barcode catalog operation. This is the read-side complement to the existing qrencode pack. The operation is path-based because decoded payloads are stdout value output; it does not combine file_ref materialization with value capture. Requires zbarimg on PATH (Debian/Ubuntu: apt install zbar-tools). Local and no-egress.

One-install Zendesk suite with 772 operations: 597 of 622 official Support routes plus 175 of 178 official Help Center routes. The 41-operation compatibility root preserves every prior operation ID and all three existing Zendesk workflows, while ten bounded dependency packs expose the remaining Support and Help Center surfaces. Twenty-eight routes fail closed because they require unsupported multipart, binary, or DELETE-body transport, omit a credential request shape, or expose OAuth or session credentials. Official JSON-body schema gaps use operation-scoped raw bodies instead of dispatching empty writes, while documented bodyless and optional-body actions remain callable without invented payloads. Reads are uncached, newly added sensitive reads are marked sensitive-read, every mutation is grant-off and approval-gated, documented pagination is bounded, binary downloads are isolated as file_ref values, and JSON integers are parsed losslessly.

Zendesk Support views, macros, automations, triggers, SLA policies, and deletion schedules. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Support custom objects, records, fields, permissions, attachments, object triggers, lookup relationships, queues, and skill-based routing. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Support incremental exports, search, tags, dynamic content, bookmarks, IT asset management, job statuses, and target failures. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Support account configuration, roles, fields, forms, statuses, saved searches, support addresses, task lists, resource collections, and workspaces. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Help Center article comments, posts, post comments, topics, votes, subscriptions, sessions, and user-image coordination. Generated from the current hash-pinned official Zendesk Help Center OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Help Center articles, categories, sections, translations, labels, attachments, search, user segments, and service-catalog content. Generated from the current hash-pinned official Zendesk Help Center OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Support organizations, memberships, subscriptions, brands, brand agents, locales, countries, and sharing agreements. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Support audit, channel, security, session, target, reseller, remote-authentication, and platform administration surfaces. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Workflow pack for Recued-sent Zendesk public replies. It composes the Zendesk capability pack with a closure ledger: send one public ticket reply through the existing Zendesk approval gate, persist only the connection/ticket reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact ticket until Zendesk reports solved/closed or an owner-actionable status such as new/open. This pack does not replace Zendesk triggers, automations, views, macros, SLA policy, or helpdesk queue rules; it adds Recued-visible closure state for tickets Recued replied to.

Zendesk Support tickets, requests, comments, audits, metrics, imports, skips, suspended tickets, satisfaction, attachments, activity, and conversation surfaces. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

Zendesk Support users, identities, groups, memberships, and password-requirement reads. Generated from the current hash-pinned official Zendesk Support OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and requires approval every run. Documented continuations are bounded by 25 pages and 1,000 records, and int64 values are handled losslessly.

V3 deterministic ZIP archive capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local zip CLI ingredient exposes readiness, compressed single-file archive creation, store-only single-file archive creation, and ZIP integrity testing. Fixed-function and reproducible: the executor materializes source files and owns the throwaway output directory, while zip writes fixed archive results captured as result.file_ref. Write-tier operations write only to an engine-managed output dir, read-tier testing returns only exit status, and recipes cannot pass arbitrary flags, recurse into directories, encrypt archives, read file lists from stdin, move/delete source files, add comments, or choose output paths. Requires the zip binary on PATH (Debian/Ubuntu: apt install zip; macOS: zip is commonly installed with the system tools). Local and no-egress.

API capability pack for bounded Zoho CRM back-office operations. Uses the shared Zoho CRM OAuth connection and fixed Zoho CRM API V8 endpoints. Covers organization/user/module/field lookup, contact/account lookup, products, price books, quotes, sales orders, invoices, purchase orders, vendors, and notes. Writes are approval-gated and limited to one product, price book, quote, sales order, invoice, purchase order, vendor, or note operation at a time. Excludes lead/deal pipeline mutation, service appointment booking, quote/order/invoice/purchase-order line-item recipes, payment/refund/receiving/bill recording, deletes, bulk APIs, COQL/query APIs, admin mutation, arbitrary module passthrough, attachments, files, functions, webhooks, and credential-bearing operation arguments.

API capability pack for bounded Zoho CRM sales operations. Uses the shared Zoho CRM OAuth connection and fixed Zoho CRM API V8 endpoints. Covers organization/user lookup, leads, contacts, accounts, deals, campaigns, sales notes, and read-only activity slices needed for sales briefings; standalone note listing requires a Zoho admin profile. Writes are approval-gated and limited to one lead, contact, account, deal, campaign, or note operation at a time. Excludes back-office inventory documents, service appointment booking, deletes, bulk APIs, COQL/query APIs, blueprints, admin mutation, arbitrary module passthrough, attachments, files, functions, webhooks, and credential-bearing operation arguments.

API capability pack for bounded Zoho CRM work and service operations. Uses the shared Zoho CRM OAuth connection and fixed Zoho CRM API V8 endpoints. Covers organization/user lookup, cases, solutions, tasks, calls, events/meetings, services, appointments, and customer lookup. Writes are approval-gated and limited to one case, solution, task, call, event, service, appointment, or note operation at a time. Excludes sales pipeline mutation, back-office inventory documents, service creation, service member/pricing/tax recipes, appointment deletes, appointment preference mutation, appointment rescheduled-history direct writes, bulk APIs, COQL/query APIs, admin mutation, arbitrary module passthrough, attachments, files, functions, webhooks, and credential-bearing operation arguments.

API capability pack for bounded Zoom Meetings operations against https://api.zoom.us/v2 only. Reads users, user settings, scheduled meetings, invitations, registrants, polls, past-meeting participants, Q&A, poll results, recordings, recording files, recording analytics, and recording registrants for daily meeting operations that go beyond the generic calendar surface. Approval-gates creating/updating/canceling meetings and adding or approving/denying registrants. It also bundles a scheduled upcoming-meetings digest, an AI-assisted meeting and recording review brief, and approval-gated meeting creation workflow. The bundled recipes only use meeting.create as a write. Enroll a Zoom OAuth or server-to-server OAuth bearer connection named zoom; no credential is embedded in the manifest. Zoom Calendar, Chat, Phone, Rooms, webhooks, user administration, settings mutation, poll mutation, recording deletion, recording download passthrough, livestream controls, in-meeting controls, and arbitrary API passthrough are intentionally not exposed.

V3 deterministic Zstandard compression capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local zstd CLI ingredient exposes readiness, default compression, fast compression, decompression, and compressed-stream integrity testing. Fixed-function and reproducible: the executor materializes source files and owns the throwaway output directory, while zstd writes fixed output files that are captured as result.file_ref. Write-tier operations write only to an engine-managed output dir, read-tier testing returns only exit status, and recipes cannot pass arbitrary flags, dictionaries, recursive inputs, file lists, source-removal flags, shell wrappers, or caller-controlled output paths. Requires the zstd binary on PATH (Debian/Ubuntu: apt install zstd; macOS: brew install zstd). Local and no-egress.

API capability pack for bounded Zuora Billing v1 revenue operations. Enroll a Zuora OAuth2 bearer connection named zuora with base_url set to the tenant REST endpoint, for example https://rest.zuora.com, https://rest.na.zuora.com, or a documented sandbox endpoint. The pack reads accounts, account summaries, account subscriptions, subscriptions, invoices, product catalog, orders, product charge definitions, and bill runs through documented Zuora REST endpoints. Bundled recipes provide a scheduled revenue operations digest, an account revenue brief, a catalog readiness brief, and guarded account intake. Writes are approval-gated and limited to creating one account without payment methods or subscriptions. Subscription/order/invoice mutation, payment-method creation or authorization, bill-run creation/post/cancel/delete, invoice post/reverse/write-off/collection/delete, order activation/cancel/delete, OAuth token exchange, object CRUD, exports, files, webhooks, custom object mutation, and arbitrary Zuora API passthrough are intentionally not exposed. No credential is embedded in the manifest.

One-install Vercel front door over five bounded domain packs and six release workflows. It admits 336 of 357 current official method/path operations. Twenty-one fail-closed exclusions are two HEAD probes, three binary uploads, one POST binary file read, two JSONL billing responses the adapter would misparse, two real-time log streams the adapter cannot buffer safely, and eleven routes added upstream in July 2026 whose admission is deferred pending policy curation. The compatibility root keeps all 25 prior operation IDs and routes while dependencies add 311 operations. Project environment metadata reads pin decrypt=false; an explicitly selected decrypted variable read remains separately marked sensitive-read. Reads are uncached, sensitive reads are marked sensitive-read, and every mutation is grant-off and approval-gated. Binary artifact downloads become isolated file_ref values. Enroll a Vercel bearer-token connection at https://api.vercel.com.

Vercel marketplace, integrations, webhooks, drains, logs, Web Analytics, microfrontends, storage, and Insights controls. Generated from the current hash-pinned official Vercel OpenAPI document. Reads are uncached; sensitive reads are marked sensitive-read. Every mutation is grant-off and approval-gated, and administrative or destructive changes require approval every run.

Workflow pack that closes the loop between Vercel production deployment failures and owner-reviewed Statuspage incident communication. It depends on the Vercel and Statuspage capability packs, detects one unhandled failed production deployment at a time, writes a data.shared proposal, notifies the owner, and provides a manual action recipe that either creates the Statuspage incident and links it back to the Vercel deployment or dismisses the proposal when no customer-facing incident is needed. It does not duplicate Vercel's native deployment notifications, rollback controls, or webhooks; those stay in Vercel. It also does not auto-publish customer-facing Statuspage updates from unattended automation.

V3 deterministic image-transform capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local libvips CLI ingredient exposes readiness, thumbnails, resize, PNG conversion, metadata-stripped optimized JPEG export, and WebP export via fixed catalog operations. Write-tier but approval=never: vips writes only to an engine-managed throwaway output dir and each result is captured as result.file_ref; image bytes never flow through stdout values. The output format is selected from fixed file suffixes and bounded save options, never from caller-supplied filenames or arbitrary vips flags. Requires vips on PATH (Debian/Ubuntu: apt install libvips-tools; macOS: brew install vips). Local and no-egress. Use this pack for fast local image normalization and web-ready derivatives; use specialized optimizers such as jpegoptim/oxipng when the workflow must preserve the source format exactly.

V3 JavaScript/TypeScript test-run capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local vitest CLI runs one trusted test file, directory filter, or filename:line filter from an explicit project directory cwd and returns plain test output via the javascript.test_run catalog operation. Fixed invocation, but approval-gated: Vitest loads project Vite/Vitest config and executes test, setup, transform, and dependency code, so the run may write caches or project state depending on the project. The pack uses single-run mode, the built-in default reporter, colors disabled, coverage/browser/UI/snapshot-update surfaces disabled, no custom config/root/project/reporter/output-file/watch/debug/list/cache-clear/MCP-like server/browser/shard/changed/typecheck/filter-expression/stdin/shell surface, and a target validation pattern that rejects leading-dash values so the editable target cannot become a Vitest flag. Test failures and no-tests-found outcomes are represented as successful text output; the runner output remains authoritative for distinguishing assertion failures from configuration/runtime errors. Requires vitest on PATH.

API capability pack for bounded Wave Accounting GraphQL operations against https://gql.waveapps.com only. Reads the authenticated user, setup constants, businesses, customers, products/services, invoices, invoice payments, chart-of-account payment accounts, sales taxes, vendors, and estimates. Bundles daily bookkeeping, collections, customer/product intake, invoice and estimate draft/send, estimate-to-invoice conversion, manual payment workflows, and a closed-loop invoice reminder-exception pair that sends an owner-approved Wave invoice email only when native reminders are insufficient, then watches Wave until the invoice is paid or resolved. Enroll a Wave OAuth access token or personal full-access token connection as bearer auth; no credential is embedded in the manifest. Writes are approval-gated and limited to customer create/update, product create/update, invoice create/update/clone/approve/mark-sent/send, invoice payment record/update/receipt-send, estimate create/update/clone/approve/mark-sent/mark-accepted/send/PDF/convert, and estimate deposit payment record/update/receipt-send. The pack intentionally excludes customer/product/invoice/estimate delete or archive, account/tax mutation, money transaction creation, estimate acceptance reset, webhooks, arbitrary GraphQL passthrough, OAuth app administration, and cross-host egress.

Workflow pack for Wave invoice-reminder exceptions. It adds a collections brief, an owner-approved Wave invoice email for cases native reminders cannot cover, and a scheduled watcher that closes the shared lifecycle when Wave reports the invoice paid or resolved. It depends on the Wave capability pack and does not create or edit invoices, record payments, change customers, or replace Wave native reminders.

V3 deterministic text/file-count capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local wc CLI ingredient exposes bounded read-only count metadata for one trusted local path: byte count, line count, word count, character count, longest line, and combined line/word/byte counts. The operations return wc's count output only; they do not return file content, read stdin, accept file lists, recurse directories, follow shell globs, expose arbitrary wc flags, write outputs, use environment overrides, or use a shell wrapper. Editable paths reject flag-like values, URL-like references, and scp-style remotes. Requires a POSIX-compatible wc on PATH. Local and no-egress.

V3 deterministic HTML-to-PDF capability pack. By-value connector composition (service_kind=cli, no separate ingredient): the local WeasyPrint CLI renders one source HTML document to a PDF via the html.to_pdf catalog operation. Fixed-function and reproducible: the executor materializes the source HTML and owns the throwaway output directory, while WeasyPrint writes a fixed document.pdf result captured as result.file_ref. Write-tier but approval=never: WeasyPrint writes only to an engine-managed output dir and exposes no arbitrary flags. Use self-contained/local HTML inputs; the pack does not expose URL input or asset-fetch controls. Requires weasyprint on PATH (Debian/Ubuntu: apt install weasyprint).

One-install Weaviate front door over 6 bounded official domain packs and 6 non-chat, uncached, read-only workflows. It admits 108 of 114 operations from Weaviate 1.38.4's official Swagger document at commit 6af189f84eed9fcc9ea24614ed0b52bcd6d01abb. Only three redundant HEAD aliases and three protocol-owned MCP session/stream endpoints are excluded; every static JSON REST feature family remains covered. The surface spans objects, references, batches, GraphQL, tokenization, classifications, schemas, properties, indexes, shards, tenants, aliases, users, keys, RBAC, namespaces, backups, restore, export, replication, cluster statistics, nodes, tasks, health, metadata, and discovery. Enroll a secured deployment with the complete Authorization Bearer value. Raw JSON and decimal-string query selectors preserve exact request integers; unsafe response integers remain strings; reads are uncached; authenticated reads are marked sensitive-read and every mutation requires approval. No arbitrary vector-database object is misrepresented as a task, note, or project Source.

Weaviate database-user, API-key lifecycle, RBAC, group, and namespace operations. Generated from Weaviate's immutable commit-pinned official Swagger 2.0 schema. This leaf carries 31 of the suite's 108 admitted operations. Enroll a Weaviate Cloud or secured self-hosted deployment at its origin and store the complete Bearer credential in the Authorization header. JSON request documents are sent verbatim, query integers use exact decimal strings, unsafe response integers remain exact strings, reads are uncached, all authenticated reads are marked sensitive-read and every mutation requires approval, and no arbitrary vector-database object is represented as a task, note, or project Source.

Weaviate backup, restore, export, replica movement, sharding-state, and scale operations. Generated from Weaviate's immutable commit-pinned official Swagger 2.0 schema. This leaf carries 20 of the suite's 108 admitted operations. Enroll a Weaviate Cloud or secured self-hosted deployment at its origin and store the complete Bearer credential in the Authorization header. JSON request documents are sent verbatim, query integers use exact decimal strings, unsafe response integers remain exact strings, reads are uncached, all authenticated reads are marked sensitive-read and every mutation requires approval, and no arbitrary vector-database object is represented as a task, note, or project Source.

Weaviate root discovery, health, OIDC discovery, metadata, node, cluster, and distributed-task operations. Generated from Weaviate's immutable commit-pinned official Swagger 2.0 schema. This leaf carries 9 of the suite's 108 admitted operations. Enroll a Weaviate Cloud or secured self-hosted deployment at its origin and store the complete Bearer credential in the Authorization header. JSON request documents are sent verbatim, query integers use exact decimal strings, unsafe response integers remain exact strings, reads are uncached, all authenticated reads are marked sensitive-read and every mutation requires approval, and no arbitrary vector-database object is represented as a task, note, or project Source.

Weaviate object, reference, validation, and batch data operations. Generated from Weaviate's immutable commit-pinned official Swagger 2.0 schema. This leaf carries 20 of the suite's 108 admitted operations. Enroll a Weaviate Cloud or secured self-hosted deployment at its origin and store the complete Bearer credential in the Authorization header. JSON request documents are sent verbatim, query integers use exact decimal strings, unsafe response integers remain exact strings, reads are uncached, all authenticated reads are marked sensitive-read and every mutation requires approval, and no arbitrary vector-database object is represented as a task, note, or project Source.

Weaviate GraphQL query, tokenization, and classification operations. Generated from Weaviate's immutable commit-pinned official Swagger 2.0 schema. This leaf carries 5 of the suite's 108 admitted operations. Enroll a Weaviate Cloud or secured self-hosted deployment at its origin and store the complete Bearer credential in the Authorization header. JSON request documents are sent verbatim, query integers use exact decimal strings, unsafe response integers remain exact strings, reads are uncached, all authenticated reads are marked sensitive-read and every mutation requires approval, and no arbitrary vector-database object is represented as a task, note, or project Source.

Weaviate collection schema, property, index, shard, tenant, and alias operations. Generated from Weaviate's immutable commit-pinned official Swagger 2.0 schema. This leaf carries 23 of the suite's 108 admitted operations. Enroll a Weaviate Cloud or secured self-hosted deployment at its origin and store the complete Bearer credential in the Authorization header. JSON request documents are sent verbatim, query integers use exact decimal strings, unsafe response integers remain exact strings, reads are uncached, all authenticated reads are marked sensitive-read and every mutation requires approval, and no arbitrary vector-database object is represented as a task, note, or project Source.

Point Recued at the public web and let it tell you when something moved. Four recipes: watch-webpage-changes hashes one page every tick and only wakes you when the content actually changed, then says what changed; watch-competitor-pricing does the same for a pricing page but extracts the plans and prices first, so a new banner stays quiet and a price does not; brief-company-news searches news once per company on your list, drops the stories that repeat, and hands you one brief with the source table behind it; answer-with-sources answers a question from Brave's pre-extracted page content and shows the citations as data you can check. The two watchers are reactive and install DISARMED — set a URL, then arm them. Nothing here writes anywhere except its own cursor row, and the notifications go only to the channels you pick. The two search recipes need an enrolled Brave Search connection (Settings → Connections); the watchers need no connection at all — they fetch the URL you name and nothing else.

API capability pack for bounded Webex Messaging v1 operations against https://webexapis.com/v1 only. Reads the current person, people lookup, rooms, messages, and room memberships, and supports approval-gated posting of one room message or threaded reply. Bundles a scheduled room activity digest, an AI-assisted message brief, and an approval-gated room update workflow. Enroll a Webex OAuth bearer connection named webex with the narrowest Messaging scopes needed for the installed operations. The pack intentionally excludes room create/update/delete, membership mutation, message edit/delete, files and attachments, webhooks and events, meetings, calling, devices, admin/compliance organization access, and arbitrary API passthrough.

API capability pack for bounded Webflow Data API v2 operations against https://api.webflow.com/v2 only. Reads the authorized user, sites, domains, redirects, CMS collections and items, pages, assets, forms and submissions, comments, products, orders, and ecommerce settings for daily site and small-business operations. Approval-gates staged CMS item create/update and explicit 301 redirect create/update. Enroll a Webflow site token, workspace token, or OAuth bearer connection named webflow; no credential is embedded in the manifest. The pack intentionally excludes site publish, live CMS publish/unpublish, deletes, custom code mutation, page/component mutation, asset upload/delete, form submission mutation, order mutation, inventory mutation, webhooks, workspace administration, audit-log enterprise APIs, and arbitrary API passthrough.

No-auth API capability pack for bounded English Wikipedia lookups against https://en.wikipedia.org only. The pack exposes page search through MediaWiki Core REST and page summaries through the Wikimedia REST page-summary endpoint. No credential is embedded or required; the pack fixes the host, paths, search limit, and identifying API user agent.

One-install Wise Business front door over 7 separately bounded domains: profiles and reference data, balances and account details, recipients, quotes, transfers, batch payouts, and transfer webhooks. It bundles five read-only operating views and three narrow approval-gated payout-preparation intakes. The catalog covers every current nondeprecated OpenAPI operation explicitly marked PersonalToken plus the current quote, recipient, and profile-webhook operations Wise's SMB personal-token workflow requires. Partner-only OAuth/client-credential surfaces, deprecated duplicate versions, recipient mutations not documented for personal tokens, and simulated or embedded-partner endpoints are excluded. Funding operations remain available only for Wise-supported regions, grant-off, destructive, and approval-required every run; no bundled workflow funds money.

Wise activities, balances, balance statements, bank-account details and orders, deposit limits, total funds, and controlled balance administration. Generated from Wise's pinned OpenAPI document and bounded to the current self-service Wise Business personal-token surface. Arguments are enumerated, scalar-only requests are fail-closed, financial and identity-bearing reads avoid durable caching, reads install on, and every mutation remains grant-off and approval-gated.