Documentation, in plain terms.
Everything you need to use Felarity well — from your first session to running it from your own code.
Quick links
Start where you are. If you're new, the first card is the door. If you're integrating, jump to the API reference.
Getting started
Create a workspace, open your first session, and read your first signed report. About fifteen minutes, no code required.
Meeting analysis
What happens between the moment a meeting starts and the moment a signed report lands. The eleven stages, named and explained.
Attestation guide
The eight-node Merkle chain, the Ed25519 signing key, and how to verify a report on a machine that has never spoken to Felarity.
API reference
Every endpoint, every header, every error code. Bearer flrt_* tokens, JSON in, JSON or SSE out.
Industries
How to pick the right industry profile, what each analyst role contributes, and when to override the defaults.
Security
Tenant isolation, encryption posture, retention controls, MFA, BYOK, and what we will and won't do with your audio.
What Felarity is
Felarity is forensic intelligence over meetings. We do not sell transcription — transcription is the first step in a much longer pipeline whose job is to find what was actually said, who said it, what contradicted what, and how confident you should be about each of those claims. The product was built for the rooms where the answer to "what was agreed?" can move money, livelihoods, or liberty, and where "I think they said…" is not good enough.
Under the hood, every meeting is processed through an eleven-stage pipeline: live transcription, live contradiction detection, audio capture for the session, full-session diarization, acoustic credibility markers, confrontation response classification, speaker sample extraction, contradiction-to-speaker attribution, DeBERTa-v3 NLI re-scoring, topology analysis of the contradiction graph, and a final council pass with full speaker context. The output is signed with Ed25519 and bound to an eight-node SHA-256 Merkle chain, so anyone with the public key can verify — months or years later — that the report you're reading is the report we produced, untouched.
What's in these docs
For the person in the room
How to run a session well, how to read a report, how to invite teammates, how to set retention, how to export and how to delete.
For the person writing the integration
The HTTP surface, the SSE event shapes, the BYOK key model, and the OpenAPI spec you can drop into Postman or your generator of choice.
- API reference — base URL
https://api.felarity.com/v1 - OpenAPI 3.1 spec (JSON)
- Authentication & Bearer tokens
- BYOK — bring your own key
- Webhooks
- Error codes
Quick check that your key works — replace the token with your own:
curl -H "Authorization: Bearer flrt_..." \
https://api.felarity.com/v1/usageGet help
Three doors, depending on what you need.
Product & billing
For account questions, billing issues, or anything not working the way the docs say it should.
Response within one business day on Starter; same-day on Professional; named contact on Enterprise.
Other operators
Discussions about industry profiles, attestation workflows, and how other teams structure their sessions. Read-only without an account; post with a workspace.
Vulnerabilities only
Suspected vulnerabilities, signing-key concerns, or anything that should not be sent through general support. PGP key on the disclosure page.
Stay current
The pipeline changes. The signing key rotates on a published schedule. New analyst roles ship. We log all of it — including the things we got wrong and reverted — on the changelog. It's the most boring page on the site, and the one we'd most like you to read.
Can't find what you need? Email hello@felarity.com and tell us what you were looking for. Missing docs are a bug.