Barndoor - Forge

Forge connects to the Barndoor Platform API for configuration inventory and accepts Barndoor audit exports for activity evidence. Provider-native policy decisions remain identified as Barndoor decisions rather than Forge inline enforcement.

API coverage

Endpoint	Imported data
`/api/agents`	Agents and agent metadata
`/api/servers`	MCP servers
`/api/servers/{id}`	Server configuration and tool catalog
`/api/servers/{id}/connection`	Server connection posture
`/api/v2/policies`	Policies and summary state
`/api/v2/policies/{id}`	Policy rules and target detail
`/api/v2/policies/{id}/revisions`	Revision count and latest revision

Audit export

Event family	Forge projection
AI request/response	Session interaction receipt
MCP tool call/result	Tool activity with server and tool route
Data access	Resource-access evidence
Session lifecycle	Session correlation and timing
Policy decision	Provider-native control event with policy references

Audit delivery accepts JSONL. Forge preserves source identifiers when present; events without a session, trace, or request ID receive a low-confidence fallback correlation key rather than a fabricated exact session.

Connection

Field	Description
Base URL	Reachable HTTPS Barndoor Platform API
Organization ID	Optional stable tenant scope
API token	Write-only credential stored by Forge
Audit delivery	Barndoor JSONL export delivered to the Forge importer

Open Settings → Integrations → Barndoor, enter the base URL, organization ID, and API token, then test the required inventory endpoints.
Run a sync and compare agent, MCP server, tool, policy, and revision counts with Barndoor.
If activity evidence is required, configure Barndoor to deliver its audit JSONL export to Forge and verify a known native request or tool-call ID.

Content visibility

Each audit receipt records prompt, response, tool-argument, and tool-result visibility independently. Raw provider fields are redacted before persistence, and absent content remains metadata-only.

Boundaries

The Platform API does not place Forge in Barndoor’s request path. Imported policy outcomes are Barndoor-native evidence; inline Forge policy enforcement is unavailable in this integration scope.