CrossBeam’s supported programmatic interface is its read-only Model Context Protocol server. Eligible paying members can connect an AI client to completed plan-check results associated with their CrossBeam account. The public website also publishes machine-readable discovery files and negotiated Markdown for core informational pages.
CrossBeam does not currently publish a general-purpose REST API, public OpenAPI specification, or public webhook product. Those names are documented here so developers and agents can distinguish a missing resource from one that merely has an unusual URL.
CrossBeam MCP server
The CrossBeam MCP server exposes completed plan-check results through read-only tools. It uses Streamable HTTP and browser-based OAuth. Project access is scoped to the signed-in CrossBeam user or that user’s organization.
API documentation and OpenAPI specification
There is no supported public CrossBeam REST API or public OpenAPI specification at this time. Application and service endpoints used by the CrossBeam web product are private implementation details and are not a stable developer contract. Use the MCP server for supported external programmatic access.
Authentication documentation
MCP clients authenticate through OAuth in a browser using the same identity associated with the member’s CrossBeam account. Developers should not collect, embed, publish, or exchange CrossBeam credentials in prompts or configuration files. Connection-specific instructions are maintained on the MCP documentation page.
Webhooks
CrossBeam does not currently offer public developer webhooks. Municipal system integrations are configured as part of an agency deployment and are documented directly for the participating agency rather than exposed as a generic public interface.