Skip to main content

LangChain Reach Dog tools

Add product enrichment, market research and catalog grouping to a LangChain application.

pip install langchain-reachdog==0.1.0

Sign in to the Reach Dog developer console, create your account's API key, and set REACHDOG_API_KEY in your environment. Every account receives daily free tokens, and API calls use your account's wallet. Your API key's scopes must cover the operations you select.

First request

This example previews a product request and asks you to approve the estimate before sending it.

import json
import os
from langchain_reachdog import ReachDogBudget, ReachDogClient, ReachDogTitleTool


def approve(details):
    print(json.dumps(details, indent=2))
    return input("Approve this request? [y/N] ").strip().lower() == "y"


client = ReachDogClient(
    base_url="https://api.reach.dog",
    api_key=os.environ["REACHDOG_API_KEY"],
)
budget = ReachDogBudget()
tool = ReachDogTitleTool(
    client=client,
    budget=budget,
    account_label="my-application",
    require_confirmation=approve,
)
request = {"body": {"title": input("Product title: "), "parameters": ["product_type"]}}
print(tool.invoke(request))
print(tool.invoke({**request, "confirm": True}))

ReachDogResearchTool and ReachDogCatalogTool share the same client, budget and approval callback. Set ReachDogBudget(max_tokens=YOUR_LIMIT) to constrain estimated spending across an agent run. The unit is Reach Dog billing tokens. The default approval callback declines. Catalog processing uses quote, accept and status actions, and payment retry requires approval again. Reuse run_label when recovering the same operation. Change it when deliberately requesting new work.

See the API reference and catalog workflow for scopes, request bodies and payment recovery. Report bugs in GitHub issues with the package version and error code.

The vendored client and helpers are based on reachdog/reachdog-ecommerce-toolkit at 6437f3b. The client records ambiguous retries for budget accounting. The package is MIT licensed. API calls use your Reach Dog account's available tokens.

Metadata

Release files for langchain-reachdog 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for langchain-reachdog 0.1.0
File Size Uploaded Provenance Actions
langchain_reachdog-0.1.0.tar.gz 17.2 kB With provenance Details for langchain_reachdog-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for langchain-reachdog 0.1.0
File Interpreter ABI Platform Actions
langchain_reachdog-0.1.0-py3-none-any.whl Python 3 none any Details for langchain_reachdog-0.1.0-py3-none-any.whl

Total release size: 33.0 kB

Release files / langchain_reachdog-0.1.0.tar.gz

Download URL langchain_reachdog-0.1.0.tar.gz
Size 17.2 kB
Tags Source
SHA-256 checksum
How to use checksums
37d6477bdeb17822fe10d97084c32914f0adcaa510b9def267ea64faffc46f0e
BLAKE2b-256 checksum
How to use checksums
0a4b22177f5933772767d099720a1ed84caa115c13d49c02e5b0df7d92312e14
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

Release files / langchain_reachdog-0.1.0-py3-none-any.whl

Download URL langchain_reachdog-0.1.0-py3-none-any.whl
Size 15.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
0f040864d8ed382f9533a051009fe57611be3aca59ffd9f57727fc1b0a38e0d8
BLAKE2b-256 checksum
How to use checksums
4456d007e4855a643499e8a4f86bf9a1ebfb41a1e92759d2501c8f6be741d3b1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/7.0.0 CPython/3.13.16

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

Security for langchain-reachdog 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for langchain_reachdog-0.1.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Nov 9, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files Full provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page