Integrations

Traceability, payments, storage, email, AI chat and MCP.

State traceability

An IntegrationInstallation with providerType: "traceability" is created at onboarding with the provider code you supply. Outbox events record each reportable action. See Reconciliation.

Payments

Cash, debit terminals and Aeropay. See Payment providers. For non-cash tenders finalizeCannabisSale requires the terminal approval reference.

Storage

S3-compatible storage through S3_BUCKET_NAME, S3_REGION, S3_ACCESS_KEY_ID, S3_SECRET_ACCESS_KEY and S3_ENDPOINT. Public menu images use the publicImageUrl text field.

Email

features/keystone/lib/mail.ts sends password-reset email when SMTP_HOST, SMTP_PORT, SMTP_USER and SMTP_PASSWORD are set. SMTP_FROM sets the sender and SMTP_STORE_LINK the link base.

AI chat and MCP

/api/completion powers the dashboard chat via OpenRouter (OPENROUTER_API_KEY, OPENROUTER_MODEL, OPENROUTER_MAX_TOKENS). Shared keys need a signed-in session with canAccessDashboard. /api/mcp-transport/[transport] returns HTTP 503, so the chat has no data tools.

Adding a provider

Write a code-owned adapter, keep credentials out of GraphQL, logs, audit metadata and outbox payloads, authenticate inbound traffic, make retries idempotent, then register the capability in features/keystone/domain/runtimeCapabilities.ts.

On this page