How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
NanoLumens website screenshot

NanoLumens

NanoLumens is an American designer and manufacturer of direct-view LED (dvLED) displays and video walls, headquartered in Atlanta, Georgia and founded in 2006 by Rick Cope. It builds fixed and flexible indoor and outdoor displays in custom sizes, shapes and curvatures across the Engage Pro, Engage, NXT, Nixel, NanoPanel 55, Captivate, Performance, CLRVision, CLRVU and NanoBanner product lines, together with Aurora video processing and the NanoSuite display-management software. Its displays are deployed in retail, casinos, higher education, sports and arenas, control rooms, hospitality, themed entertainment, government, corporate and transportation environments. The software side of the business — the AWARE platform and NanoSuite, powered by the ISAAC ecosystem — markets a JSON REST API and webhook-based alerting for remote diagnostics, content scheduling and display-fleet monitoring, but that API is delivered to display owners through an authenticated tenant and has no public developer portal, API reference or machine-readable specification.

human only

Index entry only — little beyond a description and a link, and nothing machine-readable enough for an agent to act on without a human reading the site first.

Kin Score

API Evangelist profiles NanoLumens the way a machine reads it — 1 machine-readable artifact, 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 — NanoLumens scores 11.3/100 (minimal), with a separate agent-readiness read of 0/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Behind a wall

Why this profile is thin

NanoLumens markets a "JSON REST API" on the NanoSuite product page, and its AWARE production API gateway resolves at api.nanolumens.com (a WSO2 ELB in us-west-2), but there is no public developer portal or reference anywhere on nanolumens.com and the gateway refused every connection on 80/443/8243/9443 — the contract is only available to display owners with an authenticated NanoSuite tenant.

An API exists — we simply could not reach the contract without credentials or a sales conversation. This one is NanoLumens'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://www.nanolumens.com/nanosuite/HTTP 200
  • https://www.nanolumens.com/openapi.jsonHTTP 404
  • https://www.nanolumens.com/swagger.jsonHTTP 404
  • https://www.nanolumens.com/llms.txtHTTP 404
  • https://www.nanolumens.com/.well-known/agent-card.jsonHTTP 404
  • https://api.nanolumens.com/openapi.jsonHTTP 0

Checked 2026-08-04. If this is out of date, tell us on the provider's repo and we will re-run the profile.

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 Kin Score How this is scored →
scored 2026-08-17 · rubric v0.11.0
Composite quality — 11.3/100 · minimal
Contract Quality 0.0 / 25
Developer Ergonomics 1.3 / 20
Commercial Clarity 4.2 / 20
Operational Transparency 0.0 / 13
Governance 0.0 / 12
Discoverability 5.7 / 10
Agent readiness — 0/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 10
MCP Server 0 / 12
Machine-Readable Auth 0 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3
A2A Agent Card 0 / 8
Dry-Run / Simulate Mode 0 / 4
NanoLumens Kin Score — API readiness rating by API Evangelist

Put this on your own site. The badge is drawn live from NanoLumens'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/nanolumens/"
   title="NanoLumens on API Evangelist — API profile and Kin Score">
  <img src="https://apis.io/badge/nanolumens.svg"
       alt="NanoLumens Kin Score — API readiness rating by API Evangelist" width="150" height="150" loading="lazy">
</a>

More shapes, themes and sizes → · Score as JSON · How badges work

How we profile NanoLumens

Each block below is one kind of artifact we hold for NanoLumens. 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.

Security Posture 1

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.

Nanolumens Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Every other property we hold for NanoLumens — 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.

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

Access & Security 1

Authentication, authorization, and security posture

Operate 3

Status, limits, changes, and where to get help

Other 2

Properties that don't map to a standard resource type

← All providers · Data indexed from github.com/api-evangelist/nanolumens · machine-readable index on apis.io

Where this information came from

This is an independent, third-party profile of NanoLumens, 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.