Developers

API & Agent
Documentation

Every public fact about Plateau Candy — services, work, capacity, booking — is available as a versioned REST API, an MCP server and plain Markdown. No key needed to read.

Start here01
OpenAPI 3.1
Machine-readable spec
16 operations, typed responses, RFC 9457 errors, versioning policy.
/api/openapi.json
MCP
Model Context Protocol
Five tools over Streamable HTTP — profile, services, availability, booking.
/api/mcp
Directory
All endpoints, one index
The signpost agents read first. Groups every machine-readable surface.
/api/directory
Endpoints — API v102
MethodPathPurpose
GET/api/v1/servicesService catalog as Schema.org OfferCatalog
GET/api/v1/workCase studies as Schema.org ItemList
GET/api/v1/search?q=…Search the portfolio by keyword, tag or client
GET/api/v1/capacity.jsonCurrent capacity and earliest start
POST/api/v1/negotiate.jsonFit check: send a project description, get score + next steps
POST/api/v1/briefingSubmit a structured project briefing
POST/api/v1/workflows/matching.jsonProblem analysis + capability match + contact, one call
GET/api/v1/feed.xmlAtom feed of new case studies and updates

All 16 operations with schemas and examples: openapi.json · Unversioned /api/* paths remain permanent aliases.

Authentication03

Reading is anonymous. Writing (webhooks, partner briefings) uses a Bearer token — request one by mail, revocation within one business day. Errors come back as RFC 9457 application/problem+json with a stable machine-readable code. Full guide: auth.md

Example04
# Does Plateau Candy fit my project?
curl -X POST https://www.plateaucandy.de/api/v1/negotiate.json \
  -H "Content-Type: application/json" \
  -d '{"query": "make our docs site usable for AI agents"}'
For AI agents05