> ## 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.

# Find an SDK API

> Choose a focused React Native API reference by task, with links to working guides and event payloads.

These references target `@offline-protocol/mesh-sdk@0.27.0`. They are generated from the published package. Start with a [workflow](/docs/mesh-sdk/overview#build-by-workflow) for integration steps; use the pages below when you need an exact signature.

| Task | Reference | Start with |
| - | - | - |
| Lifecycle and listeners | [OfflineProtocol](/docs/mesh-sdk/api/lifecycle) | [Guide](/docs/getting-started/quickstart) |
| Messaging and receipts | [OfflineProtocol](/docs/mesh-sdk/api/messaging) | [Guide](/docs/guides/local-handoff) |
| Device identity and sessions | [OfflineProtocol](/docs/mesh-sdk/api/identity) | [Guide](/docs/mesh-sdk/identity) |
| Groups and membership | [OfflineProtocol](/docs/mesh-sdk/api/groups) | [Guide](/docs/guides/shared-state) |
| Files and media | [OfflineProtocol](/docs/mesh-sdk/api/files) | [Guide](/docs/mesh-sdk/setup-rn) |
| Transports and routing | [OfflineProtocol](/docs/mesh-sdk/api/networking) | [Guide](/docs/getting-started/platforms) |
| Telemetry controls | [OfflineProtocol](/docs/mesh-sdk/api/telemetry) | [Guide](/docs/mesh-sdk/configuration) |
| DataStore methods | [DataStore](/docs/mesh-sdk/api/data) | [Guide](/docs/guides/shared-state) |
| MeshServices methods | [MeshServices](/docs/mesh-sdk/api/services) | [Guide](/docs/guides/nearby-service) |

## Full references

[All method signatures](/docs/mesh-sdk/methods), [event payloads](/docs/mesh-sdk/events) and [configuration types](/docs/mesh-sdk/configuration-types) remain available for a complete lookup. Existing method and event URLs are preserved.

For Python use [the Python binding guide](/docs/mesh-sdk/python); these TypeScript signatures are not the Python API. For hosted HTTP APIs use [Identity and hosted APIs](/docs/api-reference/introduction).

[All public types](/docs/mesh-sdk/public-types) and [error codes](/docs/mesh-sdk/errors) complete the reference.