> For the complete documentation index, see [llms.txt](https://docs.nfh.global/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nfh.global/product-documentation/products/onix.md).

# ONIX — connect to everything

ONIX is an enterprise-grade middleware adapter system designed to facilitate seamless communication in any NFH fabric-enabled network.

> **Realises the NFH fabric** [**Network Adapters Edge**](/product-documentation/products/onix.md) **service.**

### Overview

ONIX is an enterprise-grade middleware adapter system designed to facilitate seamless communication in any NFH fabric-enabled network. It acts as a protocol adapter between consumer nodes (buyer applications) and provider nodes (seller platforms), ensuring secure, validated, and compliant message exchange across various commerce networks.

### Features

#### 🔌 **Plugin-Based Architecture**

* **Dynamic Plugin Loading**: Load and configure plugins at runtime without code changes
* **Extensible Design**: Easy to add new functionality through custom plugins
* **Hot-Swappable Components**: Update plugins without application restart (in development)

#### 🔐 **Enterprise Security**

* **Ed25519 Digital Signatures**: Cryptographically secure message signing and validation
* **Vault Integration**: Centralized secrets and key management
* **Request Authentication**: Every message is authenticated and validated
* **TLS/SSL Support**: Encrypted communication channels

#### ✅ **Protocol Compliance**

* **JSON Schema Validation**: Ensures all messages comply with Beckn protocol specifications
* **Version Management**: Support for multiple protocol versions simultaneously
* **Domain-Specific Schemas**: Tailored validation for different business domains

#### 🚀 **High Performance**

* **Caching**: Response caching for improved performance
* **Queue Integration**: Asynchronous message processing via message queues
* **Connection Pooling**: Efficient resource utilization
* **Configurable Timeouts**: Fine-tuned performance controls

#### 📊 **Observability**

* **Structured Logging**: JSON-formatted logs with contextual information
* **Transaction Tracking**: End-to-end request tracing with unique IDs
* **Metrics Support**: Performance and business metrics collection
* **Health Checks**: Liveness and readiness probes for Kubernetes

#### 🌐 **Usecase/Domain Agnostic**

* **Retail & E-commerce**: Product search, order management, fulfillment tracking
* **Mobility Services**: Ride-hailing, public transport, vehicle rentals
* **Logistics**: Shipping, last-mile delivery, returns management
* **Healthcare**: Appointments, telemedicine, pharmacy services
* **Financial Services**: Loans, insurance, payments

For more detailed information, developer guides please visit ONIX [repository](https://github.com/Beckn-One/beckn-onix)

{% embed url="<https://github.com/Beckn-One/beckn-onix>" %}

## The NFH fabric capability: Network Adapters Edge

ONIX realises the NFH fabric **Network Adapters Edge** — the protocol-aware adapter every participant runs. It handles signing, schema validation, policy enforcement, transport, encryption, and audit logging, so participants speak the network correctly without re-implementing the wire.

**What it gives you**

* **Pluggable transport** — HTTP, message queues, custom transports.
* **Signing and verification** — every outbound and inbound message verified.
* **Policy plug-ins** — Rego-based policy enforcement for network rules.
* **Schema validation** — guaranteed conformance to the protocol.
* **Audit logging** — every exchange traceable, signed, and verifiable.

**Where it sits** — reference software NFH publishes (every participant runs their own adapter, on their own infrastructure; NFH never sees the traffic) plus the protocol NFH defines (the adapter's wire format and plug-in interface).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.nfh.global/product-documentation/products/onix.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.