Neros

Neros Technologies is an American defense manufacturer founded in 2023 and headquartered in El Segundo, California, that designs and mass-produces low-cost, attritable first-person-view (FPV) drones and ground control stations for Western military forces. Its product line includes the ARCHER FPV airframe, ARCHER STRIKE, and the CROSSBOW and LONGBOW ground control stations, built on in-house flight control, powertrain, and radio hardware for electronic-warfare resistance. Neros publishes no public web API; its machine-readable interface contribution is APEX (Adaptive Payload EXchange), an open, MIT-licensed, plug-and-play UART protocol and mechanical connector standard for drone host/payload interoperability, with a C99 reference implementation and a hardware development kit published on GitHub.

Neros is listed with 1 API on the APIs.io network. Tagged areas include Company, Defense, Drones, Unmanned Systems, and UAV.

Neros’ developer surface includes engineering blog, support, changelog, sandbox, and 15 more developer resources.

🌐 Visit website 📡 Profile data on GitHub

19.6/100 emerging ▬ flat Agent 3/100 human only Front door AI 1/6 silent library Full breakdown ↓
scored 2026-10-17 · rubric v0.24.0

1 API

Company Defense Drones Unmanned Systems UAV Aerospace Robotics Hardware Manufacturing Protocol Open Source Embedded

Kin Score

Kin Score How this is scored →
scored 2026-10-17 · rubric v0.24.0

Composite quality — 19.6/100 · emerging

Contract Quality 0.0 / 21

Developer Ergonomics 3.6 / 17

Access Clarity 3.1 / 17

Operational Transparency 2.0 / 11

Contract Governance 1.9 / 10

Discoverability 5.5 / 9

Regulatory Posture 2.9 / 15

Agent readiness — 3/100 · human only

Machine-Readable Contract 0 / 18

Agentic Access Contract 0 / 10

Documented Reversibility 0 / 6

MCP Server 0 / 12

Machine-Readable Auth 0 / 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 0 / 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

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 could not be measured. We hold no machine-readable contract for this provider to read, so there is nothing to measure a write surface against. Excluded rather than scored zero: never-measured and measured-empty are different facts. Publishing an OpenAPI is what makes this facet — and several others — scorable at all.

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

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 github.com/api-evangelist/neros: open an issue to ask a question, or submit a pull request to add artifacts. 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
Drones and Airspace (UAS, UTM, air traffic)	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.

APIs 1

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

APEX — Adaptive Payload EXchange

APEX is Neros Technologies' open, MIT-licensed plug-and-play protocol for connecting drone platforms (hosts) and payloads (devices) over a standard 10-pin connector. The core pr...

Security Posture 1

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

Neros Domain Security

TLSv1.3 · HSTS · DMARC

SECURITY

Resources

Get Started 1

Portal, sign-up, and the first successful call

Sandbox

Sandbox

Agent Surfaces 1

MCP servers, agent skills, and machine-readable catalogs

LLMsTxt

LLMsTxt

Design & Contract 5

Pagination, idempotency, versioning, errors, and events

Conventions

ErrorCatalog

Lifecycle

DataModel

Conformance

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

Compliance

Compliance

DomainSecurity

DomainSecurity

Operate 3

Status, limits, changes, and where to get help

IssueTracker

IssueTracker

Support

Support

ChangeLog

ChangeLog

Commercial 1

Pricing, plans, and the legal terms of use

PrivacyPolicy

PrivacyPolicy

Company 2

The organization behind the API

Website

Website

Blog

Blog

Other 1

Properties that don't map to a standard resource type

SecondaryMarket

SecondaryMarket

Source (apis.yml)

aid: neros
name: Neros
description: Neros Technologies is an American defense manufacturer founded in 2023 and headquartered in El Segundo, California,
  that designs and mass-produces low-cost, attritable first-person-view (FPV) drones and ground control stations for Western
  military forces. Its product line includes the ARCHER FPV airframe, ARCHER STRIKE, and the CROSSBOW and LONGBOW ground control
  stations, built on in-house flight control, powertrain, and radio hardware for electronic-warfare resistance. Neros publishes
  no public web API; its machine-readable interface contribution is APEX (Adaptive Payload EXchange), an open, MIT-licensed,
  plug-and-play UART protocol and mechanical connector standard for drone host/payload interoperability, with a C99 reference
  implementation and a hardware development kit published on GitHub.
