LVT

LVT (LiveView Technologies) is an American physical-security company that builds solar-powered, cellular-connected mobile surveillance units (MSUs) and the SaaS/PaaS platform that runs them — live video, AI analytics, alerting, lights, loudspeakers and AI talk-down — for retail, commercial, industrial, critical-infrastructure and public-sector sites. Founded in 2005 and headquartered in American Fork, Utah, LVT publishes a public Partner API: a REST service over JSON, described by a first-party OpenAPI 3.0.3 document on GitHub, that lets SOC operators and integrators list live units and locations, control cameras (pan/tilt/zoom), start RTSP and WebRTC streams through the LVT camera relay, play sounds, toggle lights, initiate speaker talk-down, review and resolve security alert events, fetch signed media URLs, and register HMAC-signed webhooks. The same API backs LVT's pre-built integrations with Immix, Axon Fusus and Genetec Security Center, and LVT units also present themselves to third-party VMS platforms as ONVIF cameras.

LVT publishes 9 API contracts indexed on the APIs.io network, including Cameras API, Events API, Live Units API, and 6 more. Tagged areas include Company, Physical Security, Video Surveillance, Camera, and Video Streaming.

The LVT catalog on APIs.io includes 1 event-driven AsyncAPI specification and 1 Spectral governance ruleset.

LVT’s developer surface includes authentication, documentation, API reference, getting-started guide, support, engineering blog, pricing, and 28 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

58.0/100 strong ▬ flat Agent 30/100 agent ready Front door AI 3/6 light Heartbeat 100/100 alive saas Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

AccessPaidSelf serve

1 published contract 4 Agent Skills

Company Physical Security Video Surveillance Camera Video Streaming WebRTC RTSP ONVIF IoT Alerts Webhook Public Safety Retail Critical Infrastructure

What this lets a business do 2

Business capabilities this provider's published APIs can perform, derived from its own contracts. Browse all capabilities →

Retail Loss Prevention Management

BC-2340

CamerasLiveUnitsTalkdown

GET /cameras/{cameraId} GET /cameras/{cameraId}/position POST /cameras/{cameraId}/streams POST /liveUnits/{liveUnitId}:call

Developer Platform & API Ecosystem Management

BC-4270

Webhooks

POST /webhooks PATCH /webhooks/{webhookId} POST /webhooks:test

Kin Score

Kin Score How this is scored →
scored 2026-11-02 · rubric v0.26.0

Composite quality — 58.0/100 · strong

Contract Quality 11.3 / 19

Developer Ergonomics 6.0 / 15

Access Clarity 11.4 / 15

Operational Transparency 3.6 / 10

Contract Governance 2.9 / 9

Discoverability 5.5 / 8

Regulatory Posture 6.8 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 30/100 · agent ready

Machine-Readable Contract 18 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 10 / 10

Idempotency 0 / 9

Stable Error Semantics 8 / 8

Request/Response Examples 7 / 7

Rate-Limit Signaling 7 / 7

Typed Event Surface 6 / 6

Agent Skills 5 / 5

Well-Known Catalog 0 / 4

Consent & Bot Identity 0 / 3

A2A Agent Card 0 / 8

Dry-Run / Simulate Mode 0 / 4

Delegated User Identity 0 / 6

Protected Resource Metadata 0 / 5

Registration Without a Human 0 / 6

Agentic Commerce Well-Known Document 0 / 5

Pagination 5 / 5

Distinct Operations 3 / 3

MCP Tool Quality 6 / 6

Regulatory Posture applies to this provider. Its tags matched the Horizontal (data, software, accessibility, platform) regime, so Regulatory Posture carries 15 points of the composite. If this regime is wrong for your business, say so on your provider repo — the applicability map is public and we will correct it.

Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it carries 10 points of the composite. It is scored from the published contracts themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in front of it, and the first time that check is skipped a duplicate record is created. Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet, not penalised by it.

The six quality facets above are damped to 75 points between them, because the conditional facet above carries the other 25. That is why each facet's contribution is shown against a damped maximum: raising a quality facet moves the composite by 75% of its nominal weight, not 100%. The full arithmetic is at apis.io/rating/.

