SDK and Execution API

The /sdk page lays out an intended integration shape: register an agent, request policy-mediated execution for a tool call, receive a signed token, execute against the MCP, and get an audit trail — with tabs for a registration form, an execution-request form, TypeScript / Python / Java code samples for a @faburai/sdk package, and an API reference listing endpoints like POST /agents/register, POST /execution/request, and GET /audit/traces.

As implemented today, none of it is live. Registering an agent or requesting an execution token on this page reads from and writes to a fixed, in-browser mock dataset — five pre-defined sample agents and four pre-defined sample executions — rather than calling a real endpoint; the "token" returned is assembled client-side, not signed by anything. None of the endpoints the API Reference tab documents exist in the Data Plane's routing, and no @faburai/sdk package is published anywhere in this repository — the code samples show what an integration could look like, not something installable and runnable against a FaburAI tenant today.

/templates is a separate, static gallery of vendor connection templates (Salesforce Agentforce, Snowflake, AWS, SAP, and others), each with a description and a short list of configuration hints. It is disconnected from the real per-vendor templates used by the MCP Server Connection wizard: its endpoints are illustrative placeholders (e.g. sap.enterprise.com/api), and its "Use Template" button simply navigates back to the MCP Server Mesh page rather than pre-filling the connect form.