Marketplace

Workflow pack for one-off expected inbound quotation emails. The entry recipe stores only bounded matching/routing state; the hidden event watcher moves a matched source pointer to owner-visible needs_owner state; an hourly timeout role moves expired watches out of active; and the review/close recipe lists needs_owner and timed_out rows before re-reading one source message for an ephemeral draft. Message bodies, deal context, and generated drafts are never persisted in data.shared, and no recipe sends email.

V3 deterministic media-inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local ffprobe CLI ingredient exposes bounded read-only media metadata operations for readiness, full stream/container JSON, compact summary JSON, and duration extraction. The operations inspect one trusted local media path and return stdout metadata; they do not transcode, decode frames to files, write outputs, materialize file_ref input into value output, recurse directories, scan devices, list sources, show packets, dump payload data, generate reports, expose arbitrary ffprobe flags, or use shell wrappers. Inputs are pinned to the file/pipe protocol whitelist and the editable path rejects scheme-like prefixes so URL inputs cannot trigger remote fetches. Requires ffprobe on PATH. Local and no-egress.

API capability pack for bounded Figma REST API operations against https://api.figma.com only. Enroll a figma connection as either OAuth bearer auth or header auth that injects X-Figma-Token for a personal or plan access token; no credential is embedded in this manifest. The pack reads the current user, files, nodes, rendered image URLs, image-fill references, file metadata, team projects, project metadata, project files, file versions, comments, reactions, published components, component sets, styles, organization activity logs, local and published variable inventories, dev resources, library analytics, and oEmbed previews for daily design-to-build workflows. Approval-gated writes are limited to creating/deleting comments, adding/removing comment reactions, applying explicit variable mutations, and creating/updating/deleting dev-resource links. The pack intentionally excludes webhook list/read/create/update/delete because Figma webhook responses include passcode secret material, plus developer-log token filters, AI usage metering, payments, SCIM, file mutation/upload, arbitrary file export downloads, broad admin configuration, OAuth token exchange, and arbitrary API passthrough.

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

V3 deterministic file-type inspection capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local file CLI ingredient exposes bounded read-only type and MIME detection for one trusted local path. The operations return only libmagic metadata on stdout: human-readable type, MIME type, MIME type with encoding, or MIME encoding. They do not return file bytes, recurse directories, read filename lists, use caller-supplied magic databases, inspect compressed contents, read special block/character devices as ordinary data, disable sandboxing, compile magic files, emit debug output, use raw unprintable output, write files, accept stdin, or use a shell wrapper. Editable paths reject flag-like values, URL-like references, and scp-style remotes. Requires file on PATH. Local and no-egress.

Drop a file, get leverage — the document and media workflows over the local CLI toolkit. extract-receipt-fields parses a dropped receipt or invoice with the local docling tool and returns merchant / total / currency / tax / date plus a spreadsheet-ready CSV row (it also fires on any inbound file, gated on a parseable MIME type). classify-inbox-file-drops fires when a file lands in data.file.received and proposes a filing category and path from the filename and MIME type alone — a proposal only, nothing is moved or renamed. convert-media-batch converts a list of dropped videos or images in one run with the local ffmpeg and imagemagick tools (video to H.264/AAC MP4 at an encoder preset, images to PNG at a geometry) and persists each result as a durable data.file; each conversion is a heavy call on the local-heavy lane, so a large batch queues rather than stampeding. diff-contract-versions parses two contract versions with docling, lifts the same named clauses from each, and diffs them clause by clause. extract-lease-key-terms reads a lease and pulls the dates, amounts, and notice windows out of it, then proposes reminders dated from the notice deadlines. assemble-evidence-packet gathers everything Recued holds on one person — their mail, matching files, and their memory timeline — into a single markdown packet file. render-weekly-report-file counts a week of your own mail and calendar into a dated markdown report, with no model call at all. No recipe here moves, renames, or deletes a file. The two staging recipes write into data.shared behind an explicit write_mode; the two file-writing recipes each write exactly one new file — their own artifact — into a file collection you nominate, and write nothing at all until you name one with the write capability. Document and media bytes move as Gateway-gated file refs and never flow through op-step values, so the model reads a parsed document by ref (which needs a document-capable model). Depends on the docling, ffmpeg, and imagemagick tool packs. Related shipped packs: media-transcribe (audio / video to transcripts and notes) and smb-invoice-finance (invoice intake staged for posting).

