LISNR

LISNR is a Cincinnati, Ohio company whose ultrasonic data-over-audio technology transmits data between devices using inaudible high-frequency tones instead of radio. Its Radius SDKs (Radius, Radius 3, Point, and the legacy and SDA product lines) embed a transmitter/receiver into iOS, Android, React Native, Linux and Windows applications so that a speaker and a microphone become a proximity data channel for contactless payment, identification, confirmation and device-pairing transactions. Developers work through the LISNR Portal, which issues per-application API tokens and SDK tokens, exposes SDK releases and sample projects, and provides a Tone Creator and a tone-speed calculator. The public Tones Service API generates a downloadable 24-bit audio tone (WAV or MP3) from a hexadecimal payload for a chosen tone profile, with optional AES-256 payload encryption and ToneLock pairing so that only matching receivers can demodulate the tone.

LISNR publishes 10 API contracts indexed on the APIs.io network, including Accounts API, API Tokens API, Applications API, and 7 more. Tagged areas include Company, Ultrasonic, Data Over Audio, Proximity, and Contactless Payments.

The LISNR catalog on APIs.io includes 1 Spectral governance ruleset.

LISNR’s developer surface includes documentation, API reference, getting-started guide, support, signup flow, authentication, and 17 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

20.7/100 emerging ▬ flat Agent 27/100 agent aware Heartbeat 0/100 dormant saas Full breakdown ↓
scored 2026-11-02 · rubric v0.26.0 · Show this score on your site →

2 published contracts 2 Agent Skills

CompanyUltrasonicData Over AudioProximity Contactless PaymentsDevice PairingIdentification Audio IoT SDK

Kin Score

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

Composite quality — 20.7/100 · emerging

Contract Quality 2.8 / 19

Developer Ergonomics 6.3 / 15

Access Clarity 0.0 / 15

Operational Transparency 0.3 / 10

Contract Governance 1.6 / 9

Discoverability 5.5 / 8

Regulatory Posture 2.3 / 15

Create-or-Update Ergonomics 0.0 / 10

Agent readiness — 27/100 · agent aware

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 0 / 7

Rate-Limit Signaling 0 / 7

Typed Event Surface 0 / 6

Agent Skills 5 / 5

Well-Known Catalog 4 / 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 Payments 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/lisnr/"><img src="https://apis.io/badge/lisnr/card.svg" alt="LISNR 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
Rate-Limit Signaling +7 pts — OpenAPI responses document X-RateLimit-* / RateLimit headers (verified), else a rate_limits artifact or RateLimits link (documented)
Request/Response Examples +7 pts — share of operations carrying request/response examples; else an Examples / Code Samples link

8 more unmet checks in the Agent Readiness table above.

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

Contract Quality scores 15.0 — up to +21.3 composite points
Access Clarity scores 0.0 — up to +20.0 composite points
Operational Transparency scores 2.6 — up to +12.7 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/lisnr/apis.yml: open an issue on github.com/api-evangelist/lisnr 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
EMV Card Terminals (card acceptance hardware and kernels)	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 1

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.

OpenAPI

measured — observed by APIs.io (published)

APIs 10

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

LISNR Accounts API

The Accounts API from LISNR — 1 operation(s) for accounts.

LISNR API Tokens API

The API Tokens API from LISNR — 2 operation(s) for api tokens.

LISNR Applications API

The Applications API from LISNR — 2 operation(s) for applications.

LISNR Authentication API

The Authentication API from LISNR — 5 operation(s) for authentication.

LISNR Billing API

The Billing API from LISNR — 1 operation(s) for billing.

LISNR Notifications API

The Notifications API from LISNR — 2 operation(s) for notifications.

LISNR SDK Releases API

The SDK Releases API from LISNR — 1 operation(s) for sdk releases.

LISNR SDK Tokens API

The SDK Tokens API from LISNR — 2 operation(s) for sdk tokens.

LISNR Tones Service API Reference API

The Tones Service API Reference API from LISNR — 1 operation(s) for tones service api reference.

LISNR Users API

The Users API from LISNR — 3 operation(s) for users.

Scroll for all 10

Open Collections 10

Open, tool-agnostic API collections (OpenAPI-derived and Bruno).

LISNR Portal API (observed) Accounts API

OPEN COLLECTION

LISNR Portal API (observed) Accounts API Tokens API

OPEN COLLECTION

LISNR Portal API (observed) Accounts Applications API

OPEN COLLECTION

LISNR Portal API (observed) Accounts Authentication API

OPEN COLLECTION

LISNR Portal API (observed) Accounts Billing API

OPEN COLLECTION

LISNR Portal API (observed) Accounts Notifications API

