Skip to main content

​
Public integration endpoint

SIA’s supported public agent integration uses MCP over remote HTTP and per-client OAuth. Use an MCP client/SDK for initialization, discovery and tool calls. The generated tool reference documents input contracts, permissions and currently declared response schemas. The reference is not an OpenAPI document. Do not treat internal Firebase function URLs, Studio browser requests or administrative routes as a supported public REST API. No general API-key or service-account integration is offered by this guide.

​
Discover the live contract

After authorization, initialize the MCP session and read its tool catalog with the client’s standard discovery. Runtime feature configuration, granted permissions and current membership can affect available operations and successful calls. Documentation does not override the live contract. Successful tools may return structured content and text, with images/audio or bounded media reads where supported. Error responses and permission challenges are part of the protocol. A queued receipt establishes admission and a job identity, not completed media.

​
Compatibility boundaries

The shared server exposes workflow tools. Client adapters handle attachment bytes and native media rendering. Public platform policies and listing reviews remain host-specific. We do not switch catalogs based on a hidden reviewer identity or claim a scope upgrade is the same as a genuinely limited endpoint. Some Production response schemas currently declare only a versioned envelope and allow additional fields. The generated reference labels these as partial contracts; developers must inspect the live documented receipts rather than assume a complete typed response. For integration questions or a proposed stable API use case, contact SIA support.