V3 bounded local filesystem discovery capability pack. By-value connector composition (service_kind=cli, no separate ingredient): one local find CLI ingredient exposes fixed read-only operations for readiness, file listing, directory listing, symlink listing, basename-glob search, recently modified file search, large-file search, and empty path search. Project operations run from an explicit project directory cwd supplied at execution time, accept only a trusted relative target path, cap traversal depth, and never expose arbitrary find expressions. Filesystem operations require approval because they can reveal local path names, directory shape, file sizes, modification times, symlink names, and project structure. The pack exposes no -exec, -delete, -ok, -ls, -print0, ownership/permission predicates, remote paths, absolute target traversal, parent-directory segments, caller-supplied flags, environment override, stdin, output-file write, or shell wrapper. Requires find on PATH.

API capability pack for bounded Firecrawl v2 REST API operations against https://api.firecrawl.dev/v2 only. Enroll a Firecrawl bearer API key connection named firecrawl; no credential is embedded in this manifest. The pack searches the web, scrapes one explicit page, maps URLs for one explicit site, starts and monitors crawl, batch scrape, and extract jobs, cancels one explicit crawl or batch scrape job, and reads team credit/token usage. Firecrawl may retrieve caller-supplied URLs inside its own service, but Recued egress is limited to the Firecrawl API host and the declared operations here. Writes are limited to starting one explicit crawl, batch scrape, or extract job and canceling one explicit crawl or batch scrape job. The pack intentionally excludes webhooks and callbacks, caller-supplied request headers and cookies, browser actions, arbitrary JavaScript execution, TLS verification bypass, enhanced proxy selection, cache/retention toggles, file download passthrough, team/billing/admin mutation, credential management, arbitrary Firecrawl API passthrough, and dynamic outbound callback routing.

One-install Fivetran front door over five bounded capability packs and 55 non-chat, uncached, read-only workflows. It admits 168 of 171 official operations across 99 paths. Exactly one provider-deprecated certificate route and two Connector SDK ZIP upload routes that the current REST transport cannot represent are excluded. Connections, schemas, destinations, groups, identities, teams, keys, certificates, external secrets managers, hybrid and proxy deployment, transformations, logs, and webhooks are covered. The public metadata route is isolated in a connectionless ingredient; all 167 remaining capabilities use connection-owned API-key/API-secret Basic authentication at api.fivetran.com. Nineteen operations retain their exact application/json;version=2 Accept header. Thirty-one documented cursor collections automatically request up to 1000 items per page; two ESM responses whose official requests omit cursor and limit remain explicit single-page gaps. All 64 admitted JSON bodies are required and sent verbatim because the OpenAPI omits requestBody.required. The Connector SDK download is captured as a private ZIP because its operation description contradicts the generated JSON response media. Recoverable-token and credential-capable reads remain callable but are excluded from rendering workflows. Reads are uncached and require no approval, every mutation requires approval, unsafe response integers remain exact strings, and rate-limit failures surface without hidden retries. No pipeline, account, or infrastructure object is claimed as a task, note, or user-work project Source.

Fivetran connections, schemas, connector metadata, destinations, groups, sync controls, setup tests, and trust approvals. Generated from Fivetran's hash-locked official OpenAPI 3.0.1 snapshot (e3cb53227875…) and carries 43 of the suite's 168 admitted operations. Calls are fixed to api.fivetran.com. Calls use Basic authentication with the API key and secret supplied only by the selected Fivetran connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Documented cursor collections paginate automatically; two ESM responses with no official request cursor remain honest single-page reads. Unsafe response integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. No pipeline, account, or infrastructure object is misrepresented as a task, note, or user-work project Source.

