bota.dev valid

Bota

Bota is a multi-tenant hardware + API platform for capturing, transcribing, and summarizing offline conversations via AI wearable devices. B2B2C model: your backend calls the Bota API; your end users wear the devices. Bota never has a direct relationship with end users.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-27T09:49:17.191Z. Cached copy · Source on bota.dev

# Bota

> Bota is a multi-tenant hardware + API platform for capturing, transcribing, and summarizing offline conversations via AI wearable devices. B2B2C model: your backend calls the Bota API; your end users wear the devices. Bota never has a direct relationship with end users.

## Get Started

- [Overview](https://docs.bota.dev): Platform overview, architecture, use cases (healthcare, sales, legal, enterprise)
- [Quickstart](https://docs.bota.dev/quickstart): Full walkthrough — create end user, register device, upload audio, get transcript
- [Core Concepts](https://docs.bota.dev/concepts): Entity model — Organization, Project, EndUser, Device, Recording, Transcription, Summary

## Authentication

- [Authentication](https://docs.bota.dev/authentication): API key types (sk_live_*, sk_test_*, rk_*, dtok_*, up_*), security practices, mobile vs server flows

## API Reference

- [API Introduction](https://docs.bota.dev/api-reference/introduction): Base URL, headers, response format, HTTP status codes
- [Pagination](https://docs.bota.dev/api-reference/pagination): Cursor-based pagination with limit and cursor params
- [Idempotency](https://docs.bota.dev/api-reference/idempotency): Safe retries using Idempotency-Key header
- [External IDs](https://docs.bota.dev/api-reference/external-ids): Mapping your user/device IDs to Bota resources via external_id
- [Test Mode](https://docs.bota.dev/api-reference/test-mode): sk_test_* keys, isolated data, no billing
- [Errors](https://docs.bota.dev/api-reference/errors): Error codes and handling strategies
- [Rate Limits](https://docs.bota.dev/api-reference/rate-limits): 100 req/s, 1000 req/min

## End Users

- [Create End User](https://docs.bota.dev/api-reference/end-users/create): POST /v1/end-users
- [List End Users](https://docs.bota.dev/api-reference/end-users/list): GET /v1/end-users
- [Get End User](https://docs.bota.dev/api-reference/end-users/get): GET /v1/end-users/:id
- [Delete End User](https://docs.bota.dev/api-reference/end-users/delete): DELETE /v1/end-users/:id — cascades to recordings, transcriptions, summaries

## Devices

- [Register Device](https://docs.bota.dev/api-reference/devices/create): POST /v1/devices with serial_number
- [Bind Device](https://docs.bota.dev/api-reference/devices/bind): POST /v1/devices/:id/bind — returns dtok_* for cellular devices
- [Unbind Device](https://docs.bota.dev/api-reference/devices/unbind): POST /v1/devices/:id/unbind — rotates device token
- [List Devices](https://docs.bota.dev/api-reference/devices/list): GET /v1/devices
- [Get Device](https://docs.bota.dev/api-reference/devices/get): GET /v1/devices/:id
- [Update Device](https://docs.bota.dev/api-reference/devices/update): PATCH /v1/devices/:id
- [Reset Device](https://docs.bota.dev/api-reference/devices/reset): POST /v1/devices/:id/reset — durable local-device wipe command; ACK finalizes backend unbind/token revocation while cloud data is preserved
- [Device Management Guide](https://docs.bota.dev/guides/
…

Related sites

Explore similar publishers →

Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.

Machine-readable: GET /v1/resolve?q=bota.dev · GET /v1/domain/bota.dev · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for bota.dev:
1. POST https://agentwebmap.com/v1/sites/bota.dev/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://bota.dev/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/bota.dev/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/bota.dev).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.