BITCOIN STRATIGRAPHY / INTEGRATION SUITE

Python SDK & Agent Cookbooks

Integrate 16 live MCP tools across 5 namespaces with LangChain, LlamaIndex, CrewAI and AutoGen. The HTTPX-based Python SDK/client supports JSON-RPC discovery and explicit, bounded L402 Lightning payment callbacks. Download the source and examples below.

Our enterprise security architecture combines Stateless MCP 2026-07-28 transport, NIP-98 agent identity headers, and Ed25519 signed response verification to detect tampered tool responses and help defend against indirect prompt injection.

Deploying internally? Request Commercial Enterprise License

Framework Integration: native MCP agents

All 16 canonical tools plug into LangChain and LlamaIndex with L402 batch-payment support: 100 tool-scoped calls for 25,000 sats. Inject prepaid Macro-Macaroon headers or connect to a trusted local wallet proxy. Discovery is free; the adapters never pay automatically.

Native LangChain agent

Official langchain.mcp MCPAdapter and a ReAct tool-calling loop. Dependencies
Native LlamaIndex agent

BasicMCPClient, McpToolSpec and ReActAgent. Dependencies
Native framework setup, credentials and proxy guide

SDK, setup guide and framework examples

Python SDK/client
HTTPX transport, catalog validation, invoice verification and explicit payment hooks.
CrewAI integration
Connect agent workflows to the live Stratigraphy MCP server.
LangChain integration
Use the remote MCP catalog from LangChain workflows.
AutoGen integration
Use the remote MCP tools in AutoGen agent workflows.
Setup & payment guide
Installation, safe defaults, wallet callbacks and run commands.
Dependency requirements
Core client requirements; install optional framework dependencies separately.

Free batch POST pricing

Send {"tools":["stratigraphy.get_latest","proof.verify_zk_proof"]} to POST /api/v1/cost for itemized satoshi quotes, a batch total and L402 invoice-generation details. These descriptive selectors are pricing-only mappings to stratigraphy.get and proof.verify.

Quotes do not create or pay invoices. Each paid MCP tool call returns its own HTTP 402 challenge; a batch total is not a multi-tool credential. Examples never pay invoices unless you explicitly configure a payment hook.