Add Praesidia: AI agent and MCP governance

[msoica]

Adds Praesidia as an agent-native hosted service in API Orchestration. Registered agent/MCP identities, connection-level tool and argument permissions, approvals, and decision evidence govern calls routed through Praesidia. The listing describes its ongoing free Developer tier and vendor-scoped paid plans.

Public client source is distinguished from the proprietary hosted core: the TypeScript SDK is Apache-2.0 and the Python SDK is MIT, with separate repository and licence evidence. Public source does not establish npm/PyPI publication; version-matched packages are obtained through the vendor. MCP content guardrails are scoped to tool calls made during an agent chat turn. Agent-to-agent intent rules exclude MCP calls, and signed-by-default decision records are distinguished from separate unsigned argument/result logs.

Ten first-party evidence sources were checked on 18 October 2026. This is a documentation-reviewed submission; no hands-on enforcement testing or independent endorsement is claimed. Submitter attribution remains msoica in tool-submitters.json; no reviewer or publication provenance is added.

Validation: npm run validate:content -- --require-submitters passes for 16 categories, 58 tools, and 1 redirect/retirement; git diff --check passes. The existing test suite passes 89/90 locally: one enrichment-preflight test needs GNU Bash mapfile, unavailable in the host's macOS Bash 3.2. Only tools/praesidia.md changes in this update.

[foo-bender]

Outcome: changes-requested

Policy assessment

@msoica, registered-agent identities, per-connection MCP permissions, mediated runtime decisions and call evidence support agent-native inclusion in API Orchestration. Required frontmatter, taxonomy, freemium pricing and registered/routed-only scope pass inspection. No duplicate was found in the published catalogue or another open PR.

A material source-availability conflict blocks acceptance: tools/praesidia.md's limitationsMd and pricing evidence claim say client SDK repositories are not public, but https://github.com/praesidia-ai/sdk contains public TypeScript implementation under Apache-2.0 and https://github.com/praesidia-ai/sdk-python contains public Python implementation under MIT. Correct that clause and the matching PR-body assertion; add scoped repository/licence evidence. Distinguish public client source, proprietary hosted core and vendor-provided release packages. Public source does not establish npm/PyPI publication or open-source backend availability.

For channel precision, qualify MCP content guardrails as the documented agent chat-turn path, not every direct API call. Agent-to-agent intent rules do not cover MCP calls; signed decision records are distinct from unsigned argument/result logs. Preserve the existing registered/routed-only boundary.

Evidence checked

Individually checked all five exact submitted URLs:

• https://praesidia.ai/mcp — registered-server identity, connection permissions, drift review and mediated-call records.
• https://praesidia.ai/platform — registered-agent governance and runtime/evidence features.
• https://praesidia.ai/docs — MCP, REST and TypeScript/Python runtime setup/interfaces.
• https://praesidia.ai/pricing — free/paid plans and proprietary core; private-client-source wording conflicts with official repositories.
• https://praesidia.ai/press — operator/product identity and registered/routed scope.

Four items validate; the fourth needs correction below. The independent pass compared website, guardrails/connections/installation/proof documentation, public repository README/implementation/LICENSE/package metadata, release/tag/registry surfaces, pricing and legal/security pages. Observe/enforce and plan gates were distinguished. No authenticated operation, SDK runtime or independent security test was performed.

Evidence requiring correction or removal

• https://praesidia.ai/pricing — its plan/core statements are supported, but its FAQ and the submitted private-client-source subclaim conflict with current public first-party SDK implementations/licences. Amend or split that subclaim and substantiate the corrected distinction using the repositories; do not infer hosted-core licensing from client licences.

Please correct or remove each evidence item above.

Checks run

Exact head 76d3b51 merged with policy main b975226 in an isolated clone:

• npm run validate:content: passed (16 categories, 58 tools, 1 redirect/retirement).
• npm test: passed 90/90, Node v26.7.0 and GNU Bash 5.3.20.
• git diff --check: passed. Existing enrichment check: successful.

SEO evaluation and a reviewer metadata commit were withheld. No branch edit, approval, merge or deployment was performed.