Developers

Build agent integrations with Local Studio by Sybil Solutions. This portal describes the public, read-only product metadata API hosted on this site and points to the separate controller API that runs on each Local Studio installation. Start with the machine-readable OpenAPI 3.1 specification or the MCP Streamable HTTP endpoint.

Quickstart and Sandbox

The public endpoints are a safe production sandbox. They require no account, API key, or write access. Responses are JSON and may be cached. Use them to test discovery, schema ingestion, function calling, health checks, and product lookup without creating user data.

curl -s https://localstudio.ai/api/v1/status
curl -s https://localstudio.ai/api/v1/products
curl -s https://localstudio.ai/openapi.json

Authentication

No authentication is required for this site's public metadata API. Local Studio's controller is different: it binds to 127.0.0.1:8080 by default. A non-loopback controller requires LOCAL_STUDIO_API_KEY. Keep controller keys out of prompts, URLs, source control, and logs.

Errors and Limits

API errors use JSON with a stable error code, a human-readable message, a resolution hint, and a documentation link. The public metadata surface is intentionally small and read-only. Use normal conditional requests and avoid repeated polling. No webhooks are offered by this marketing site.

Agent Protocols

Function-calling clients should derive tools from OpenAPI. MCP clients can initialize at /.well-known/mcp, list tools, and call the read-only product catalog tool. Agents should also read llms.txt, agents.md, and the API catalog.