DEVELOPER RESOURCES

MIAMI WEB AI for agents and developers.

Read current services, pricing, and agent guidance through the public REST API or remote MCP server. Those remote interfaces are read-only. A separate experimental Site-tool layer exists only in a visitor's current browser tab and can prepare an Application for visible review.

REST API

Structured studio information.

No authentication is required for these read-only endpoints. Every operation has a unique operation ID, typed responses, and structured JSON errors in the OpenAPI specification.

Every response allows any origin (CORS *), caches publicly, and carries a strong ETag; send If-None-Match to skip an unchanged body. Every JSON payload includes meta.dataVersion (2026-08-27), the date the published data last changed, and it matches across the pages, the API, MCP, and llms.txt.

GET /api/studio
Read one studio information section.
GET /api/studio/services
List services and published entry prices.
GET /api/studio/pricing
Read Scope, Build, and Operate pricing.
GET /api/studio/agent-guide
Read when-to-use and handoff guidance.

MACHINE-READABLE

Predictable public files.

OpenAPI specification/openapi.json
Typed REST operations and response schemas.
MCP server/mcp
Streamable HTTP endpoint for MCP clients.
MCP manifest/.well-known/mcp.json
Remote-server metadata in the official server.json format.
Site-tool inventory/site-tools.json
Browser-scoped WebMCP tools, schemas, annotations, and deployment availability.
Agent instructions/llms.txt
Use cases, boundaries, and canonical links.
Markdown guide/developers.md
This documentation as plain Markdown.

WHEN TO USE THIS

Use the interface that fits the job.

REST

Use it for a direct read from an app, script, or function call.

MCP

Use it when an MCP client needs a native tool and readable resources.

https://miamiweb.ai/mcp

This stateless Streamable HTTP endpoint accepts one JSON-RPC message per POST and supports automatic negotiation across these protocol revisions: 2026-07-28, 2025-11-25, 2025-06-18, 2025-03-26.

Modern lifecycle (preferred)

Use 2026-07-28. Start with server/discover, with no initialize. Each request carries its revision in params._meta, plus matching MCP-Protocol-Version and Mcp-Method headers. Mcp-Name is also required for tool calls and resource reads. Cacheable results carry public five-minute cache hints.

Legacy lifecycle

2025-11-25 clients still send initialize at this same URL. The 2025-06-18 and 2025-03-26 revisions remain available for existing clients.

Check either path with the MCP Inspector:

npx @modelcontextprotocol/inspector --cli https://miamiweb.ai/mcp --transport http --method tools/list

Application

Send a person to /apply when they are ready to start a free Scope.

Browser Site tools

Supported WebMCP browsers discover these tools throughdocument.modelContextonly while this origin owns the current tab. Unsupported browsers keep the complete human site.

get_studio_information
navigate_site
prepare_application
submit_application

Preparation writes only a current-tab draft. Submission needs visible visitor approval, a signed 15-minute authority token, and the server-controlled rollout switch. The first production deployment keeps submission disabled while read, navigation, and preparation are verified.