# Bucky Docs

> Documentation for the Bucky platform, API, and MCP tools.

## When to use these docs

- You are integrating with the Bucky REST API (`/api/v1`) or the Bucky MCP server (`/api/mcp`).
- You need authentication mechanics: OAuth flow, scopes, agent registration, bearer fallback.
- You are scripting Bucky with the Bucky CLI.
- You need the machine-readable contract: https://buckybuild.com/openapi.json

## When not to use these docs

- For what Bucky is and who it is for, start at https://buckybuild.com/llms.txt.
- For whether a specific city is covered, see https://buckybuild.com/en/coverage.md — coverage is per-jurisdiction and these docs do not enumerate it.
- For zoning or feasibility answers about a real address, call the API; the docs describe the interface, not the data.

## Company and legal

- [About Bucky](https://buckybuild.com/en/about-us.md)
- [Contact and support](https://buckybuild.com/en/support)
- [Privacy](https://buckybuild.com/en/privacy)
- [Terms](https://buckybuild.com/en/terms)
- [Security contact](https://buckybuild.com/.well-known/security.txt)

## api

- [API](https://docs.buckybuild.com/docs/api.md): Prepaid public REST — POST|GET /api/v1/sites/check is the priced unit. Coverage and usage are free. Keys are bk_live_. CORS stays off.

## cli

- [CLI](https://docs.buckybuild.com/docs/cli.md): Use Bucky from the command line — installation, authentication, and common commands.

## getting-started

- [Introduction](https://docs.buckybuild.com/docs.md): Bucky turns an address into sourced site intelligence, feasibility, and a decision you can defend.
- [Getting Started](https://docs.buckybuild.com/docs/getting-started.md): Start here — what Bucky is, the concepts that matter first, and how to get to your first result.
- [Core concepts](https://docs.buckybuild.com/docs/getting-started/core-concepts.md): The handful of concepts — pre-development, site intelligence, projects, parcels, zoning, feasibility, deliverables, and people — that show up across every part of Bucky.
- [Developer quickstart](https://docs.buckybuild.com/docs/getting-started/developer-quickstart.md): Load credit, mint a bk_live_ key, run one sourced site check, and read the usage receipt.
- [Quickstart](https://docs.buckybuild.com/docs/getting-started/quickstart.md): The shortest path to a first result in Bucky — one address, a cited read, and who sees it next.
- [What is Bucky?](https://docs.buckybuild.com/docs/getting-started/what-is-bucky.md): Bucky turns an address into sourced site intelligence, feasibility, and a decision you can defend — before you commit time, fees, or capital.

## guides

- [Guides](https://docs.buckybuild.com/docs/guides.md): Task-oriented walkthroughs for common Bucky workflows across the platform, API, and MCP.
- [How to read and export a feasibility report](https://docs.buckybuild.com/docs/guides/feasibility-report.md): Turn a project's cited analysis into an audience-ready deliverable — what's inside, how to pick an audience, and how to export it.
- [First week with your team](https://docs.buckybuild.com/docs/guides/first-week-with-your-team.md): The recommended first week in Bucky for a firm — one champion, one known address, then decide who sees the project.
- [End-to-end parcel analysis](https://docs.buckybuild.com/docs/guides/parcel-analysis.md): Walk one address from a map search through a cited zoning and feasibility read to a go/no-go — the full chain in one workflow.
- [Prompting BuckyAssist](https://docs.buckybuild.com/docs/guides/prompting-buckyassist.md): How to ask BuckyAssist for site exploration on the map, zoning answers, designs, project help, and more — with copy-paste example prompts.

## mcp

- [MCP](https://docs.buckybuild.com/docs/mcp.md): Connect AI agents to Bucky over the Model Context Protocol — setup, tools, and workflows.
- [Connect Bucky to your AI](https://docs.buckybuild.com/docs/mcp/connect.md): Add Bucky to Claude, Claude Code, Cursor, VS Code, Codex, ChatGPT, Grok, or the CLI.
- [MCP Integrations](https://docs.buckybuild.com/docs/mcp/integrations.md): Reach Bucky's MCP endpoint over Streamable HTTP and verify it locally.
- [MCP Tool Reference](https://docs.buckybuild.com/docs/mcp/reference.md): Generated reference for the Bucky tools exposed over the Model Context Protocol.
- [MCP Tools](https://docs.buckybuild.com/docs/mcp/tools.md): Understand the Bucky tool groups exposed through MCP.

## platform

- [Platform](https://docs.buckybuild.com/docs/platform.md): How Bucky models the world — projects, people, parcels, zoning, feasibility, and services — and how they connect in a typical workflow.
- [Feasibility](https://docs.buckybuild.com/docs/platform/feasibility.md): How to read a feasibility result in Bucky — what it's built from, what it does not replace, and where to go once a site looks viable.
- [Parcels](https://docs.buckybuild.com/docs/platform/parcels.md): How to read a parcel in Bucky — geometry, dimensions, and jurisdiction identifiers — and what to do when a field has no source on file.
- [People on a project](https://docs.buckybuild.com/docs/platform/people.md): Who belongs on a Bucky project — team, partners, stakeholders, and viewers — and when they join across the development.
- [Projects](https://docs.buckybuild.com/docs/platform/projects.md): A project is the container that ties a parcel, its analysis, site options, and the services you engage into one piece of planning work.
- [Services](https://docs.buckybuild.com/docs/platform/services.md): How to move from a viable project to the people who build it — services are a later-stage step, not the reason a project starts.
- [Site exploration](https://docs.buckybuild.com/docs/platform/site-exploration.md): How Project Scout on the Projects map helps you explore blocks, compare site options, and decide what to study before you save a project.
- [Zoning](https://docs.buckybuild.com/docs/platform/zoning.md): How to read zoning in Bucky — what's cited from the bylaw, what's a cached default, and what to verify before you rely on it.

## resources

- [Resources](https://docs.buckybuild.com/docs/resources.md): Trust, support, and lifecycle pages — FAQ, architecture, security, and the changelog.
- [Citations and confidence](https://docs.buckybuild.com/docs/resources/citations.md): What "cited" actually means in Bucky — the status behind every fact, what an assumption is, and what to verify before you rely on a result.
- [Coverage](https://docs.buckybuild.com/docs/resources/coverage.md): What "covered" means for an address in Bucky, why coverage varies by jurisdiction, and how to check it before you trust a result.
- [FAQ](https://docs.buckybuild.com/docs/resources/faq.md): Common questions from firms evaluating Bucky — how it is used across the development, who gets added, coverage, liability, and how to roll it out.

## Discovery

- [Sitemap](https://docs.buckybuild.com/sitemap.md)
- [Full docs](https://docs.buckybuild.com/llms-full.txt)
- [Bucky OpenAPI spec](https://buckybuild.com/openapi.json)
- [Bucky API catalog](https://buckybuild.com/.well-known/api-catalog)
- [Bucky MCP server card](https://buckybuild.com/.well-known/mcp/server-card.json)
- [Bucky agent entrypoint](https://buckybuild.com/AGENTS.md)