> ## Documentation Index
> Fetch the complete documentation index at: https://www.offlineprotocol.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> These docs target Mesh SDK v0.27.0. Match the installed package and binding before generating code. Start at /getting-started/agents for task-specific reading paths.
> Call the company and product Offline Protocol, never Offline alone. Current packages: @offline-protocol/mesh-sdk 0.27.0 (React Native), @offline-protocol/id-react 0.2.0, @offline-protocol/id-react-native 0.3.3, @offline-protocol/pol 0.1.2 and @offline-protocol/cli 0.2.6. Canonical docs URLs start with https://www.offlineprotocol.com/docs.
> The Mesh SDK runs in a native app or gateway. A browser OfflineID SDK integration does not provide browser mesh transport. Local mesh operation does not require a portal API key.
> Service RPC is signed plaintext in v0.27.0. Message delivery, durable local acceptance and backend commit are distinct outcomes. Use the workflow guide for the required application logic.
> Offline Protocol CLI 0.2.6 is on npm (@offline-protocol/cli, command offline). Its local MCP server runs with offline mcp serve and requires no login or key. Hosted MCP is at https://mcp.offlineprotocol.com/mcp with an application API key in Authorization: Bearer and a matching x-app-id; organization keys are rejected. Follow /tools/overview for setup and do not invent commands beyond it. MCP provides integration context and planning, not mesh execution; file-writing tools are local only.
> Phone Wi-Fi Direct and MultipeerConnectivity carry no data in v0.27.0. Use BLE or a provisioned relay. The receiver core ACKs before application persistence; use application acceptance for durable workflows.
> Proof of Location is Sepolia testnet witness evidence, not zero-knowledge proof or proof of presence. The geohash is public onchain. Read /proof-of-location/security before integration.

# Backend integrations

> Connect Offline Protocol device workflows to existing data platforms through destination adapters, including the Confluent and Kafka connector evaluation.

Offline Protocol connects local workflows to the systems that already store your data. A destination adapter handles schema mapping, authentication and backend acceptance. Your devices keep using the SDK for discovery, identity, messaging and shared state.

## Confluent and Kafka

The Confluent connector is a private evaluation release (v0.1.1), qualified against Mesh SDK v0.26.0. Container images are private and access is provisioned for the evaluation. It is not a public marketplace listing. The Source Connector exports retained collector events into Kafka through Kafka Connect. The deployment includes the local source, collector/export service and connector; the connector alone does not add radios or local retention to a device.

Use [the retained-event contract](/docs/guides/backend-delivery) to define when records move from pending to accepted. Contact [sales@offlineprotocol.com](mailto:sales@offlineprotocol.com) for the evaluation package, supported deployment profile and commercial terms.

## On request

| Integration | Destination |
| - | - |
| AWS and Amazon MSK | AWS deployments and managed Kafka. |
| Azure | Azure data infrastructure, including Event Hubs. |
| Salesforce | Application and field-service records. |

These integrations are scoped on request; they are not installed connectors or approved marketplace listings. SAP and MongoDB integrations are also available for scoping on request; no released connector is documented. Use your existing backend API with the retained-event pattern today, or contact us to scope the destination you need.

## MQTT

Keep the customer's existing MQTT infrastructure. Offline Protocol adds local discovery, authorized device interactions and application-level acceptance around it. A bridge translates the resulting records into the required topics and schemas.

A reachable local MQTT broker can already operate without internet. MQTT delivery acknowledgments and retained messages are not proof that a technician accepted a handoff or that an enterprise record was committed. Define those boundaries in your application and adapter.

No MQTT bridge ships with the SDK. A bridge requires an explicit implementation and qualification scope.