Fivetran account details, roles, system keys, teams, users, memberships, and access administration. Generated from Fivetran's hash-locked official OpenAPI 3.0.1 snapshot (e3cb53227875…) and carries 45 of the suite's 168 admitted operations. Calls are fixed to api.fivetran.com. Calls use Basic authentication with the API key and secret supplied only by the selected Fivetran connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Documented cursor collections paginate automatically; two ESM responses with no official request cursor remain honest single-page reads. Unsafe response integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. No pipeline, account, or infrastructure object is misrepresented as a task, note, or user-work project Source.

Fivetran certificates, Connector SDK package metadata, external secrets managers, HVR, hybrid agents, private links, and proxy agents. Generated from Fivetran's hash-locked official OpenAPI 3.0.1 snapshot (e3cb53227875…) and carries 45 of the suite's 168 admitted operations. Calls are fixed to api.fivetran.com. Calls use Basic authentication with the API key and secret supplied only by the selected Fivetran connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Documented cursor collections paginate automatically; two ESM responses with no official request cursor remain honest single-page reads. Unsafe response integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. No pipeline, account, or infrastructure object is misrepresented as a task, note, or user-work project Source.

Fivetran's anonymous connector-type metadata endpoint, isolated from every credential-bearing operation. Generated from Fivetran's hash-locked official OpenAPI 3.0.1 snapshot (e3cb53227875…) and carries 1 of the suite's 168 admitted operations. Calls are fixed to api.fivetran.com. The endpoint is connectionless because the official operation declares no authentication; it cannot receive an enrolled Basic credential. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Documented cursor collections paginate automatically; two ESM responses with no official request cursor remain honest single-page reads. Unsafe response integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. No pipeline, account, or infrastructure object is misrepresented as a task, note, or user-work project Source.

Fivetran log services, transformations, transformation projects, package metadata, runs, tests, and webhooks. Generated from Fivetran's hash-locked official OpenAPI 3.0.1 snapshot (e3cb53227875…) and carries 34 of the suite's 168 admitted operations. Calls are fixed to api.fivetran.com. Calls use Basic authentication with the API key and secret supplied only by the selected Fivetran connection. All documented JSON bodies are required and sent verbatim because the authority omits requestBody.required on every body-carrying operation. Documented cursor collections paginate automatically; two ESM responses with no official request cursor remain honest single-page reads. Unsafe response integers remain exact strings, reads are uncached and require no approval, and every mutation requires approval. No pipeline, account, or infrastructure object is misrepresented as a task, note, or user-work project Source.

API capability pack for bounded Fly.io Machines REST API calls against https://api.machines.dev/v1 only. Reads current token metadata, apps, machines, machine events, process lists, machine memory, machine metadata, machine versions, volumes, snapshots, IP assignments, TLS certificates, organization-wide machine/volume inventories, and platform regions. Approval-gated writes are limited to creating one app, creating or extending one volume, creating one volume snapshot, requesting or re-checking one ACME certificate, creating one machine, and single-machine lifecycle actions: start, stop, restart, cordon, uncordon, or suspend. Enroll a Fly.io API-token bearer connection named flyio. The pack intentionally excludes app/machine/volume/certificate deletes, raw command execution, arbitrary signals, secret and secret-key value reads/writes, deploy-token creation, KMS/OIDC token minting, token authorization endpoints, custom certificate upload, IP assignment mutation, and arbitrary API passthrough.

No-auth API capability pack for exchange-rate lookups through Frankfurter v2. The pack exposes current blended rates, a single currency-pair rate, and the currency catalog against https://api.frankfurter.dev only. No credential is embedded or required; recipes provide currency codes as query or path parameters.

