Raclip¶
Raclip records spoken encounters on a small hardware device and gives you programmatic access to the audio. Press a button to record, press another to send. The audio is then ready to fetch via the API.
SDK status
Python SDK at v0.0.1 and Node.js SDK at v0.0.4 — read-only surface (devices + calls). Webhook helpers and device mutation are on the roadmap. The HTTP API is stable and covers everything in the SDKs.
-
Claim a device, connect it to Wi-Fi, generate an API key, record your first encounter, and fetch the audio.
-
Public HTTP endpoints — calls, statistics, webhooks. Every method, parameter, and response shape.
-
pip install raclip. Sync and async clients, typed responses, full quickstart. -
npm install @raclip/sdk. Async client, TypeScript types, full quickstart.
Use cases¶
Raclip is vertical-agnostic — anywhere a spoken encounter is worth keeping:
- Healthcare — clinic visits, telehealth follow-ups, intake conversations.
- Legal — client consultations, depositions, deal calls.
- Field services — construction site walkthroughs, inspections, technician handoffs.
- Anything else — interviews, lectures, customer calls, voice notes.
How the platform fits together¶
- Hardware — A Raclip device with three buttons (On/Off, Start/Stop, Send) and a status LED. Pairs with the cloud over Wi-Fi.
- Console —
console.raclip.ai. Claim devices, manage your org, generate API keys, configure webhooks. - Public API —
api.raclip.ai. Authenticate with an API key, list and fetch recordings, receive webhook events. - Tooling — The Python SDK is one option; any HTTP client works (curl, Node, Go, Ruby, …).