Show this score on your site.

It updates itself when the score changes. Paste this where you link to your API docs:

<a href="https://apis.io/providers/lvt/"><img src="https://apis.io/badge/lvt/card.svg" alt="LVT on APIs.io — Kin Score by API Evangelist"></a>

Other styles, a README pill and a shields.io endpoint are on the badge page.

Raise your score.

Agent readiness — checks not met, largest first (exact, from this profile):

MCP Server +12 pts — deployment.mode + probe verdict on the mcp/ manifest, not the pointer; an unprobed slug falls back to authorship
Agentic Access Contract +10 pts — agentic_access artifact present (x-agentic-access), graded by author
Idempotency +9 pts — OpenAPI mutating operations declare an idempotency key — a header, a request-body property, or a named de-duplication token whose own description says so (verified); else common[].type matches /idempoten/i (documented)
A2A Agent Card +8 pts — a2a/-a2a.yml manifest, graded on conformance.grade against A2A 1.0.0
Registration Without a Human +6 pts — a `registration_endpoint` in the served RFC 8414 / OIDC discovery document
Delegated User Identity +6 pts — a served discovery document listing authorization_code in grant_types_supported (served), else an oauth2 authorizationCode flow or openIdConnect declared in an OpenAPI (documented)

6 more unmet checks in the Agent Readiness table above.

Kin Score — facets with the most composite points still available (weight × headroom):

Developer Ergonomics scores 39.9 — up to +12.0 composite points
Contract Quality scores 60.3 — up to +9.9 composite points
Operational Transparency scores 36.8 — up to +8.2 composite points

Each check links to what satisfies it. Publish the artifact, or tell us where it already lives, and the score moves on the next scoring run.

Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from the provider profile at artifacts.apis.io/lvt/apis.yml: open an issue on github.com/api-evangelist/lvt to ask a question or point us at an artifact you publish. Submit an artifact on GitHub — free → Manage your own listing — the Influence plan, $499/mo →

Markets this provider is in provisional

The Kin Score Market layer reads a provider inside its market: its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted: not part of the Kin Score or agent readiness.

Market	Position	Depth	Registered MCP server	Declares compatibility
Government Cloud (FedRAMP, GovRAMP, G-Cloud)	undeclared	-	-	-
Public Safety and NG911 (first-responder apps, CJIS, 911)	undeclared	-	-	-
ONVIF Video Analytics (video surveillance, edge cameras, computer vision)	undeclared	-	-	-

Registered MCP server and declares compatibility are report only — not weighted. Undeclared means we found nothing we can read, so there is no number: we never infer integrations.

Standards implemented 3

Standards this provider implements or carries. De facto ones are profiled and measured by the API Commons; formal ones come from the standards directory and are linked by the provider's own tags. The evidence column says how each claim was established — not that it was made.

RTSP

tagged — the provider's own APIs.json carries the standard as a tag; implementation not verified

OpenAPI

measured — observed by APIs.io (published)

OAuth 2.0

measured — observed by APIs.io (declared)

APIs 9

Individual APIs this provider publishes, each with its own machine-readable definition.

LVT Cameras API

Operations on cameras

LVT Events API

The Events API from LVT — 5 operation(s) for events.

LVT Live Units API

Operations on LiveUnits

LVT Locations API

Operations on locations

LVT Media API

The Media API from LVT — 1 operation(s) for media.

LVT Streams API

The Streams API from LVT — 3 operation(s) for streams.

LVT Talkdown API

Operations related to Partner Talkdown

LVT Webhooks API

Operations on webhooks

LVT Public Keys API

Operations related to outbound message verification

Scroll for all 9

Agent Skills 4

Packaged agent skills for driving this provider's APIs from an AI assistant.

lvt-deter-onsite-activity

AGENT SKILL

lvt-live-stream-a-camera

AGENT SKILL

lvt-register-a-webhook-receiver

AGENT SKILL

lvt-triage-a-security-event

