# Databuddy API Context

Databuddy exposes a REST API at https://api.databuddy.cc, an OpenAPI spec at https://www.databuddy.cc/openapi.json, and an RFC 9727 API catalog at https://www.databuddy.cc/.well-known/api-catalog. Use API keys in `x-api-key` or `Authorization: Bearer`.

## Authentication

Read https://www.databuddy.cc/auth.md. Unauthenticated protected API probes return `WWW-Authenticate: Bearer resource_metadata="https://api.databuddy.cc/.well-known/oauth-protected-resource"`.

## Primary Endpoints

- `GET https://api.databuddy.cc/v1/query/websites`: list websites accessible to the key.
- `POST https://api.databuddy.cc/v1/query?website_id=...`: query analytics using typed query builders.
- `POST https://basket.databuddy.cc/track`: send server-side events with a scoped API key.
- `POST https://api.databuddy.cc/v1/mcp/`: use the Databuddy MCP server over Streamable HTTP.

## Agent Guidance

Use `read:data` for analytics. Ask for explicit confirmation before write tools such as feature flags, links, goals, funnels, and memory. Prefer date presets such as `last_7d` and `last_30d`.