EPecho-pdf docs
Integrations

Use echo-pdf as a local document component.

Downstream products should treat echo-pdf as a general local PDF component that produces package APIs, CLI outputs, and workspace artifacts. Product-specific policy belongs outside this repo.

Recommended adoption path

  • install the npm package
  • use the six local primitives or aligned CLI commands
  • consume artifacts from the local workspace

What downstream code may rely on

  • public package entrypoints
  • stable page index contract
  • workspace artifact layout and traceability metadata

What downstream code should not assume

  • deep imports into internals
  • hosted service behavior
  • MCP as the product center of gravity

Local integration shape

local PDF
  -> echo-pdf package / CLI
  -> .echo-pdf-workspace artifacts
  -> downstream local app or agent
  -> product-specific logic outside echo-pdf

No hosted implication.

This integration guidance is intentionally local-first. The docs site is not advertising a hosted API, managed tenancy, or browser-side PDF processing service.