AGENT SKILL

Pricing Plans 2

Published pricing tiers and plan structures.

Lvt Plans Pricing

2 plans

PLANS

Lvt Price Estimates

0 plans

PLANS

Rate Limits 1

Documented rate limits and quota policies.

Lvt Rate Limits

0 limits

RATE LIMITS

FinOps 1

Cost, billing, and metering signals for API financial operations.

Lvt Finops

FINOPS

Event Specifications 1

AsyncAPI definitions for this provider's event-driven and streaming APIs.

Lvt Webhooks

ASYNCAPI

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LVT API Rules

55 rules · 45 errors 7 warnings 3 info

SPECTRAL

OpenAPI Overlays 1

Overlays applied on top of this provider's contracts. Each card says who wrote it: a document the provider publishes, or one API Evangelist derived or generated.

Lvt Partner Api Overlay

9 actions · update · api.yaml

GENERATED

Security Posture 4

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Lvt Authentication

oauth2 · 1 scheme

SECURITY

Lvt Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Lvt Vulnerability Disclosure

Bugcrowd · contact published

SECURITY

Lvt Trust Center

trust center published

SECURITY

Scopes 1

OAuth scopes governing access to this provider's APIs.

Lvt Scopes

3 scopes · clientCredentials

3 scopes

SCOPES

Resources

Get Started 3

Portal, sign-up, and the first successful call

DeveloperPortal

DeveloperPortal

GettingStarted

GettingStarted

SignUp

SignUp

Documentation 2

Reference material describing how the API behaves

Documentation

Documentation

APIReference

APIReference

Agent Surfaces 3

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

X-MCPServerCandidate

X-MCPServerCandidate

AgentSkill

AgentSkill

Design & Contract 6

Pagination, idempotency, versioning, errors, and events

Conformance

ErrorCatalog

Lifecycle

Conventions

DataModel

Webhooks

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

ToolCrosswalk

ToolCrosswalk

Access & Security 7

Authentication, authorization, and security posture

DomainSecurity

OAuthScopes

Authentication

TrustCenter

Compliance

VulnerabilityDisclosure

VulnerabilityDisclosure

Security

Security

Scroll for all 7

Operate 3

Status, limits, changes, and where to get help

Support

Support

StatusPage

StatusPage

RateLimits

RateLimits

Commercial 4

Pricing, plans, and the legal terms of use

Pricing

TermsOfService

PrivacyPolicy

Plans

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 2

Properties that don't map to a standard resource type

CapabilityMap

CapabilityMap

Overlay

Overlay

Source (apis.yml)

aid: lvt
name: LVT
description: 'LVT (LiveView Technologies) is an American physical-security company that builds solar-powered, cellular-connected
  mobile surveillance units (MSUs) and the SaaS/PaaS platform that runs them — live video, AI analytics, alerting, lights,
  loudspeakers and AI talk-down — for retail, commercial, industrial, critical-infrastructure and public-sector sites. Founded
  in 2005 and headquartered in American Fork, Utah, LVT publishes a public Partner API: a REST service over JSON, described
  by a first-party OpenAPI 3.0.3 document on GitHub, that lets SOC operators and integrators list live units and locations,
  control cameras (pan/tilt/zoom), start RTSP and WebRTC streams through the LVT camera relay, play sounds, toggle lights,
  initiate speaker talk-down, review and resolve security alert events, fetch signed media URLs, and register HMAC-signed
  webhooks. The same API backs LVT''s pre-built integrations with Immix, Axon Fusus and Genetec Security Center, and LVT units
  also present themselves to third-party VMS platforms as ONVIF cameras.'
url: https://raw.githubusercontent.com/api-evangelist/lvt/refs/heads/main/apis.yml
deliveryModel:
  model: saas
  open_source: false
  commercial: true
  callable_host: true
  label: Hosted service · you call their endpoint
  confidence: high
  source:
  - openapi
  - pricing
  generated: '2026-08-28'
  method: derived
