generated: '2026-08-13' method: searched source: https://docs.paragraph.com/developers authentication: style: bearer scheme: HTTP Bearer token (API key) in the Authorization header public_reads: Many read endpoints (search, feed, public publication/post fetch) require no key key_source: app.paragraph.com → Settings → API keys discovery: RFC 8414 + RFC 9728 metadata at paragraph.com (scopes api.read, api.write) agent_registration: https://paragraph.com/auth.md — anonymous register + user claim cross_ref: authentication/paragraph-authentication.yml pagination: style: cursor request_params: [cursor, limit] response_fields: [items, pagination] notes: List endpoints return { items, pagination }; follow the cursor for the next page. CLI exposes --cursor / --limit. idempotency: supported: false notes: >- No Idempotency-Key header is documented. Post updates instead use optimistic concurrency — a 409 Conflict is returned when the update body is not based on the post's current content. concurrency: style: optimistic signal: 409 Conflict on stale/mismatched update bodies (updatePost / updatePostBySlug) error_envelope: content_type: application/json shape: '{ "success": false, "msg": "message" }' rfc9457: false cross_ref: errors/paragraph-problem-types.yml rate_limiting: present: true quantified: false response_headers: [] exhaustion_status: undocumented sdk_error_code: RATE_LIMITED notes: >- Requests are rate-limited for fair usage; higher limits on request to support@paragraph.com. No number, window, scope, RateLimit-*/Retry-After header or 429 response is published — the limit is stated but not measurable. See rate-limits/paragraph-rate-limits.yml. cross_ref: rate-limits/paragraph-rate-limits.yml versioning: scheme: uri-path current: v1 stability: alpha (breaking changes possible until finalized) change_record: >- No API changelog is published; the dated record lives in GitHub Releases on the SDK, CLI and MCP repositories. See changelog/paragraph-changelog.yml. cross_ref: lifecycle/paragraph-lifecycle.yml identifiers: publications: by id, slug, or custom domain posts: by id or slug (scoped to publication) users: by id or wallet address coins: by id or on-chain contract address