Area guide · 60 packages · Find a capability-level provider contract
Integrations and provider selection
Choose concrete external capabilities through provider-neutral contracts, explicit connections and observable runtime bindings.
What are you trying to do?
- Where is the portable interface for a provider capability?
- How do connection credentials differ from runtime mode?
- What makes a provider supported for a particular operation?
Why start with these packages
Suggested entry point
@lssm-tech/lib.contracts-integrationsStart with integration specs, connections, secrets, provider interfaces and runtime/health contracts.
Suggested entry point
@lssm-tech/lib.provider-specInspect routing, runtime-target, observation, execution-receipt and comparison contracts.
Suggested entry point
@lssm-tech/lib.provider-runtimeUse runtime-target, routing and receipt normalization shared by provider hosts.
Suggested entry point
@lssm-tech/module.integration-hubInspect reusable integration-management composition for a selected product.
Practical steps
Step 01
Select the exact interface
Read the consumer’s provider contract and list the methods or capability references it needs. Open the matching integration package export map and README rather than importing a broad implementation bundle by default.
Step 02
Bind a scoped connection
Identify the credential owner, runtime target, secret resolver and required permissions. Follow how the product checks readiness and handles a missing capability or disconnected account before offering an action.
Step 03
Inspect a provider result
Trace the adapter response into the normalized receipt and domain outcome. Use the owning fixture for denial, throttling and uncertain completion, then qualify real provider behavior in the intended environment before advertising it as available.
Begin with a capability, not a vendor name
ContractsIntegrations defines provider-agnostic specifications, connections, authentication/transport, secret resolution, health and capability interfaces such as LLM, embeddings, email, vector stores and storage. The provider integration packages implement concrete boundaries. Start from the operation your product needs, find its capability contract, then inspect the adapter that claims that exact surface. A provider package name or a registered catalog record does not establish that every provider product feature is supported or enabled for an account.
Keep execution mode separate from credentials
ProviderSpec describes runtime targets, routing policies, leases, receipts, observations and comparison evidence. ProviderRuntime normalizes those records for host use. The README distinguishes managed/local/hybrid runtime targets from credential ownership modes such as BYOK, ephemeral or none. Preserve that distinction in configuration and UI so a credential selection does not silently choose an execution location. Redact credential-like resolver fields before logging while retaining non-secret mode and capability information needed for diagnosis.
Inspect the whole connection lifecycle
A useful integration guide should follow connection creation, required scopes/capabilities, secret references, readiness, one operation and its returned receipt. Reconnection, revoked access, rate limits, stale health and ambiguous effects belong to the same story. Provider observations can inform routing and budget decisions, but source metadata still needs the host’s current evidence. For capabilities such as meeting capture or external publication, domain consent and current authorization remain prerequisites even when the provider SDK is available.
Follow a practical path.
Select the exact interface
Read the consumer’s provider contract and list the methods or capability references it needs. Open the matching integration package export map and README rather than importing a broad implementation bundle by default.
Bind a scoped connection
Identify the credential owner, runtime target, secret resolver and required permissions. Follow how the product checks readiness and handles a missing capability or disconnected account before offering an action.
Inspect a provider result
Trace the adapter response into the normalized receipt and domain outcome. Use the owning fixture for denial, throttling and uncertain completion, then qualify real provider behavior in the intended environment before advertising it as available.
Packages in this area (60)
60 of 60 shown
- Open manual →
MCP server exposing ALPIC application lifecycle and platform integration operations.
- Open manual →
MCP server exposing governed Notion workspace operations.
- Open manual →
MCP server for provider discovery, evaluation, and ranking workflows.
- Open manual →
MCP server exposing governed Microsoft Teams collaboration operations.
- Open manual →
Alpic MCP server and ChatGPT App hosting bundle
- Open manual →
Read-first App Store Connect API integration for ReviewReady app submission readiness, with deterministic mocks and secret-ref-only credentials.
- Open manual →
Telegram Builder control-channel integration.
- Open manual →
Voice Builder input integration.
- Open manual →
WhatsApp Builder control-channel integration.
- Open manual →
Example plugin: Markdown documentation generator for ContractSpec specs
- Open manual →
Fake/sandbox outbox adapter for builder delivery loop testing.
- Open manual →
Read-first Google Play Android Publisher API integration for ReviewReady app submission readiness, with deterministic mocks and secret-ref-only credentials.
- Open manual →
Tenant-scoped append-only Postgres evidence adapter for Integration Hub topology receipts.
- Open manual →
Analytics provider implementations for ContractSpec.
- Open manual →
Attio API, webhook, and hosted MCP integration for ContractSpec.
- Open manual →
Calendar provider implementations for ContractSpec.
- Open manual →
Claude Code provider compatibility wrapper for Builder.
- Open manual →
Clay API, webhook, and hosted MCP integration for ContractSpec.
- Open manual →
Codex provider compatibility wrapper for Builder.
- Open manual →
Read-only governed source adapters for CompanyOS metrics.
- Open manual →
Copilot provider compatibility wrapper for Builder.
- Open manual →
Provider adapters for SupportOS, beginning with a version-pinned Intercom mirror and cutover lane.
- Open manual →
Database provider implementations for ContractSpec.
- Open manual →
French Factur-X (EN16931 CII) generation, EN16931/CIUS-FR conformance (Mustangproject), and PDP submission adapters for ContractSpec BillingOS.
- Open manual →
Email provider implementations for ContractSpec.
- Open manual →
Gemini provider compatibility wrapper for Builder.
- Open manual →
GitHub provider implementation for ContractSpec with repository, issue, and pull request management.
- Open manual →
Official advertising API request adapter.
- Open manual →
Health data provider implementations for ContractSpec.
- Open manual →
Tenant-isolated asynchronous Higgsfield media provider.
- Open manual →
Official Instagram API read adapters for ContractSpec.
- Open manual →
Official LinkedIn API adapters for ContractSpec.
- Open manual →
LLM provider implementations for ContractSpec.
- Open manual →
Local model provider compatibility wrapper for Builder.
- Open manual →
Meeting recorder provider implementations for ContractSpec.
- Open manual →
Messaging provider implementations for ContractSpec.
- Open manual →
Official advertising API request adapter.
- Open manual →
Open banking provider implementations for ContractSpec.
- Open manual →
OpenCode Go provider compatibility wrapper for Builder.
- Open manual →
Payments provider implementations for ContractSpec.
- Open manual →
Pioneer AI provider adapter for ContractSpec AI improvement workflows.
- Open manual →
Project management provider implementations for ContractSpec.
- Open manual →
Signed Reclaim Scheduling Link webhook ingestion for CompanyOS OPA.
- Open manual →
SMS provider implementations for ContractSpec.
- Open manual →
Object storage provider implementations for ContractSpec.
- Open manual →
Speech-to-text provider compatibility wrapper for Builder.
- Open manual →
Official TikTok social provider adapter for ContractSpec.
- Open manual →
Voice, speech, and conversational provider implementations for ContractSpec.
- Open manual →
Governed web access, scraping, browser, MCP, and residential proxy integrations.
- Open manual →
Official X API read and scoped native publication adapters for ContractSpec.
- Open manual →
Official YouTube social provider adapter for ContractSpec.
- Open manual →
Integration provider implementations for email, payments, storage, and more
- Open manual →
Unified AI provider abstraction layer
- Open manual →
Integration contract definitions for external services
Start with integration specs, connections, secrets, provider interfaces and runtime/health contracts.
- Open manual →
AI provider ranking: benchmark ingestion, scoring, and model comparison
- Open manual →
Builder provider-runtime helpers for routing, context prep, runtime targets, and receipt normalization.
Use runtime-target, routing and receipt normalization shared by provider hosts.
- Open manual →
Provider routing and runtime-target contracts for ContractSpec Builder.
Inspect routing, runtime-target, observation, execution-receipt and comparison contracts.
- Open manual →
Alpic MCP and ChatGPT App hosting helpers
- Open manual →
Scoped integration-hub module — 3 genuinely reusable primitives (useIntegrationData, useCredentialSetup, renderIntegrationMarkdown) promoted from examples/integration-hub. RSC-directive boundaries are explicit.
Inspect reusable integration-management composition for a selected product.
- Open manual →
AI provider ranking module with persistence and pipeline orchestration
What connects to this area
Core contracts
The consumer needs a declared capability and operation boundary.
Identity and access
A connection is usable only in its current trusted scope.
Agents and context
Agent model/tool routes consume explicit provider capabilities.
Delivery and infrastructure
Execution targets and infrastructure providers have their own operational ports.