How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Hugging Face Chat Completions API

OpenAI-compatible chat completion endpoints

Hugging Face Chat Completions API is one of 21 APIs that Hugging Face publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Chat Completions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, a getting-started guide, rate-limit docs, and pricing.

This API exposes 1 operation across 1 path, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 1.0.0.

Requests are made against a single base URL, https://router.huggingface.co.

1 operations 1 paths 5 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api-inference.huggingface.co
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

Hugging Face Chat Completions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HF Token) (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Hugging Face API token with Inference Providers permission. Generate from https://huggingface.co/settings/tokens

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Chat Completions 1

OpenAI-compatible chat completion endpoints

POST
/v1/chat/completions
Create Chat Completion
createChatCompletion body → 200400401404429502

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are ChatCompletionRequest (18 properties), ChatCompletionStreamResponse (7 properties), ChatCompletionResponse (7 properties), Usage (3 properties). Each schema is shown below with its type and property counts.

Error
object
1 property
ChatCompletionResponse
object
7 properties
Usage
object
3 properties
ChatCompletionRequest
object
18 properties 2 required
ChatCompletionStreamResponse
object
7 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

hugging-face-chat-completions-api-openapi.yml Raw ↑

Other APIs Hugging Face publishes across the network.

Hugging Face Audio API
Hugging Face Chat API
Hugging Face Computer Vision API
Hugging Face Data Access API
Hugging Face Dataset Info API
Hugging Face Datasets API
Hugging Face Embeddings API
Hugging Face Endpoints API
Hugging Face Files & Metadata API
Hugging Face Image Generation API
Hugging Face Info API
Hugging Face Models API
Where this information came from

This is an independent, third-party profile of Hugging Face Chat Completions API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.