DELIVERY

Three delivery surfaces. One security layer.

Serve governed financial data to authorized agents and integrations through MCP, REST, or the CLI under one delivery-policy contract.

The problem

Every team wants GL data somewhere different — an assistant in Claude, a dashboard over REST, a job in CI. Wire each up separately and security drifts surface to surface.

How it works

Approved data for each configured surface

Your ERP / GL

Raw ledger data from any source system

PipeLedger transformations

scope · privacy · publication

Published dataset

snapshot · As of 2026-Q2 · certified

MCP, REST, and CLI all read the published dataset

MCP

For AI assistants

Ask questions in plain language and get governed answers — e.g. in Claude.

REST

For apps & dashboards

Feed the tools your team already uses every day, over a versioned API.

CLI

For autonomous agents

High-frequency infrastructure that runs unattended in any pipeline.

Source provenance

Bounded publication evidence appropriate to each operation and surface

Supporting detail

pl_drilldown — governed and re-authorized for the caller

Protocol

JSON-RPC transport · MCP version negotiation · strict tool inputs

Surfaces

MCP, REST & CLI — identical scope and masking