← Protocols
Paragraph
Social / Messaging·EVM · Multi-chain

Paragraph

01Description

All-in-one publishing and newsletter protocol with Web3-native primitives: permanent storage, wallet-native subscribers, crypto payments, post coins, and writer coins. Absorbed Mirror in late 2025 and is now the default onchain publishing platform.

02Best for
  • 01newsletters with wallet-native subscribers
  • 02onchain publishing + permanent archives
  • 03post / writer coins for monetisation
  • 04Mirror migration / archive reads
  • 05AI agents publishing or consuming articles via MCP
03Install
  • pnpm add @paragraph-com/sdk
04Environment variables
VariableScopeDescription
PARAGRAPH_API_KEYServerParagraph API key from your publication settings. Server-only — required for authenticated writes (create/update/delete posts, manage subscribers).
NEXT_PUBLIC_PARAGRAPH_PUBLICATION_IDClientSlug or id of your Paragraph publication, used by the SDK for scoped reads.
05Prompt snippet
Use Paragraph for onchain publishing and newsletters. Instantiate `const client = new ParagraphAPI({ apiKey: process.env.PARAGRAPH_API_KEY })` from `@paragraph-com/sdk`. Read with `client.posts.list({ status: 'published' })`, `client.posts.get(slug)`, `client.me.get()`. Write with `client.posts.create({ title, content, status })` and `client.posts.update(id, { ... })` — keep these calls server-side to avoid leaking the API key. Public read endpoints work without auth, so static feeds (`/blog`, RSS, sitemaps) can be ISR-cached. For AI agent integrations, expose your publication through the Paragraph MCP server so agents can fetch and summarise posts.
06Gotchas
  • Multi-chain reach via wallet subscribers, but the post storage is hybrid — drafts/metadata live in Paragraph's hosted DB, only published artefacts get pinned onchain/Arweave. Treat the hosted layer as the source of truth for unpublished work.
  • Onchain vs offchain content: writer/post coins and subscriber NFTs are onchain (EVM); article bodies are off-chain markdown referenced by hash. Don't assume a tx confirmation means the body is durable until pinning completes.
  • Migrated Mirror posts kept their Arweave tx ids but new Paragraph slugs — link by the new canonical URL, not legacy mirror.xyz paths, to avoid 404s.
  • Content moderation surface: Paragraph hosts a public reader at paragraph.com and applies platform-level moderation; self-hosted readers via the API must implement their own moderation/abuse layer.
  • API rate limits apply per key — bulk-imports of historical posts will 429 if you don't backoff. Use the dashboard import flow for >100 posts.
  • Free vs paid features differ: writer coins, custom domains, and high subscriber counts gate behind paid tiers — confirm tier before promising launch features.
07Alternatives