accessModel:
  pricing: paid
  onboarding: self-serve
  trial: false
  try_now: false
  public: false
  gated: none
  gated_source:
  - onboarding
  label: Paid · Self-serve signup
  confidence: high
  source:
  - plans
  - authentication
  - rate-limits
  - security
  generated: '2026-11-02'
  method: derived
image: https://cdn.prod.website-files.com/674d649ddd92d4cd09236107/6848c7616683823ae0acc47c_a61093f6d3186e071147c4359eed84e2_lvt-open-graph-preview_v1.jpg
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.20'
created: '2026-08-25'
modified: '2026-08-25'
tags:
- Company
- Physical Security
- Video Surveillance
- Camera
- Video Streaming
- WebRTC
- RTSP
- ONVIF
- IoT
- Alerts
- Webhook
- Public Safety
- Retail
- Critical Infrastructure
tags_raw:
- Company
- Physical Security
- Video Surveillance
- Cameras
- Video Streaming
- WebRTC
- RTSP
- ONVIF
- IoT
- Alerts
- Webhooks
- Public Safety
- Retail
- Critical Infrastructure
apis:
- aid: lvt:lvt-cameras-api
  name: LVT Cameras API
  description: Operations on cameras
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Camera
  tags_raw:
  - Cameras
  properties:
  - type: OpenAPI
    url: openapi/lvt-cameras-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-events-api
  name: LVT Events API
  description: The Events API from LVT — 5 operation(s) for events.
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Event
  tags_raw:
  - Events
  properties:
  - type: OpenAPI
    url: openapi/lvt-events-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-liveunits-api
  name: LVT Live Units API
  description: Operations on LiveUnits
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - LiveUnits
  properties:
  - type: OpenAPI
    url: openapi/lvt-liveunits-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-locations-api
  name: LVT Locations API
  description: Operations on locations
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Location
  tags_raw:
  - Locations
  properties:
  - type: OpenAPI
    url: openapi/lvt-locations-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-media-api
  name: LVT Media API
  description: The Media API from LVT — 1 operation(s) for media.
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Media
  properties:
  - type: OpenAPI
    url: openapi/lvt-media-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-streams-api
  name: LVT Streams API
  description: The Streams API from LVT — 3 operation(s) for streams.
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Streams
  properties:
  - type: OpenAPI
    url: openapi/lvt-streams-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-talkdown-api
  name: LVT Talkdown API
  description: Operations related to Partner Talkdown
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Talkdown
  properties:
  - type: OpenAPI
    url: openapi/lvt-talkdown-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-webhooks-api
  name: LVT Webhooks API
  description: Operations on webhooks
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - Webhook
  tags_raw:
  - Webhooks
  properties:
  - type: OpenAPI
    url: openapi/lvt-webhooks-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
- aid: lvt:lvt-public-keys-api
  name: LVT Public Keys API
  description: Operations related to outbound message verification
  humanURL: https://docs.lvt.com/r/lvt-partner-api-manual
  baseURL: https://api.lvt.com/v1
  tags:
  - PublicKeys
  tags_raw:
  - Public Keys
  properties:
  - type: OpenAPI
    url: openapi/lvt-public-keys-api-openapi.yml
  - type: Documentation
    url: https://docs.lvt.com/r/lvt-partner-api-manual
  - type: APIReference
    url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
  - type: GettingStarted
    url: https://github.com/LiveViewTech/lvt-public-api
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: CapabilityMap
  url: capabilities/lvt-capability-edges.yml
  name: LVT Business Capability Map
- type: DomainSecurity
  url: security/lvt-domain-security.yml
- type: OAuthScopes
  url: scopes/lvt-scopes.yml
- type: Authentication
  url: authentication/lvt-authentication.yml
- type: Website
  url: https://www.lvt.com/
- type: DeveloperPortal
  url: https://docs.lvt.com/
- type: Documentation
  url: https://docs.lvt.com/r/lvt-partner-api-manual
- type: APIReference
  url: https://github.com/LiveViewTech/lvt-public-api/blob/master/api-specs/api.yaml