url: https://raw.githubusercontent.com/api-evangelist/neros/refs/heads/main/apis.yml
deliveryModel:
  model: library
  license_evidence:
    not_product:
    - neros-technologies/apex
  open_source: unknown
  commercial: false
  callable_host: false
  label: Library · distributed through package registries, no callable service
  confidence: low
  source:
  - repository-not-product
  generated: '2026-09-25'
  method: derived
accessModel:
  pricing: unknown
  onboarding: unknown
  trial: false
  try_now: false
  public: false
  label: Unknown
  confidence: low
  source:
  - security
  - sandbox
  generated: '2026-09-02'
  method: derived
image: https://cdn.prod.website-files.com/65c24ca07768af3ed05a9982/65c28f5597ed1e93b45a67a3_webclip.png
x-type: company
x-source: harvest:secondary-market
specificationVersion: '0.23'
created: '2026-08-04'
modified: '2026-08-04'
tags:
- Company
- Defense
- Drones
- Unmanned Systems
- UAV
- Aerospace
- Robotics
- Hardware
- Manufacturing
- Protocol
- Open Source
- Embedded
tags_raw:
- Company
- Defense
- Drones
- Unmanned Systems
- UAV
- Aerospace
- Robotics
- Hardware
- Manufacturing
- Protocols
- Open Source
- Embedded
- Open-Source
apis:
- aid: neros:apex
  name: APEX — Adaptive Payload EXchange
  description: 'APEX is Neros Technologies'' open, MIT-licensed plug-and-play protocol for connecting drone platforms (hosts)
    and payloads (devices) over a standard 10-pin connector. The core protocol is class-agnostic — COBS framing, a 4-byte
    outer header, CRC-16/CCITT-FALSE, baud negotiation, a three-leg discovery handshake (DEVICE_INFO to CONFIG_REPLY to CONFIG_ACK),
    capability exchange, and a device lifecycle the host tracks — while payload behavior is defined in separate device-class
    specifications (Activation, Analog HMI, Wayfinding, Repeater; USB_FS_HUB reserved). It is a UART wire protocol, not an
    HTTP API: there is no base URL, no authentication scheme, and no hosted endpoint.'
  humanURL: https://github.com/Neros-Technologies/APEX
  x-transport: uart
  x-protocol-version: V0
  x-spec-version: v0.8.0
  x-status: draft
  tags:
  - Protocol
  - Drones
  - Payloads
  - Embedded
  - Interoperability
  properties:
  - type: SourceCode
    url: https://github.com/Neros-Technologies/APEX
  - type: Specification
    url: https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Core.md
  - type: License
    url: https://github.com/Neros-Technologies/APEX/blob/main/LICENSE
maintainers:
- FN: Kin Lane
  email: kin@apievangelist.com
- FN: APIs.json
  email: info@apis.io
common:
- type: IssueTracker
  url: https://github.com/Neros-Technologies/APEX/issues
- type: Website
  url: https://www.neros.tech/
- type: GitHubOrganization
  url: https://github.com/Neros-Technologies
- type: Blog
  url: https://www.neros.tech/news
- type: Support
  url: mailto:info@neros.tech
- type: PrivacyPolicy
  url: https://www.neros.tech/legal/privacy-policy
- type: SecondaryMarket
  url: https://forgeglobal.com/neros_stock/
- type: Packages
  url: packages/neros-packages.yml
- type: SDKs
  url: packages/neros-packages.yml
- type: Conventions
  url: conventions/neros-conventions.yml
- type: ErrorCatalog
  url: errors/neros-apex-status-codes.yml
- type: Lifecycle
  url: lifecycle/neros-lifecycle.yml
- type: ChangeLog
  url: changelog/neros-changelog.yml
- type: DataModel
  url: data-model/neros-data-model.yml
- type: Conformance
  url: conformance/neros-conformance.yml
- type: Compliance
  url: conformance/neros-conformance.yml
- type: Sandbox
  url: sandbox/neros-sandbox.yml
- type: LLMsTxt
  url: llms/neros-llms.txt
- type: DomainSecurity
  url: security/neros-domain-security.yml
x-enrichment:
  date: '2026-08-04'
  status: enriched
  artifacts_added: 11
  pass: local-v1

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/neros"

All providers

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

Every operation they expose

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

How their score was established

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