# TileDB

> TileDB, Inc. builds a multimodal database around one universal data model — the multi-dimensional
> array — that stores tables, population genomics (VCF), single-cell (SOMA), biomedical imaging, vector
> embeddings, point clouds, files and ML models in a single cloud-native format on S3, Azure Blob, GCS,
> Lustre or MinIO. The open-source TileDB Embedded engine is paired with TileDB Cloud, a hosted and
> self-hostable platform for cataloging, sharing, governing and querying those assets with serverless
> SQL, user-defined functions, task graphs, notebooks and dashboards.

Generated by API Evangelist on 2026-08-30. This is a third-party profile, not a TileDB document.
TileDB serves no llms.txt of its own: https://docs.tiledb.com/llms.txt 302s to the cloud console SPA,
https://documentation.cloud.tiledb.com/llms.txt returns a 470-byte JavaScript redirect stub, and
https://tiledb.com/llms.txt and https://www.tiledb.com/llms.txt both 404 (all probed 2026-08-30).

## API

- [TileDB Storage Platform API v1](https://api.tiledb.com/v1): 168 operations across arrays, groups,
  assets, files, notebooks, UDFs, task graphs, serverless SQL, queries, users, organizations,
  invitations, favorites and tokens. Swagger 2.0, basePath /v1.
- [TileDB Storage Platform API v2](https://api.tiledb.com/v2): 21 operations, mostly groups and assets.
  Swagger 2.0, basePath /v2. Coexists with v1 rather than replacing it.
- [OpenAPI contracts](https://github.com/TileDB-Inc/TileDB-Cloud-API-Spec): TileDB publishes both
  contracts openly — openapi-v1.yaml and openapi-v2.yaml.
- [API reference](https://documentation.cloud.tiledb.com/academy/api-reference/): index of the REST API
  and every client library, with TileDB's own currency flags on each.

## Authentication

- [REST API tokens](https://documentation.cloud.tiledb.com/academy/accounts/individual/profile/api-tokens/):
  send the token in the `X-TILEDB-REST-API-KEY` header. Tokens are created in the console under
  Profile > API tokens, or with POST /v1/token. Expiry defaults to 30 minutes if none is set; scope
  defaults to all permissions (`*`).
- HTTP Basic is also accepted. An OAuth 2.0 authorization-code flow is declared in the contract, but it
  is commented out of the global security requirement and its declared host `oauth2.tiledb.com` does not
  resolve in public DNS.
- Inside a TileDB Cloud notebook a temporary token is injected as `$TILEDB_REST_TOKEN`; client libraries
  read it via the `rest.token` config key.

## Conventions an agent needs

- Assets are addressed as `{namespace}/{name}`, where the namespace is a user or an organization. The
  canonical client-side URI form is `tiledb://{namespace}/{name}`.
- Errors are `application/json` with `{code, message, request_id}`. NOT RFC 9457 problem details.
  Quote `request_id` in support requests.
- Listing endpoints paginate with `page` and `per_page` and return a `pagination_metadata` object.
- Content negotiation matters: the high-throughput array paths speak `application/capnp` (Cap'n Proto)
  as well as JSON, and some operations exist in both forms. Prefer the `*Json` operationIds
  (`submitQueryJson`, `getArrayMetaDataJson`, `getArrayNonEmptyDomainJson`) if you only speak JSON.
- No idempotency keys are published. No rate limits, no 429, no Retry-After, no RateLimit headers.
- No dry-run mode. `getEstResultSizes` and `getArrayMaxBufferSizes` let you size a query before running it.
- Reversal paths exist (`stopTaskGraphExecution`, `deregisterArray`, `revokeToken`, the `cancel*`
  invitation operations) but TileDB states no window for any of them. `deleteArray`, `deleteGroup`,
  `vacuumArray` and `consolidateArray` are not reversible.

## Client libraries

- Python: [tiledb](https://pypi.org/project/tiledb/) (engine), [tiledb-cloud](https://pypi.org/project/tiledb-cloud/) (REST client), [tiledbsoma](https://pypi.org/project/tiledbsoma/), [tiledb-vector-search](https://pypi.org/project/tiledb-vector-search/), [tiledb-bioimg](https://pypi.org/project/tiledb-bioimg/), [tiledb-ml](https://pypi.org/project/tiledb-ml/)
- R: [tiledb on CRAN](https://cran.r-project.org/package=tiledb), tiledbcloud on TileDB's r-universe
- Java: [io.tiledb:tiledb-java](https://central.sonatype.com/artifact/io.tiledb/tiledb-java), [io.tiledb:tiledb-cloud-java](https://central.sonatype.com/artifact/io.tiledb/tiledb-cloud-java)
- Go: [github.com/TileDB-Inc/TileDB-Go](https://pkg.go.dev/github.com/TileDB-Inc/TileDB-Go)
- C#: [TileDB.CSharp](https://www.nuget.org/packages/TileDB.CSharp/)
- JavaScript: [@tiledb-inc/tiledb-cloud](https://www.npmjs.com/package/@tiledb-inc/tiledb-cloud) — last
  published 2023-09-06, roughly two years behind the contract it wraps.
- TileDB's own API reference marks the Java, C#, Go, Rust, R and JavaScript clients as "out of date,
  incomplete, or under active development".

## Domain standards

- [SOMA](https://github.com/single-cell-data/SOMA) for single-cell, implemented as `tiledbsoma`.
- VCF/BCF ingestion and export via TileDB-VCF and the `tiledbvcf` CLI.
- OME-TIFF, OME-Zarr and OpenSlide whole-slide formats via TileDB-BioImaging.
- CF metadata conventions for climate/forecast data via TileDB-CF-Py.
- SCIM 2.0 provisioning and OpenID Connect SSO for self-hosted deployments (Okta, Microsoft Entra).

## Docs

- [Academy home](https://documentation.cloud.tiledb.com/academy/home/)
- [Get started](https://documentation.cloud.tiledb.com/academy/get-started/)
- [Arrays](https://documentation.cloud.tiledb.com/academy/structure/arrays/)
- [Single cell (SOMA)](https://documentation.cloud.tiledb.com/academy/structure/life-sciences/single-cell/)
- [Population genomics (VCF)](https://documentation.cloud.tiledb.com/academy/structure/life-sciences/population-genomics/)
- [Biomedical imaging](https://documentation.cloud.tiledb.com/academy/structure/life-sciences/biomedical-imaging/)
- [Vector search](https://documentation.cloud.tiledb.com/academy/structure/ai-ml/vector-search/)
- [Tables and serverless SQL](https://documentation.cloud.tiledb.com/academy/structure/tables/)
- [Access control](https://documentation.cloud.tiledb.com/academy/collaborate/access-control/)
- [Self-hosting](https://documentation.cloud.tiledb.com/academy/self-hosting/)

## Company

- [Website](https://www.tiledb.com/)
- [Pricing](https://www.tiledb.com/pricing) — sold as components: user seats ($10/seat/month, 10-seat
  increments), vCPUs ($50/vCPU/month, 50-vCPU increments), and a Dedicated Success Engineer
  ($250/hour, 100-hour increments), all billed annually. No self-serve paid plan.
- [Free tier](https://documentation.cloud.tiledb.com/academy/accounts/individual/apply-for-free-tier/) —
  $100 of credits for 6 months, individual accounts only, reviewed by TileDB.
- [Blog](https://www.tiledb.com/blog) · [Forum](https://forum.tiledb.com/) · [GitHub](https://github.com/TileDB-Inc)
- [Terms of Use](https://www.tiledb.com/terms-of-use) · [Privacy Policy](https://www.tiledb.com/privacy-policy)

## Known gaps (probed 2026-08-30)

- No MCP server, no A2A agent card, no /.well-known/ documents on any TileDB host.
- No status page (status.tiledb.com does not resolve), no published SLA, no deprecation policy.
- No trust center and no published SOC 2 / ISO 27001 / HIPAA certification page.
- No dated changelog for the REST API. The engine publishes GitHub Releases; the contract repository
  publishes none and was last committed 2025-08-04.