Skip to main content
POST
Count Anthropic message tokens

Authorizations

Authorization
string
header
required

A project-scoped Aixy API key. Create keys in the dashboard and send the secret as a Bearer token.

Headers

X-Request-ID
string

Optional caller-generated request identifier for end-to-end tracing.

Maximum string length: 255
X-Aixy-Client
string

Optional application[/version] for Activity attribution. Overrides User-Agent detection. Use a product name, not personal data or credentials. Names are 1-64 ASCII letters, digits, spaces, dots, underscores or hyphens, starting with a letter or digit. Optional versions start with a digit and use up to 32 letters, digits, dots, underscores, plus signs or hyphens. Invalid values are ignored. This self-declared label grants no permissions and is not forwarded.

Maximum string length: 97
Example:

"Acme Support/1.2.3"

X-Aixy-Session
string

Optional opaque session identifier for virtual routes with session affinity. Scoped to the authenticated caller and alias; never forwarded or recorded. Send full conversation history. Invalid values return 400 when affinity is enabled. Omission retains the route's normal strategy.

Required string length: 1 - 128
Pattern: ^[A-Za-z0-9._:-]+$
Example:

"conversation-82"

X-Aixy-Session-ID
string

Optional opaque conversation identifier recorded in Activity metadata. Reuse it for every call in a conversation. Sessions are isolated by organization, project, user and API key. Use no personal data or secrets. Invalid values are ignored. The header is not forwarded, grants no permissions and does not change routing affinity.

Required string length: 1 - 128
Pattern: ^[A-Za-z0-9._:-]+$
Example:

"conversation-82"

anthropic-version
string
required

Anthropic client contract version; forwarded unchanged on native requests. Reviewed Bedrock InvokeModel routes use the required upstream envelope version.

Example:

"2023-06-01"

anthropic-beta
string

Comma-separated Anthropic beta features, forwarded on matching native requests. Reviewed destination compatibility rules may omit unused beta announcements; unsupported features in use fail explicitly. Repeated headers are additive. Preserved Bedrock InvokeModel routes carry beta features in the upstream envelope. Translated routes reject unsupported beta features.

Body

application/json
model
string
required

Provider-qualified Anthropic model identifier.

Example:

"anthropic/claude-sonnet-4-5"

messages
object[]
required
system
tools
object[]

Response

Successful Anthropic response.

input_tokens
integer
required
Required range: x >= 0