OPEN COLLECTION

LISNR Portal API (observed) Accounts SDK Releases API

OPEN COLLECTION

LISNR Portal API (observed) Accounts SDK Tokens API

OPEN COLLECTION

LISNR Portal API (observed) Accounts Tones Service API Reference API

OPEN COLLECTION

LISNR Portal API (observed) Accounts Users API

OPEN COLLECTION

Scroll for all 10

Agent Skills 2

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

Generate a LISNR ultrasonic tone

AGENT SKILL

Provision a LISNR application and its tokens

AGENT SKILL

Spectral Rules 1

Spectral governance rulesets for linting and validating these APIs.

LISNR API Rules

58 rules · 48 errors 9 warnings 1 info

SPECTRAL

OpenAPI Overlays 2

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.

Lisnr Portal Overlay

6 actions · update · lisnr-portal-openapi-derived.json

DERIVED

Lisnr Tones Overlay

6 actions · documentation · lisnr-tones-openapi-original.json

DERIVED

Security Posture 2

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

Lisnr Authentication

apiKey · 1 scheme

SECURITY

Lisnr Domain Security

TLSv1.3 · DMARC

SECURITY

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 4

MCP servers, agent skills, and machine-readable catalogs

WellKnown

WellKnown

X-MCPServerCandidate

X-MCPServerCandidate

LLMsTxt

LLMsTxt

AgentSkill

AgentSkill

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

Conformance

DataModel

Build 3

SDKs, sample code, and the tooling you integrate with

GitHubOrganization

GitHubOrganization

Packages

Packages

SDKs

SDKs

Access & Security 2

Authentication, authorization, and security posture

Authentication

Authentication

DomainSecurity

DomainSecurity

Operate 2

Status, limits, changes, and where to get help

Support

Support

HelpCenter

HelpCenter

Company 1

The organization behind the API

Website

Website

Other 1

Properties that don't map to a standard resource type

Overlay

Overlay

Source (apis.yml)

aid: lisnr
name: LISNR
description: LISNR is a Cincinnati, Ohio company whose ultrasonic data-over-audio technology transmits data between devices
  using inaudible high-frequency tones instead of radio. Its Radius SDKs (Radius, Radius 3, Point, and the legacy and SDA
  product lines) embed a transmitter/receiver into iOS, Android, React Native, Linux and Windows applications so that a speaker
  and a microphone become a proximity data channel for contactless payment, identification, confirmation and device-pairing
  transactions. Developers work through the LISNR Portal, which issues per-application API tokens and SDK tokens, exposes
  SDK releases and sample projects, and provides a Tone Creator and a tone-speed calculator. The public Tones Service API
  generates a downloadable 24-bit audio tone (WAV or MP3) from a hexadecimal payload for a chosen tone profile, with optional
  AES-256 payload encryption and ToneLock pairing so that only matching receivers can demodulate the tone.
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: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - authentication
  - security
  generated: '2026-11-02'
  method: derived
image: https://lh3.googleusercontent.com/v89HEtbE-zGOkBwCmWf7zbG9BBtS22tgXzNSgZG4F3fqv90KqLo0yWO5D1PFUxGG-VSIVNgoxsWEVLLjA-pkHA=w205
url: https://raw.githubusercontent.com/api-evangelist/lisnr/refs/heads/main/apis.yml
x-type: company
x-source: vc-portfolio
x-backed-by:
- techstars
specificationVersion: '0.23'
created: '2026-07-17'
modified: '2026-07-19'
tags:
- Company
- Ultrasonic
- Data Over Audio
- Proximity
- Contactless Payments
- Device Pairing
- Identification
- Audio
- IoT
- SDK
tags_raw:
- Company
- Ultrasonic
- Data Over Audio
- Proximity
- Contactless Payments
- Device Pairing
- Identification
- Audio
- Internet of Things
- SDK
apis:
- aid: lisnr:lisnr-accounts-api
  name: LISNR Accounts API
  description: The Accounts API from LISNR — 1 operation(s) for accounts.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - Account
  tags_raw:
  - Accounts
  properties:
  - type: OpenAPI
    url: openapi/lisnr-accounts-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-api-tokens-api
  name: LISNR API Tokens API
  description: The API Tokens API from LISNR — 2 operation(s) for api tokens.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - API Tokens
  properties:
  - type: OpenAPI
    url: openapi/lisnr-api-tokens-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-applications-api
  name: LISNR Applications API
  description: The Applications API from LISNR — 2 operation(s) for applications.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - Application
  tags_raw:
  - Applications
  properties:
  - type: OpenAPI
    url: openapi/lisnr-applications-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-authentication-api
  name: LISNR Authentication API
  description: The Authentication API from LISNR — 5 operation(s) for authentication.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - Authentication
  properties:
  - type: OpenAPI
    url: openapi/lisnr-authentication-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-billing-api
  name: LISNR Billing API
  description: The Billing API from LISNR — 1 operation(s) for billing.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - Billing
  properties:
  - type: OpenAPI
    url: openapi/lisnr-billing-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-notifications-api
  name: LISNR Notifications API
  description: The Notifications API from LISNR — 2 operation(s) for notifications.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - Notification
  tags_raw:
  - Notifications
  properties:
  - type: OpenAPI
    url: openapi/lisnr-notifications-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-sdk-releases-api
  name: LISNR SDK Releases API
  description: The SDK Releases API from LISNR — 1 operation(s) for sdk releases.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - SDK Releases
  properties:
  - type: OpenAPI
    url: openapi/lisnr-sdk-releases-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-sdk-tokens-api
  name: LISNR SDK Tokens API
  description: The SDK Tokens API from LISNR — 2 operation(s) for sdk tokens.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - SDK Tokens
  properties:
  - type: OpenAPI
    url: openapi/lisnr-sdk-tokens-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-tones-service-api-reference-api
  name: LISNR Tones Service API Reference API
  description: The Tones Service API Reference API from LISNR — 1 operation(s) for tones service api reference.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - Tones Service API Reference
  properties:
  - type: OpenAPI
    url: openapi/lisnr-tones-service-api-reference-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
