Steno
Steno is a Los Angeles-based legal technology and litigation services company serving more than 1,200 US law firms with court reporting, remote and hybrid depositions, legal videography, interpreting, and record retrieval. Its software products are Steno Connect for Zoom (a videoconferencing and exhibit-handling app purpose-built for remote depositions, hearings, and bench trials), Firm Dashboard (scheduling, job management, file access, invoicing, SAML SSO, MFA, and role-based access control), Transcript Genius (AI-assisted transcript search, summarization, and video clip cutting), and DelayPay deferred-payment financing for plaintiff firms. Steno does not operate a public developer program: its integration surface is distributed through host platforms as a Salesforce AppExchange managed package for Litify, a Clio App Directory listing for Clio Manage, and a Zoom Marketplace app, each authenticated with an organization-scoped API key that Steno issues on request. Steno Connect, Firm Dashboard, and Ops are audited SOC 2 Type II and HIPAA by Linford & Company LLP, with posture published at a Vanta-hosted trust center.
More than an index entry, but the surface is still mostly links rather than artifacts — the cohort most likely to move a full band from modest, well-targeted work.
API Evangelist profiles Steno the way a machine reads it — 4 machine-readable artifacts across 1 API, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.
Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — Steno scores 26.4/100 (emerging), with a separate agent-readiness read of 9/100 (agent aware). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.
Why this profile is thin
Steno's API exists and is named on its own status page as "Core API services for Steno platform", but the only way to reach it is a Salesforce AppExchange managed package or a Clio App Directory listing whose key Steno issues per Salesforce Organization ID on request — there is no developer.steno.com or docs.steno.com host at all (both NXDOMAIN) and api.steno.com answers AWS API Gateway {"message":"Forbidden"} on every anonymous spec path.
An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is Steno's to change: publishing the reference and a machine-readable spec at a public URL, while keeping key issuance behind whatever gate they like, would let an integrator evaluate the API before committing to a call.
What we probed
https://api.steno.com/openapi.json→ HTTP 403https://api.steno.com/v1/openapi.json→ HTTP 403https://status.steno.com/→ HTTP 200https://help.steno.com/steno-litify-integration→ HTTP 200https://steno.com/llms.txt→ HTTP 404
Kin Score
This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.
Kin Score
How this is scored →scored 2026-08-17 · rubric v0.11.0
Put this on your own site. The badge is drawn live from Steno's current Kin Score — paste it once and it updates itself every time the score is recomputed. It follows your visitor's light or dark setting, and it links back here so anyone who sees it can read the full breakdown.
<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/steno/"
title="Steno on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/steno.svg"
alt="Steno Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>[](https://providers.apievangelist.com/providers/steno/)<!-- Kin Score · API Evangelist -->
<a href="https://providers.apievangelist.com/providers/steno/"
title="Steno on API Evangelist — API profile and Kin Score">
<img src="https://apis.io/badge/steno/card.svg"
alt="Steno Kin Score — API readiness rating by API Evangelist" width="340" height="120" loading="lazy">
</a>More shapes, themes and sizes → · Score as JSON · How badges work
How we profile Steno
Each block below is one kind of artifact we hold for Steno. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.
APIs 1
Each API is captured as its own OpenAPI definition — every operation, parameter, and response. This is the single most useful machine-readable description of what an API does, and it's what lets us score, lint, mock, and generate against it without asking the provider for anything.
Individual APIs this provider publishes, each with its own machine-readable definition.
Steno Integration API
The private, organization-scoped HTTP API behind Steno's first-party case-management integrations. The Steno-Litify Salesforce managed package is configured with a Steno API URL...
Security Posture 3
Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Resources
Every other property we hold for Steno — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.
Get Started 1
Portal, sign-up, and the first successful call
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 3
Pagination, idempotency, versioning, errors, and events
Build 1
SDKs, sample code, and the tooling you integrate with
Access & Security 4
Authentication, authorization, and security posture
Operate 2
Status, limits, changes, and where to get help
Commercial 3
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
← All providers · Data indexed from github.com/api-evangelist/steno · machine-readable index on apis.io
This is an independent, third-party profile of Steno, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.
The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.
Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.
info@apievangelist.com
·
Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and
you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.