API capability pack for bounded FreshBooks REST operations against https://api.freshbooks.com only. Reads the authenticated identity, clients, invoices, payments, estimates, expenses, projects, services, and time entries for daily solo-business accounting and time tracking. Writes cover approval-gated client upkeep, invoice draft/update/send actions, estimate draft/update actions, expense logging, and time-entry creation/update using FreshBooks' documented request wrappers. Enroll a FreshBooks OAuth bearer-token connection named freshbooks; no credential is embedded in the manifest. FreshBooks uses account_id for accounting endpoints and business_id for projects, services, and time tracking; both are discoverable from the identity endpoint. The pack intentionally excludes deletes, payment mutation/collection flows, online payment setup, invoice/estimate attachments, project/service mutation, reports, staff/admin settings, webhooks, arbitrary API passthrough, and any endpoint outside api.freshbooks.com.

Freshdesk ticket forms and fields, custom objects, jobs, account export, email, products, business hours, SLA policies, and automation rules. Generated from the hash-locked official Freshdesk API reference; no OpenAPI pin is claimed.

Freshdesk canned responses, discussion forums, topics, comments, solution categories, folders, articles, and translations. Generated from the hash-locked official Freshdesk API reference; no OpenAPI pin is claimed.

Freshdesk contacts, agents, groups, roles, skills, companies, fields, exports, and import-job administration. Generated from the hash-locked official Freshdesk API reference; no OpenAPI pin is claimed.

Workflow pack for Recued-sent Freshdesk public replies. It composes the Freshdesk capability pack with a closure ledger: send one public ticket reply through the existing Freshdesk approval gate, optionally set a configured Freshdesk numeric status such as Pending, persist only the connection/ticket reply-watch linkage in data.shared, and let a scheduled watcher re-read that exact ticket until Freshdesk reports Resolved/Closed or an owner-actionable status such as Open. This pack does not replace Freshdesk automations, dispatch rules, Observer/Supervisor rules, SLA policy, ticket views, native notifications, or helpdesk queue rules; it adds Recued-visible closure state for tickets Recued replied to.

Freshdesk ticket lifecycle, conversations, time entries, satisfaction surveys, outbound messages, and collaboration threads. Generated from the hash-locked official Freshdesk API reference; no OpenAPI pin is claimed.

One-install Datadog US1 front door over 17 stable management and observability packs plus four existing workflows. The complete generated suite admits 1,035 callable operations: 1,033 of 1,038 stable nondeprecated operations in Datadog's immutable official v1/v2 schemas plus the two still-official per-monitor mute and unmute compatibility routes documented outside the generated v1 schema. Five explicit transport exclusions are three multipart-only IdP/stegadography requests and two POST operations whose binary ZIP success responses cannot use the GET-only file_ref capture transport. Four dedicated-host event intake, log intake, On-Call paging, and product-analytics intake packs are separately installable so ordinary API access never requests ingestion or alternate-host credentials. The compatibility root keeps all 10 prior operation IDs and routes while the dependency and optional packs add 1,025 operations. The root intentionally omits a misleading partial OpenAPI pin because its compatibility surface spans two official schemas and two official documentation pages; every single-schema leaf carries its exact immutable pin and the reverse-audit fixture records all authorities. Reads are uncached, sensitive reads are marked sensitive-read, and every mutation is grant-off and approval-gated. JSON responses and generated leaf int64 inputs remain exact decimal strings; legacy root numeric inputs stay unchanged for workflow compatibility. Forty-one of 51 provider-declared pagination contracts are followed through their original route. The ten POST-search cursors nested inside JSON request bodies remain explicit because the current paginator cannot replay them without changing the documented wire shape, so automatic completeness is not claimed for those operations.

Datadog v2 audit, allowlists, authorized clients, organization connections and settings, restriction policies, and seats. 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 product-analytics ingestion through the dedicated US1 browser 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 security monitoring rules, signals, findings, filters, suppressions, critical assets, and CSM agent coverage. 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 synthetics, RUM events and replay features, RUM metrics and retention, and product analytics. 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 logs, archives, custom destinations, log metrics, observability pipelines, CI visibility, storage management, and test optimization. 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.

