Beckn Network

AINative operates the first US-based Beckn-compatible commerce network. The Beckn Protocol is an open standard for decentralized commerce, used by India's ONDC (Open Network for Digital Commerce) to connect millions of buyers and sellers.

Our network brings this to the US market with a lightweight Python implementation running on AINative infrastructure.

Network Architecture

┌─────────────────────────────────────────────────────────┐
│                 AINative US Beckn Network                │
│                                                         │
│  ┌──────────┐    ┌──────────┐    ┌──────────────────┐  │
│  │ Registry │◄──►│ Gateway  │───►│ BPP (Businesses) │  │
│  │          │    │          │    │                    │  │
│  │ - BAPs   │    │ - Routes │    │ - beckn-sandbox   │  │
│  │ - BPPs   │    │   search │    │ - your-bpp.com    │  │
│  │ - Keys   │    │ - Domain │    │ - ...             │  │
│  └──────────┘    │   filter │    └──────────────────┘  │
│                  └──────────┘                           │
│                       ▲                                 │
│                       │                                 │
│               ┌───────┴───────┐                        │
│               │ BAP (Buyers)  │                        │
│               │               │                        │
│               │ - AINative    │                        │
│               │   Marketplace │                        │
│               │ - Your app    │                        │
│               └───────────────┘                        │
└─────────────────────────────────────────────────────────┘

Endpoints

Method	Path	Description
POST	/beckn-network/registry/subscribe	Register as BAP or BPP
POST	/beckn-network/registry/lookup	Find subscribers
GET	/beckn-network/registry/subscribers	List all subscribers
POST	/beckn-network/gateway/search	Route search to BPPs
GET	/beckn-network/health	Network health status

All endpoints are under /api/v1/public/beckn-network/.

Register as a BPP (Seller)

To make your business discoverable on the network:

curl -X POST https://api.ainative.studio/api/v1/public/beckn-network/registry/subscribe \
  -H "Content-Type: application/json" \
  -d '{
    "subscriber_id": "your-company.com",
    "subscriber_url": "https://your-api.com/beckn",
    "type": "BPP",
    "domain": "nic2004:52110",
    "country": "US"
  }'

Response:

{
  "message": {"ack": {"status": "ACK"}},
  "subscriber_id": "your-company.com",
  "action": "registered",
  "status": "SUBSCRIBED"
}

Register as a BAP (Buyer App)

To build a buyer application that searches the network:

curl -X POST https://api.ainative.studio/api/v1/public/beckn-network/registry/subscribe \
  -H "Content-Type: application/json" \
  -d '{
    "subscriber_id": "your-buyer-app.com",
    "subscriber_url": "https://your-app.com/beckn/callback",
    "type": "BAP",
    "domain": "*",
    "country": "US"
  }'

Search via Gateway

Send a Beckn search through the gateway — it routes to all registered BPPs:

curl -X POST https://api.ainative.studio/api/v1/public/beckn-network/gateway/search \
  -H "Content-Type: application/json" \
  -d '{
    "context": {
      "domain": "nic2004:52110",
      "action": "search",
      "version": "1.1.0",
      "bap_id": "your-buyer-app.com",
      "bap_uri": "https://your-app.com/beckn/callback",
      "transaction_id": "txn-001",
      "message_id": "msg-001",
      "timestamp": "2026-06-13T00:00:00Z",
      "country": "US"
    },
    "message": {
      "intent": {
        "descriptor": {"name": "sustainable packaging"}
      }
    }
  }'

Response:

{
  "message": {"ack": {"status": "ACK"}},
  "bpp_count": 1,
  "forwarded": 1
}

The gateway forwards your search to all matching BPPs. BPPs respond asynchronously via your bap_uri callback with on_search containing their catalog.

Beckn Transaction Lifecycle

The full Beckn protocol supports these actions:

Action	Description	Status
search	Discover services	Implemented
on_search	Catalog response	Implemented
select	Choose items	Implemented
on_select	Quote/pricing	Implemented
init	Initialize order	Implemented
confirm	Place order	Implemented
on_confirm	Order confirmation	Implemented
status	Check order status	Implemented
cancel	Cancel order	Implemented
track	Track fulfillment	Planned
rating	Rate transaction	Planned

Supported Domains

Domain Code	Category
nic2004:52110	Retail / Wholesale
ONDC:SRV10	Professional Services
ONDC:SRV11	Local Services
nic2004:60232	Logistics
*	All domains (wildcard)

Network Health

GET /api/v1/public/beckn-network/health

{
  "status": "healthy",
  "network": "AINative US Beckn Network",
  "version": "1.0.0",
  "registry": {
    "bap_count": 1,
    "bpp_count": 1,
    "total_subscribers": 2
  },
  "gateway": {
    "status": "active",
    "domains": ["nic2004:52110", "ONDC:SRV10", "ONDC:SRV11", "*"]
  }
}

Comparison with ONDC

Feature	ONDC (India)	AINative (US)
Protocol	Beckn 1.1.0	Beckn 1.1.0
Region	India only	US (global-ready)
Registration	Formal process (weeks)	Instant API call
Infrastructure	Java (heavy)	Python/FastAPI (lightweight)
Database	External Postgres	Embedded in Core backend
Gateway	Proteantech (managed)	Self-hosted on Railway
Auth	Ed25519 signing (required)	Optional (planned)
Cost	Compliance fees	Free (open network)

Building a BPP

A BPP (Beckn Provider Platform) must implement these callback endpoints:

POST /search      → Return catalog matching the search intent
POST /select      → Return quote for selected items
POST /init        → Initialize order with billing/fulfillment
POST /confirm     → Confirm the order
POST /status      → Return current order status
POST /cancel      → Cancel an active order

Each endpoint receives a Beckn-formatted request with context and message, and must respond with the corresponding on_* action sent to the BAP's bap_uri.

See the Beckn Protocol Specification for detailed schemas.