langchain-delta-registry
28 pay-per-event regulatory, sanctions, procurement, and corporate-registry monitoring tools for
LangChain agents, backed by
Apify's hosted MCP gateway. Every tool's Pydantic input schema is
generated directly from the underlying Apify actor's own real .actor/input_schema.json — never
hand-written, so it can't silently drift from what the actor actually accepts.
Install
pip install langchain-delta-registry
Quickstart
import os
os.environ["APIFY_TOKEN"] = "..." # get one at https://console.apify.com/settings/integrations
from langchain_delta_registry import DELTA_REGISTRY_TOOLS
from langchain.agents import create_agent
agent = create_agent("gpt-4o", tools=DELTA_REGISTRY_TOOLS)
Or import a single tool directly, without loading all 28:
from langchain_delta_registry.actor_19_maritime_sanctions_monitor import actor_19_maritime_sanctions_monitor_tool
result = actor_19_maritime_sanctions_monitor_tool.invoke({"vesselNameContains": "ARTAVIL"})
Authentication
Every tool reads APIFY_TOKEN from the environment at call time — never hardcoded, never passed
as a constructor argument, never read from a config file. Get a token from the
Apify Console. This library does not issue,
broker, or proxy that token in any way; it is sent directly to api.apify.com over HTTPS.
Pricing
Every actor bills strictly per delivered event (pay-per-event) — no subscriptions, no minimum spend. Unchanged records across runs are never re-billed. See each actor's real, current pricing on its Apify Store page — pricing is not duplicated here to avoid it going stale relative to the authoritative source.
Reliability
Every tool call goes through a shared, production-hardened HTTP client
(langchain_delta_registry._client): bounded exponential-backoff retry (3 attempts, full jitter)
for transient failures (429, 5xx, network errors), no retry for real 4xx client errors, a 320-second
timeout (Apify's own real cap on run-sync-get-dataset-items is 300s), and a structured
DeltaRegistryAPIError exception carrying the real HTTP status and response body rather than a
bare requests exception.
The 28 actors
| Tool name | Real Apify actor |
|---|---|
actor-18-b2b-lead-magnet |
B2B Lead Enrichment Engine |
actor-19-maritime-sanctions-monitor |
Maritime Sanctions Watchdog |
actor-20-mdb-procurement-monitor |
World Bank Procurement & Debarment Monitor |
actor-21-patent-ip-enforcement-monitor |
Patent & IP Enforcement Monitor |
actor-22-drug-safety-recalls-monitor |
Drug Safety & Recall Monitor |
actor-24-clinical-trials-delta-engine |
Clinical Trial Data Extractor |
ai-crawler-content-signal-permission-monitor |
AI Crawler Permission Monitor |
aozora-bunko-public-domain-text-feed |
Aozora Bunko Public-Domain Feed |
australia-grantconnect-monitor |
Australian Government Grants Monitor |
cordoba-compras-monitor |
Cordoba Government Tenders Monitor |
diario-oficial-cl-monitor |
Chile Official Gazette Monitor |
emerging-market-sovereign-debt-auction-monitor |
Sovereign Debt Auction Monitor |
entrerios-compras-monitor |
Entre Rios Government Tenders Monitor |
eu-ted-procurement-delta-monitor |
EU TED Procurement Monitor |
florida-tenders-monitor |
Florida State Procurement Monitor |
kipris-patent-trademark-status-monitor |
KIPRIS Patent & Trademark Monitor |
mendoza-compras-monitor |
Mendoza Government Tenders Monitor |
page-metadata-extractor |
Page Metadata Extractor |
pba-tenders-monitor |
Buenos Aires Province Tenders Monitor |
regione-lombardia-grants-registry-monitor |
Lombardy Grants & Tenders Monitor |
salta-compras-monitor |
Salta Government Tenders Monitor |
santafe-compras-monitor |
Santa Fe Government Tenders Monitor |
sec-enforcement-litigation-delta-feed |
SEC Enforcement & Litigation Feed |
singapore-acra-registry-monitor |
Singapore ACRA Registry Monitor |
tucuman-compras-monitor |
Tucuman Government Tenders Monitor |
uae-corporate-registry-monitor |
UAE Corporate Registry Monitor |
uk-hse-enforcement-monitor |
UK HSE Enforcement Monitor |
uk-modern-slavery-statement-registry-monitor |
UK Modern Slavery Statement Registry Monitor |
Also available for
- MCP (Model Context Protocol):
io.github.stefanoseggio/delta-registryon the Official MCP Registry, and Smithery. - OpenAI, Anthropic, Gemini, LlamaIndex, CrewAI, AG2: per-actor tool definitions at
https://delta-registry-website.vercel.app/schemas/{actor-slug}/.
Source & regeneration
Every file in src/langchain_delta_registry/ except _client.py is generated by
lib/schema-generator/langchain-package-generator.ts
in the delta-registry-website
repository, from each actor's real, live-verified .actor/input_schema.json. Do not hand-edit a
generated file — regenerate it instead, or the next regeneration will silently overwrite your
change.
License
Apache-2.0
Release files for langchain-delta-registry 1.0.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| langchain_delta_registry-1.0.2.tar.gz | 55.8 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| langchain_delta_registry-1.0.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 141.6 kB
Release files / langchain_delta_registry-1.0.2.tar.gz
| Download URL | langchain_delta_registry-1.0.2.tar.gz |
|---|---|
| Size | 55.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
343a5c3922ac358a1d44defc0e2ce726114cb2273703742c093ede318f94f48d
|
|
BLAKE2b-256 checksum How to use checksums |
ce29e3b839c7bcd185c44858f24828d9f5c1b12f36308dc4c0b5416ff29d5951
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency logRelease files / langchain_delta_registry-1.0.2-py3-none-any.whl
| Download URL | langchain_delta_registry-1.0.2-py3-none-any.whl |
|---|---|
| Size | 85.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c80536c1e40f47a57dc5ee96aca21b8bd347aff8341bde4a7fefa3733049fd1f
|
|
BLAKE2b-256 checksum How to use checksums |
2b4a471bb11af5937017cf6b258be2336b2057f7299756c0caefc6dd7a85230d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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 Sep 18, 2026.
Transparency log