API and technical reference
Use this directory when you need an exact interface, supported behavior or format detail. If you are still choosing a workflow, begin with Build and publish or Query and analyze.
Interfaces and behavior
| Reference | What it answers |
|---|---|
| CLI | Commands, arguments, defaults and output |
| SPARQL | Query syntax and evaluation support |
| Python, JavaScript, R, Rust | Client usage and result types |
| WASM bindings | Low-level browser engine interfaces |
| Compatibility | Reader/file compatibility and feature restrictions |
| Interoperability | Import/export formats and graph preservation |
| GeoSPARQL, SHACL, reasoning | Spatial functions, validation and inference |
| Federation | Combining files and remote endpoints |
| Writable graphs | Manifest and journal semantics |
| Dataset Card fields | Metadata schema, projections and maintenance contracts |
| Hosting | HTTP and browser hosting requirements |
| Media and SQL companions | Additional representations and assets |
How rete works
The format specification describes the bytes on disk. Repository and core explains the implementation, while semantic zoom explains the summaries used to explore a graph.
Large builds and tables covers data preparation and scale. Parallel browser execution describes the experimental threading paths and their requirements.
Evidence and development
Benchmarks explains how to run and interpret measurements; the measurement record retains the detailed results. SPARQL conformance records test coverage and limitations; neither is a promise about every workload.
For building and changing the project, start with Development and Tests, coverage and CI. Language packaging and releases live in Client development and the Release guide.