# Share a Deep Research Report — Make the AI's Findings Reviewable

Canonical: https://commareports.com/agents/share-deep-research-report
Published: 2026-08-23

> Deep research output is long, sourced, and mostly unread. Publish it as HTML in Comma so reviewers can challenge a specific claim in place, and so the next run updates the same link instead of starting a new thread.

# Share a deep research report

Deep research modes produce the longest artifacts any model writes: twenty
sections, forty citations, an executive summary that is itself a page. They
are also the least reviewed. The output arrives as a wall of text in a chat
window, the recipient skims the summary, and nobody checks whether footnote 23
actually supports the sentence pointing at it.

That is not a model problem. It is a venue problem: a chat transcript has no
way to mark one sentence as suspect.

## Publish it as a document

Export the research as HTML — or have the agent post it directly:

```bash
curl -fsS -X POST https://commareports.com/api/v1/reports \
  -H "Authorization: Bearer $COMMA_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d "$(jq -n --rawfile html research.html \
        '{title: "Market landscape — payments infra", html: $html}')"
```

Agents that speak [MCP](/mcp) can do the same thing as a tool call, with the
same scoped token — see
[where should my agent post](/agents/where-should-my-agent-post) and
[scoped tokens for AI agents](/agents/scoped-tokens-for-ai-agents).

## Review the claims, not the report

The unit of review for research is the claim. On a published report, each one
can be marked:

- **Challenge a sentence in place.** "Source is a vendor blog, not the filing"
  pins to the sentence. See [commenting on HTML](/comment-on-html).
- **Mark what is verified.** Resolve the threads that check out, leave the
  rest open, and the open threads are the remaining work.
- **Let the agent answer.** It can read unresolved comments back over MCP,
  fix what it got wrong, and reply — see
  [let an agent respond to comments](/agents/let-an-agent-respond-to-comments).

## Keep it alive

Research goes stale fastest exactly where it is most useful — competitors,
pricing, regulation. A [routine](/docs/routines) re-runs the research on a
cron and PATCHes the same report, so the link a stakeholder bookmarked in
March still shows current findings in July, with every intermediate version
in the revision history.

## Limits

- **HTML body: 5 MB** — long-form research fits comfortably.
- **Scripts run, sandboxed:** `allow-scripts`, no `allow-same-origin`.
- **60 requests/minute per token.**

## Try it

Comma is free — unlimited reports, unlimited commenters, unlimited revision
history.

**[Publish a research report →](https://commareports.com/)**

### Related

- [Share HTML an AI chat generated](/agents/share-chatgpt-html-output)
- [Give an agent feedback](/agents/give-an-agent-feedback) · [Context budgeting](/agents/context-budgeting-ai-reports)
- [Cron for AI agents](/features/routines/cron-for-ai-agents) · [Where Claude Code routines post](/agents/where-do-claude-code-routines-post)