- aid: lisnr:lisnr-users-api
  name: LISNR Users API
  description: The Users API from LISNR — 3 operation(s) for users.
  humanURL: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  baseURL: https://tones.lisnr.com/
  tags:
  - User
  tags_raw:
  - Users
  properties:
  - type: OpenAPI
    url: openapi/lisnr-users-api-openapi.yml
  - type: Documentation
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: APIReference
    url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
  - type: Documentation
    url: https://portal.lisnr.com/developer-resources/api
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: Overlay
  url: overlays/lisnr-portal-overlay.yaml
- type: Website
  url: https://lisnr.com/
- type: DeveloperPortal
  url: https://portal.lisnr.com/
- type: Documentation
  url: https://portal.lisnr.com/developer-resources/
- type: APIReference
  url: https://portal.lisnr.com/assets/tones-docs/tones-docs.html
- type: GettingStarted
  url: https://portal.lisnr.com/help-center/getting-started/
- type: Support
  url: https://lisnr1.atlassian.net/servicedesk/customer/portals
- type: HelpCenter
  url: https://portal.lisnr.com/help-center/
- type: GitHubOrganization
  url: https://github.com/lisnr
- type: SignUp
  url: https://portal.lisnr.com/
- type: Authentication
  url: authentication/lisnr-authentication.yml
- type: Conventions
  url: conventions/lisnr-conventions.yml
- type: ErrorCatalog
  url: errors/lisnr-problem-types.yml
- type: Lifecycle
  url: lifecycle/lisnr-lifecycle.yml
- type: Conformance
  url: conformance/lisnr-conformance.yml
- type: Packages
  url: packages/lisnr-packages.yml
- type: SDKs
  url: packages/lisnr-packages.yml
- type: WellKnown
  url: well-known/lisnr-well-known.yml
- type: X-MCPServerCandidate
  url: mcp/lisnr-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: LLMsTxt
  url: llms/lisnr-llms.txt
- type: DataModel
  url: data-model/lisnr-data-model.yml
- type: DomainSecurity
  url: security/lisnr-domain-security.yml
- type: AgentSkill
  url: skills/_index.yml
x-enrichment:
  date: '2026-07-19'
  status: backfilled
  pass: local-v1
  note: backfilled from .gitignore signal + verified work evidence

LISNR API — frequently asked questions

Does LISNR have an API?

Yes. APIs.io lists 10 APIs from LISNR, including LISNR Accounts API, LISNR API Tokens API and LISNR Applications API, and 7 more.

Is there an OpenAPI specification for the LISNR API?

Yes. APIs.io indexes 10 OpenAPI specifications for LISNR, each linked for download from this page.

How do I authenticate with the LISNR API?

LISNR uses bearer-token authentication (apiKey · 1 scheme). The details are profiled on APIs.io as Lisnr Authentication.

Is the LISNR API ready for AI agents?

LISNR has a Kin Score of 20.7 out of 100 (emerging) and an Agent Readiness score of 26.6 (agent-aware), 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/lisnr"

All providers

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

Every operation they expose

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

How their score was established

curl "https://apis.io/api/v1/providers/lisnr/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.