Bem File System API
Unix-shell-style nav over parsed documents and the cross-doc memory store.`POST /v3/fs` is a single op-driven endpoint designed for LLM agentsand programmatic consumers that want to walk a corpus the way they'dwalk a filesystem.## Doc-level ops (every parsed document)- `ls` — list parsed documents with rich per-doc metadata.- `cat` — read one doc's parse JSON, sliced (`range`) or projected (`select`).- `head` — first N sections of one doc.- `grep` — substring or regex search; `scope`, `path`, `countOnly` available.- `stat` — metadata only (page/section/entity counts, timestamps).## Memory-level ops (require `linkAcrossDocuments: true` on the parse function)- `find` — list canonical entities across the corpus.- `open` — entity + mentions.- `xref` — for one entity, sections across docs that mention it (with content).Memory ops return an empty list with a `hint` when no docs in thisenvironment have been memory-linked.## PaginationList ops paginate by cursor — pass the previous response's `nextCursor`back as `cursor`; `hasMore: false` signals the last page. Same idiom as`/v3/calls` and `/v3/outputs`.
Bem File System API is one of 22 APIs that Bem publishes on the APIs.io network, described by a machine-readable OpenAPI specification.
Tagged areas include Filesystem. The published artifact set on APIs.io includes an OpenAPI specification.
This API exposes 1 operation across 1 path, and defines 6 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against 2 base URLs: https://api.bem.ai, https://api.eu1.bem.ai.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Bem File System API declares
1 security scheme
for authenticating requests.
An API key is passed in the header as x-api-key (API Key).
By default, every request must be authenticated.
API Key— Authenticate using API Key in request header
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.
Unix-shell-style nav over parsed documents and the cross-doc memory store. POST /v3/fs is a single op-driven endpoint designed for LLM agents and programmatic consumers that want…
Schemas 6
The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are FSRequest (14 properties), FSResponse (6 properties), FSFilter (4 properties), FSRange (3 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 Bem 12
Other APIs Bem publishes across the network.
This is an independent, third-party profile of Bem File System 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.