The messages endpoint implements the Anthropic Messages API format, letting you use the official Anthropic SDK with Darkbloom by pointing it atDocumentation Index
Fetch the complete documentation index at: https://docs.darkbloom.dev/llms.txt
Use this file to discover all available pages before exploring further.
https://api.darkbloom.dev. The request and response shapes follow the Anthropic API specification; the coordinator routes the request through the same provider dispatch and attestation pipeline as all other inference endpoints.
Authentication
All inference endpoints require a Bearer token:api_key argument alongside the custom base_url.
Request
The conversation as an array of message objects. Each object must have:
role—"user"or"assistant"content— the message text (string)
Maximum number of tokens to generate. Required in Anthropic format.
An optional system prompt that sets context or persona for the assistant.
Response
The response follows the Anthropic response shape with acontent array.
Unique identifier for the request.
Always
"message".Always
"assistant".Array of content blocks. Text responses contain a single block with
type: "text".Why generation stopped.
"end_turn" for natural completion; "max_tokens" if the token limit was reached.