One-install Daytona front door over 6 bounded official domain packs and 6 non-chat, uncached, read-only workflows. It admits 277 of 288 methods from the official platform, toolbox, and analytics contracts published with the v0.199 documentation. Exact exclusions are 4 deprecated platform routes, two unsupported multipart uploads, one unsupported multipart POST response, two WebSocket streaming routes, one provider-internal toolbox initializer, and one toolbox environment update whose undeclared request media the closed request-schema gate cannot express. Platform API-key, account JWT plus organization, privileged admin, sandbox toolbox, and analytics credentials remain separate. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No task, note, or project Source is claimed for infrastructure resources.

Privileged Daytona runner, user, webhook, registry, snapshot, audit, and organization-quota administration. Generated from the hash-pinned official Daytona contract retrieved 2026-07-20. This leaf carries 24 of the suite total 277 admitted operations. Pick the isolated Daytona administrative connection whose Authorization header is a complete privileged Bearer credential. JSON request documents are sent verbatim, integer selectors use decimal strings, unsafe JSON response integers remain exact strings, and finite binary GET downloads become isolated file references. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

Read-only Daytona sandbox telemetry, trace spans, and organization usage analytics. Generated from the hash-pinned official Daytona Analytics API contract retrieved 2026-07-20. This leaf carries 8 of the suite total 277 admitted operations. Pick the Daytona analytics connection whose Authorization header is a complete Bearer API key, JWT, or admin API key. JSON request documents are sent verbatim, integer selectors use decimal strings, unsafe JSON response integers remain exact strings, and finite binary GET downloads become isolated file references. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

Daytona organizations, invitations, roles, members, regions, account links, API keys, and webhook setup. Generated from the hash-pinned official Daytona contract retrieved 2026-07-20. This leaf carries 56 of the suite total 277 admitted operations. Pick the Daytona account connection carrying the complete Bearer JWT and its X-Daytona-Organization-ID header. JSON request documents are sent verbatim, integer selectors use decimal strings, unsafe JSON response integers remain exact strings, and finite binary GET downloads become isolated file references. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

Daytona runners, regions, jobs, registries, secrets, audit, object-storage access, configuration, and health. Generated from the hash-pinned official Daytona contract retrieved 2026-07-20. This leaf carries 33 of the suite total 277 admitted operations. Pick the Daytona platform connection whose Authorization header is the complete Bearer organization API key. JSON request documents are sent verbatim, integer selectors use decimal strings, unsafe JSON response integers remain exact strings, and finite binary GET downloads become isolated file references. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

Daytona sandbox lifecycle, forks, networking, previews, telemetry, snapshots, and persistent volumes. Generated from the hash-pinned official Daytona contract retrieved 2026-07-20. This leaf carries 60 of the suite total 277 admitted operations. Pick the Daytona platform connection whose Authorization header is the complete Bearer organization API key. JSON request documents are sent verbatim, integer selectors use decimal strings, unsafe JSON response integers remain exact strings, and finite binary GET downloads become isolated file references. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

Sandbox-scoped Daytona files, Git, processes, interpreter contexts, LSP, ports, computer use, recordings, and runtime information. Generated from the hash-pinned official Daytona Toolbox API contract retrieved 2026-07-20. This leaf carries 96 of the suite total 277 admitted operations. Pick the Daytona toolbox connection whose Authorization header is the complete Bearer API key; each call also requires a sandbox ID. JSON request documents are sent verbatim, integer selectors use decimal strings, unsafe JSON response integers remain exact strings, and finite binary GET downloads become isolated file references. Reads are uncached; private reads are marked sensitive-read and every mutation requires approval. No infrastructure object is misrepresented as a task, note, or project Source.

