Introduction

Bucky is the pre-development platform that turns an address into sourced site intelligence, project analysis, and decision-ready deliverables. Developers, design-builders, architects, and planning consultants use it to screen sites, read zoning and feasibility with citations, and carry a project from first look through entitlement. Homeowners and marketplace professionals work in the same product on a smaller scale.

These docs are organized around what you do, not who you are:

• Start a project — an address, the map, and Project Scout.
• Read the site — parcels, zoning, feasibility, and what's cited vs. unverified.
• Work with the team — who to add on a project, and when.
• Connect agents — the MCP server, the CLI, and the public OpenAPI document.

Where to startCopy Anchor Link

Browse by section in the sidebar, or use search (top right) to jump straight to a page.

For agents and integratorsCopy Anchor Link

Four machine-readable surfaces, each at a stable URL:

• Bucky MCP server — Streamable HTTP at https://buckybuild.com/api/mcp. Tools for feasibility, projects, geography, and the marketplace. See MCP, or read the server card before connecting.
• Bucky OpenAPI spec — /openapi.json, an OpenAPI 3.1 description of the curated public REST subset under /api/v1 (prepaid site check, coverage, usage, addresses) and /api/marketplace/v2. It is the machine-readable contract for that subset, not a generated per-endpoint HTTP reference. Every operation carries an operationId and a typed error schema, so it converts directly to LLM function-calling definitions.
• Bucky CLI — scripted access to the same product state, with an agent-safe profile. See CLI.
• Discovery — /.well-known/api-catalog (RFC 9727) indexes all of the above; /AGENTS.md and /llms.txt are the prose entry points, and /auth.md walks through obtaining credentials.

When to use these docsCopy Anchor Link

Reach for this site when you are building against Bucky: integrating the API or MCP server, scripting the CLI, or working out how authentication and scopes fit together.

For what Bucky is and who it is for, start at buckybuild.com/llms.txt. For whether a particular city is covered — coverage is onboarded jurisdiction by jurisdiction, and these docs do not enumerate it — see coverage. For a zoning or feasibility answer about a real address, call the API: the docs describe the interface, not the data.