---
title: Integration checklist
description: A safe, mock-first sequence for coding agents that add Social SDK to an existing application and verify the result.
---

Use this sequence when integrating Social SDK into an existing application.

1. Identify the required platform, operation, content formats, runtime, and tenant model.
2. Select a direct or managed backend from current capability evidence.
3. Keep all credentials and native clients in server-only modules.
4. Build the account membership check before accepting an account reference from application input.
5. Implement the flow with the deterministic testing backend and explicit scenarios.
6. Preserve per-target outcomes. Do not translate accepted, queued, or processing states into published.
7. Handle uncertain writes through status reconciliation before retrying.
8. Add provider-specific webhook verification before parsing or acknowledging events.
9. Run the packed-consumer and runtime checks for the imports the application uses.
10. Request human credentials, platform approval, mutation authorization, or spend authorization only for the remaining live step.

The documentation site is static. It publishes Markdown pages and `llms.txt`, but it does not advertise a live MCP endpoint. Use the repository's integration skill for the complete implementation workflow once its examples and commands have been verified against the released package.