# Neros

> Neros Technologies is an American defense manufacturer (founded 2023, El Segundo, California) that designs and mass-produces low-cost, attritable FPV drones and ground control stations for Western military forces. 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 on GitHub.

Generated by the API Evangelist enrichment pipeline on 2026-08-04 from apis.yml and the artifacts in this repository. Neros does not publish an llms.txt of its own (https://www.neros.tech/llms.txt returned 404).

## What Neros ships

- ARCHER — FPV drone built for modular payloads and resilient comms; mass produced with a secured supply chain, on the DIU Blue UAS Cleared List
- ARCHER STRIKE — kinetic-enabled FPV for effects at range in contested environments
- CROSSBOW — tactical ground control station built for electronic-warfare resistance at range
- LONGBOW — maximum-range ground control station for stationary positions

## APIs

- [APEX — Adaptive Payload EXchange](https://github.com/Neros-Technologies/APEX): Open plug-and-play UART protocol connecting drone hosts and payloads over a standard 10-pin connector. Class-agnostic core (COBS framing, 4-byte outer header, CRC-16/CCITT-FALSE, three-leg discovery handshake, capability exchange, device lifecycle) plus extensible device classes. Protocol version V0; specification snapshot v0.8.0; status Draft. It is a UART wire protocol — there is no base URL, no hosted endpoint, and no authentication scheme.

## Specs

- [APEX — Core](https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Core.md): framing, outer header, baud negotiation, discovery handshake, capability exchange, device lifecycle
- [APEX — Device Classes](https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Device_Classes.md): the traffic_type registry
- [APEX Device Class — Activation](https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Device_Class_Activation.md): devices that progress through enable and trigger phases
- [APEX Device Class — Analog HMI](https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Device_Class_Analog_HMI.md): CRSF / MAVLink 2 control packets in, CVBS video out
- [APEX Device Class — Wayfinding](https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Device_Class_Wayfinding.md): directional cues for the operator
- [APEX Device Class — Repeater](https://github.com/Neros-Technologies/APEX/blob/main/spec/APEX_Device_Class_Repeater.md): RF relay extending C2 and video links
- [APEX mechanical standard](https://github.com/Neros-Technologies/APEX/tree/main/spec/mechanical): STEP 3D model and 2D PDF drawing of the connector assembly

## Code

- [APEX reference implementation](https://github.com/Neros-Technologies/APEX/tree/main/lib): portable C99 library, Host and Device roles, no dynamic allocation, no stdio, no third-party dependencies (MIT)
- [apex_devkit](https://github.com/Neros-Technologies/apex_devkit): STM32G0 host emulator and reference device firmware for bringing up APEX payloads and hosts (MIT, Bazel)
- [bazel_armclang](https://github.com/Neros-Technologies/bazel_armclang): ARM toolchain for embedded Bazel integration
- [Neros-Technologies on GitHub](https://github.com/Neros-Technologies): the organization

## API Evangelist artifacts

- [Packages](packages/neros-packages.yml): first-party libraries and how they are distributed
- [Conventions](conventions/neros-conventions.yml): framing, integrity, addressing, discovery, liveliness, versioning, routing
- [Error catalog](errors/neros-apex-status-codes.yml): apex_status_t return codes, CONFIG_REPLY rejection codes, receiver drop rules
- [Lifecycle](lifecycle/neros-lifecycle.yml): version negotiation, spec snapshot policy, device lifecycle states, implementation maturity
- [Changelog](changelog/neros-changelog.yml): dated APEX release history
- [Data model](data-model/neros-data-model.yml): frame, message and device-class entity graph
- [Conformance](conformance/neros-conformance.yml): wire/mechanical standards plus Blue UAS and NDAA posture
- [Sandbox](sandbox/neros-sandbox.yml): the devkit, host emulator, reference device and test suite
- [Domain security](security/neros-domain-security.yml): TLS, HSTS, DNSSEC, CAA, SPF, DMARC probe
- [Well-known](well-known/neros-well-known.yml): the /.well-known/ probe record (all misses)

## Company

- [Website](https://www.neros.tech/)
- [News](https://www.neros.tech/news)
- [Media](https://www.neros.tech/media)
- [Careers](https://job-boards.greenhouse.io/nerostechnologies)
- [Privacy policy](https://www.neros.tech/legal/privacy-policy)
- [Contact](mailto:info@neros.tech)

## Optional

- [Neros on Forge Global](https://forgeglobal.com/neros_stock/): secondary-market listing (Neros is privately held; no ticker)

## Notes for agents

- There is no Neros HTTP API, no OpenAPI, no GraphQL endpoint, no MCP server and no A2A agent card. api.neros.tech, docs.neros.tech, developer.neros.tech and status.neros.tech do not resolve in DNS.
- Neros' own product documentation sits at https://www.neros.tech/protected-downloads and returns HTTP 401 — it is customer-only.
- APEX is a Draft specification. The specification documents and the C reference library are versioned together; the current snapshot is in VERSION.txt.
- APEX V0 defines no authentication, authorization or encryption. The trust boundary is the physical connector.