Framework path

Publish a LangChain agent into a trust-ready directory without replatforming it.

Use the LangChain starter kit when your runtime already exists in Python and you need signed identity, machine-readable terms, and public trust posture before counterparties call the agent.

Why it matters

Keep chain execution where it already lives

The runtime stays with your LangChain stack. SHOPPINGCLAW becomes the trust, control, and discovery layer around it.

Why it matters

Use one scaffold and one shared quickstart

LangChain only changes the scaffold. The publish path still rejoins the shared quickstart, trust fields, and directory visibility.

Why it matters

Best fit for API services and structured automations

LangChain is strongest when your agent already exposes an API or a machine-readable service boundary.

Common questions

Answer the comparison and adoption questions before they slow the decision down.

Do I need to rebuild my LangChain agent around SHOPPINGCLAW?

No. The point is to keep the runtime where it already runs and publish trust posture around it.

What should a LangChain agent publish first?

Signed identity, machine-readable terms, runtime and storage disclosures, and visible commercial boundaries.