- type: GettingStarted
  url: https://github.com/LiveViewTech/lvt-public-api
- type: GitHubOrganization
  url: https://github.com/LiveViewTech
- type: Support
  url: https://www.lvt.com/contact
- type: Blog
  url: https://www.lvt.com/blog
- type: Pricing
  url: https://www.lvt.com/pricing
- type: SignUp
  url: https://vms.liveviewtech.com/
- type: TermsOfService
  url: https://www.lvt.com/legal/msa
- type: PrivacyPolicy
  url: https://www.lvt.com/legal/privacy
- type: StatusPage
  url: https://status.lvt.com/
- type: TrustCenter
  url: https://trust.lvt.com/
- type: LLMsTxt
  url: llms/lvt-llms.txt
- type: Packages
  url: packages/lvt-packages.yml
- type: X-MCPServerCandidate
  url: mcp/lvt-mcp.yml
  note: 'Renamed from MCPServer 2026-09-03 (roadmap#247): the manifest self-describes as status: candidate — a tool list derived
    from the published API contracts, not an existing server. The scorer already read the manifest and reported mcp_server
    correctly; the MCPServer type was crediting the artifact-type surfaces with a server that does not exist.'
- type: ToolCrosswalk
  url: mcp/lvt-tool-crosswalk.yml
- type: Overlay
  url: overlays/lvt-partner-api-overlay.yaml
- type: Conformance
  url: conformance/lvt-conformance.yml
- type: Compliance
  url: conformance/lvt-conformance.yml
- type: ErrorCatalog
  url: errors/lvt-problem-types.yml
- type: Lifecycle
  url: lifecycle/lvt-lifecycle.yml
- type: VulnerabilityDisclosure
  url: security/lvt-vulnerability-disclosure.yml
- type: Security
  url: security/lvt-vulnerability-disclosure.yml
- type: Conventions
  url: conventions/lvt-conventions.yml
- type: DataModel
  url: data-model/lvt-data-model.yml
- type: Webhooks
  url: asyncapi/lvt-webhooks.yml
- type: AgentSkill
  url: skills/_index.yml
- type: Plans
  url: plans/lvt-plans-pricing.yml
- type: RateLimits
  url: rate-limits/lvt-rate-limits.yml
x-enrichment:
  date: '2026-08-25'
  status: enriched
  artifacts_added: 25
  pass: local-v1

LVT API — frequently asked questions

Does LVT have an API?

Yes. APIs.io lists 9 APIs from LVT, including LVT Cameras API, LVT Events API and LVT Live Units API, and 6 more.

Is there an OpenAPI specification for the LVT API?

Yes. APIs.io indexes 9 OpenAPI specifications for LVT, each linked for download from this page.

How do I authenticate with the LVT API?

LVT documents its authentication (oauth2 · 1 scheme). The details are profiled on APIs.io as Lvt Authentication.

How much does the LVT API cost?

APIs.io lists 2 pricing plans for LVT, with each plan's price, limits and inclusions under Pricing Plans on this page.

Is the LVT API ready for AI agents?

LVT has a Kin Score of 58.0 out of 100 (strong) and an Agent Readiness score of 29.8 (agent-ready), scored by API Evangelist on 2026-11-02.

Work with this as data

Every provider here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for providers

9 MCP tools reach this

find_providersBrowse and filter every provider in the catalog.
get_provider_artifactsEvery artifact this provider publishes, grouped by type.
get_provider_operationsEvery operation across all of their OpenAPIs — one call instead of parsing every spec.
get_provider_toolsEvery MCP tool they ship, with the operation each wraps.
get_provider_evidenceHow each part of their score was established. Free — the basis for a claim should not sit behind it.
get_provider_ratingPRO — composite, band, trend and facet scores.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This provider

curl "https://apis.io/api/v1/providers/lvt"

All providers

curl "https://apis.io/api/v1/providers?limit=25"

Every operation they expose

curl "https://apis.io/api/v1/providers/lvt/operations?limit=25"

How their score was established

curl "https://apis.io/api/v1/providers/lvt/evidence"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.