Jentic publishes the only available OpenAPI specification for Anthropic API, keeping it validated and agent-ready. Send messages to Claude models with up to 200K token context windows for complex reasoning, analysis, and code generation across 11 endpoints. Supports message batching for high-volume async workloads, token counting for cost estimation, and model listing for version discovery. Authentication uses the x-api-key header with API key validation.
11 endpointsSend prompts to Anthropic's Claude models for text generation, reasoning, and code tasks through the Messages API. Two endpoints cover the core flow: POST /messages for synchronous chat completions with system prompts, tool use, and large-context inputs, and POST /messages/count_tokens for cost-aware token estimation before a request is dispatched. Anthropic's documentation accepts either an API key in the X-API-Key header or an Authorization bearer token, and every call also carries a required anthropic-version header plus an optional anthropic-beta header for opting into preview features. Suited to agent workflows that need long-context reasoning, structured tool calls, or precise cost control.
2 endpointsStep 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.