LangChain fleet usage API
The fleet usage API from LangChain — 4 operation(s) for fleet usage.
LangChain fleet usage API is one of 66 APIs that LangChain publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include fleet usage. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.
This API exposes 4 operations across 4 paths, and defines 10 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.
Requests are made against a single base URL, /.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 4
LangChain fleet usage API declares
4 security schemes
for authenticating requests.
An API key is passed in the header as X-API-Key (API Key).
An API key is passed in the header as X-Tenant-Id (Tenant ID).
It accepts HTTP bearer tokens (Bearer Auth).
An API key is passed in the header as X-Organization-Id (Organization ID).
Bearer Auth— Bearer tokens are used to authenticate from the UI. Must also specify x-tenant-id or x-organization-id (for org scoped apis).
Paths & Operations 4
Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.
Schemas 10
The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are usage.AgentUsage (8 properties), usage.UserUsage (7 properties), usage.ToolUsage (5 properties), usage.ModelUsage (4 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from LangChain 12
Other APIs LangChain publishes across the network.
This is an independent, third-party profile of LangChain fleet usage 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.