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

Langbase Memory API

The Memory API from Langbase — 5 operation(s) for memory.

Langbase Memory API is one of 8 APIs that Langbase publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Memory. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, and an API reference.

This API exposes 7 operations across 5 paths, and defines 6 schemas. It is described by OpenAPI 3.0.3, at version 1.0.

Requests are made against a single base URL, https://api.langbase.com.

7 operations 5 paths 6 schemas 2 DELETE2 GET3 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.3
API Version
1.0
Base URL
https://api.langbase.com/v1
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Langbase Memory API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (apiKey) (api_key). By default, every request must be authenticated.

Paths & Operations 7

Across 5 paths, the API surfaces 7 operations — 2 DELETE, 2 GET, 3 POST. Each is listed below with its method, path, parameters, and response codes.

Memory 7
GET
/v1/memory
List memory stores.
listMemories → 200
POST
/v1/memory
Create a memory store.
createMemory body → 200
DELETE
/v1/memory/{name}
Delete a memory store.
deleteMemory 1 param → 200
POST
/v1/memory/retrieve
Retrieve similar chunks (RAG).
retrieveMemory body → 200
GET
/v1/memory/{name}/documents
List documents in a memory store.
listDocuments 1 param → 200
POST
/v1/memory/{name}/documents
Upload a document to a memory store.
uploadDocument 1 param body → 200
DELETE
/v1/memory/{name}/documents/{documentName}
Delete a document from a memory store.
deleteDocument 2 params → 200

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are RetrieveMemoryRequest (4 properties), Memory (3 properties), Document (3 properties), CreateMemoryRequest (3 properties). Each schema is shown below with its type and property counts.

RetrieveMemoryRequest
object
4 properties 2 required
RetrievedChunk
object
3 properties
CreateMemoryRequest
object
3 properties 1 required
Document
object
3 properties
Memory
object
3 properties
DeleteResponse
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

langbase-memory-api-openapi.yml Raw ↑

Other APIs Langbase publishes across the network.

Langbase Agent API
Langbase Chunker API
Langbase Embed API
Langbase Parser API
Langbase Pipes API
Langbase Threads API
Langbase Tools API
Where this information came from

This is an independent, third-party profile of Langbase Memory 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.