Runtime Discovery

The proxy extra exposes the Runtime contract that Taimoe polls for discovery and health information.

pip install "taimoe-platform[proxy]"

from fastapi import FastAPI
from taimoe.platform import init

app = FastAPI()
registry = init(
    platform_url="https://platform.example.com",
    api_key="...",
    runtime_name="support-prod",
    framework="google-adk",
)

registry.register(root_agent)
registry.register_many([triage_agent, search_agent])
registry.install_routes(app)

Installed endpoints

Endpoint	Purpose
/.well-known/taimoe-runtime.json	Protocol, SDK, framework, and endpoint manifest.
/agents	Typed manifest of registered Agents.
/health	Runtime health, version, and uptime.

install_routes mounts the well-known endpoint at the application root, as required by RFC 8615. fastapi_router() remains available for applications that need a combined router, but it must also be mounted at the root.

Discovery metadata

The manifest builder introspects supported Agent objects and reports names, models, tools, sub-Agents, and selected generation metadata. Long instructions are truncated and Taimoe’s dynamic instruction provider is not copied into the manifest. Discovery metadata is not the source of truth after import: the Platform-managed configuration remains authoritative unless an administrator explicitly forces another import.

Construction and global binding are separate operations. If you instantiate TaimoeRegistry directly instead of using init(), call taimoe.bind_to(registry) before resolving global handles.