> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bedrock.cv/llms.txt
> Use this file to discover all available pages before exploring further.

# Introduction

> The Bedrock API for construction document management and analysis.

The Bedrock API provides programmatic access to a headless construction management platform. Upload drawings, extract structured data, compare revisions, and run computer vision analysis — all through a single REST API.

## Base URL

```
https://api.bedrock.cv
```

All endpoints are served over HTTPS. HTTP requests are rejected.

## Two APIs, One Platform

Bedrock exposes two complementary APIs:

| API                                    | Purpose                                                                                                                    |
| -------------------------------------- | -------------------------------------------------------------------------------------------------------------------------- |
| [CMS API](/cms-api/introduction)       | Manage projects, drawings, sheets, and files. Create overlays, track jobs, and organize your construction documents.       |
| [Vision API](/vision-api/introduction) | Run computer vision on drawings: detect symbols, generate revision overlays, analyze changes. Synchronous search and Q\&A. |

Both APIs share the same base URL, [authentication](/api-reference/authentication), and [error format](/api-reference/errors).

## Request Format

All request bodies use JSON. Set the `Content-Type` header accordingly:

```bash theme={null}
curl -X POST https://api.bedrock.cv/projects \
  -H "Authorization: Bearer sk_xxx" \
  -H "Content-Type: application/json" \
  -d '{"name": "Tower Block A"}'
```

## Response Format

All responses return JSON. Successful responses return `2xx` status codes. Errors return `4xx` or `5xx` with a [Problem Details](/api-reference/errors) body.

## Pagination

List endpoints return cursor-based paginated results. See [Pagination](/api-reference/pagination) for details.

## Filtering

List endpoints accept query parameters to filter by status, type, date range, and related resources. See [Filtering](/api-reference/filtering) for details.

## Expanding Responses

Include related objects inline to avoid N+1 requests. See [Expanding](/api-reference/expanding) for details.

## Idempotency

Safely retry `POST` requests without creating duplicates. See [Idempotency](/api-reference/idempotency) for details.

## SDKs

Official SDKs are coming soon. In the meantime, use any HTTP client — the API is a standard REST interface.