Chat completions (ZeroClick)
OpenAI-style chat inference authenticated by a ZeroClick HMAC signature instead of an API key.
/v1/chat/completions — only authentication, authorization, and metering differ.
- Authentication — no
x-api-key. A buying agent calls ZeroClick’s hosted pay URL; ZeroClick proxies the request and signs the raw request bytes with an HMAC in thezc-signatureheader. A request is authenticated only by a valid signature. - Authorization — a ZeroClick allowance check runs before any billable work. It fails open on a transient ZeroClick outage (the signature has already verified), but never for a missing or invalid signature.
- Metering — actual token usage is settled with ZeroClick and reported via the
zc-usageresponse header. Stripe metering is bypassed; ZeroClick is the sole biller.
Authorizations
HMAC signature minted by ZeroClick over the raw request bytes, of the
form t=<unix-seconds>,kid=<key-id>,v1=<hex-hmac>. Verified by the
@zeroclickai/sellers SDK against the seller's signing secret keyed by
kid. A missing or invalid signature is rejected with 401
invalid_zeroclick_signature; this is never failed open.
Headers
ZeroClick request id, echoed in logs for correlation. Set by ZeroClick when it proxies the request.
"zcreq_1"
Identifier of the buying agent. Used to partition logs/analytics by agent; becomes the synthesized caller identity.
"agt_1"
Body
Model id; routes the request via model metadata. Kebab-cased into a ZeroClick service slug for metering.
"LFM2.5-1.2B-Instruct"
1Candidate labels for text-classification models. May also be supplied via a system-role message.
Forwarded to the IAB cloud inference API only when the resolved model supports it.
Task-specific options. For GLiNER models this carries usecase,
schema, labels, threshold, mask, and replacement_char. For
moderation, threshold; for signal-extract, max_keywords.
Response
OpenAI Chat Completions response. Includes the zc-usage header settling actual usage with ZeroClick.