API capability pack for bounded dbt Cloud Administrative API operations against https://cloud.getdbt.com only. Enroll a dbt Cloud API token connection named dbt-cloud that injects Authorization: Token <token> or an equivalent bearer header; no credential is embedded in this manifest. The pack reads accounts, projects, environments, jobs, runs, run steps, and run artifacts, and supports approval-gated triggering of one job run and cancellation of one run. It bundles a run-health brief, run-artifact brief, guarded job trigger, and guarded run cancel workflow. The pack intentionally excludes project, environment, job, connection, credential, group, user, invite, SCIM, service-token, webhook, audit-log export, semantic-layer, Discovery API, regional/private-host switching, retry/rerun routes, arbitrary artifact paths outside documented run artifacts, and arbitrary dbt API passthrough.

One-install Deel front door over 9 separately bounded official API domains: organization and compliance, contractors, Global Payroll, HRIS, EOR, ATS, IT, accounting, and SCIM. It bundles read-only operating views plus narrow approval-gated task, timesheet, and time-off intakes. Reads are installed on; dependency write/admin/destructive groups remain off until explicitly granted and still ask or always require approval. Worker-token self-service is intentionally a separate deel-worker pack. Credential and login-link issuance, webhook signing-key responses, password changes, multipart uploads, and presigned upload initiation are excluded.

Deel invoices, payment receipts, refund statements, credit-note breakdowns, and organization-side accounts-payable capabilities. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Deel ATS applications, candidates, jobs, postings, interviews, feedback, offers, tags, locations, departments, templates, and hiring reference data. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Deel independent-contractor contracts, amendments, milestones, tasks, timesheets, invoice adjustments, invoicing taxes, projects, off-cycle items, candidates, equity events, and termination controls. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Deel organization, legal-entity, group, manager, lookup, immigration, screening, cost-center, integration-consent, organization-task, and safe webhook-event capabilities. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Organization-side Deel Employer of Record contracts, hiring, amendments, documents, benefits, job scopes, project assignments, offboarding, terminations, and cost calculation. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Deel Global Payroll hiring, worker information, payroll cycles, reports, payslips, benefits, time tracking, shifts, and related legal-entity capabilities. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Deel people, personal information, positions, organization structures, custom fields, worker relations, time off, onboarding, offboarding, and learning capabilities. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Read-only Deel IT asset, order, and hardware-policy inventory. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Deel SCIM service-provider configuration and user read/search capabilities under the dedicated /scim/v2 surface. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

Separately connected Deel worker self-service surface for EOR worker agreements, benefits, compliance, documents, information, payslips, contractor invoices and transactions, payout methods, and onboarding. Bind a worker-scoped bearer token; organization-token workflows belong in the main Deel pack. The surface is generated from Deel's pinned aggregate OpenAPI document; documented arguments are enumerated, scalar-only requests are fail-closed, array/object-bearing schemas remain descriptive under the runtime's scalar-only closed subset, reads are default-granted, mutations remain grant-off and approval-gated, and credential/session, webhook-secret, and multipart upload operations are excluded.

API capability pack for bounded Deepgram REST API operations against https://api.deepgram.com only. Enroll a Deepgram API connection named deepgram that injects the Authorization header, commonly Authorization: Token <API_KEY>; no credential is embedded in this manifest. The pack transcribes and analyzes one explicit pre-recorded media URL, analyzes explicit text, reads public and project model catalogs, reads projects, usage fields, usage breakdowns, and project balances for meeting notes, call analytics, media intelligence, product research, compliance review, usage monitoring, and model inventory workflows. Transcription and text analysis are synchronous JSON read-tier inference calls that consume Deepgram quota but do not create durable customer resources through this pack. The pack intentionally excludes WebSocket streaming, turn-based audio, voice-agent configuration and variables, token generation, binary file upload, binary text-to-speech output, callback and callback_method parameters, arbitrary extra metadata, project/key/member/invite/request mutations or deletes, self-hosted distribution credentials, billing purchase exports beyond balances, regional/custom host switching, arbitrary Deepgram API passthrough, dynamic outbound callbacks, and any operation outside api.deepgram.com.