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

LangChain usage-limits API

The usage-limits API from LangChain — 3 operation(s) for usage-limits.

LangChain usage-limits API is one of 66 APIs that LangChain publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include usage-limits. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and authentication docs.

This API exposes 4 operations across 3 paths, and defines 5 schemas. It is described by OpenAPI 3.1.0, at version 0.1.0.

Requests are made against a single base URL, /.

4 operations 3 paths 5 schemas 1 DELETE2 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
0.1.0
Base URL
https://api.smith.langchain.com
Authentication
API Key, API Key, HTTP Bearer, API Key
Resource Areas
1

Authentication & Security 4

LangChain usage-limits 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 3 paths, the API surfaces 4 operations — 1 DELETE, 2 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

usage-limits 4
GET
/api/v1/usage-limits
List Usage Limits
list_usage_limits_api_v1_usage_limits_get → 200
PUT
/api/v1/usage-limits
Upsert Usage Limit
upsert_usage_limit_api_v1_usage_limits_put body → 200422
GET
/api/v1/usage-limits/org
List Org Usage Limits
list_org_usage_limits_api_v1_usage_limits_org_get → 200
DELETE
/api/v1/usage-limits/{usage_limit_id}
Delete Usage Limit
delete_usage_limit_api_v1_usage_limits__usage_limit_id__delete 1 param → 200422

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are UsageLimit (6 properties), ValidationError (3 properties), UpsertUsageLimit (3 properties), HTTPValidationError (1 property). Each schema is shown below with its type and property counts.

UpsertUsageLimit
object
Request body for creating or updating a usage limit.
3 properties 2 required
ValidationError
object
3 properties 3 required
UsageLimit
object
Usage limit model.
6 properties 5 required
UsageLimitType
string
Type of usage limit.
HTTPValidationError
object
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

langchain-usage-limits-api-openapi.yml Raw ↑

Other APIs LangChain publishes across the network.

LangChain access_policies API
LangChain ace API
LangChain alert_rules API
LangChain annotation-queues API
LangChain api-key API
LangChain audit-logs API
LangChain auth API
LangChain aws_marketplace API
LangChain backfills API
LangChain beacon API
LangChain bulk-exports API
LangChain charts API
Where this information came from

This is an independent, third-party profile of LangChain usage-limits 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.