External integrations
Public Legal API is a preview with static client configuration and in-memory quotas. MCP is unimplemented.
The Public Legal API is a preview facade over Legal Core. Its server validates external tokens, applies configured client scopes and projects responses. It is not yet a complete production integration-management platform. MCP is unimplemented.
flowchart LR
Client["External client"] --> Public["Public Legal API preview"]
Public --> Verify["JWT and configured client/scope checks"]
Verify --> Core["Legal Core via new workload token"]
Core --> Data[("Legal PostgreSQL")]
MCP["MCP: target only"] -.-> Public
Implemented preview
Section titled “Implemented preview”services/public-legal-api/cmd/server/main.go loads registrations from PUBLIC_LEGAL_CLIENTS_JSON and tracks quotas in process memory. Its tests and tests/suites/legal-api/live-gateway.yaml exercise authenticated requests through Legal Core.
The facade mints a downstream workload token instead of forwarding an external token unchanged. This keeps external issuer trust at one boundary and lets Legal Core apply its own audience and content policy. Response projection restricts returned fields; original-binary delivery remains a private capability.
Target work
Section titled “Target work”Durable registration and revocation, coordinated quotas across replicas, key-rotation operations, durable usage receipts and MCP delegated-user consent still need implementation. In-memory limits reset with a process and cannot serve as a distributed entitlement guarantee.
A future MCP adapter should expose typed application operations and validate arguments because model-generated input is untrusted. There is no MCP adapter or specialist-operation endpoint in the current API contract.
The API overview links the actual OpenAPI surfaces.