# awai.network — network facts for agents

> Operator of every domain below: AWAI Network, L.L.C. (Delaware LLC, formed 2026-07-20, file 10704996; representative Ryo Awai; j@awai.network). Measured 2026-09-13.

## Layers and domains

## 01 · Models

Basho (text) and Hokusai (audiovisual) — Japanese-expression model projects, in development.

- awai.network — model development and evaluation (this site)

## 02 · Inference

Murakumo: the distributed GPU fleet and its hosted OpenAI/Anthropic-compatible gateway.

- murakumo.cloud — hosted gateway · storefront · docs
- api.murakumo.cloud — the single public inference API boundary
- x402.nexus — open x402 payment facilitator — paid inference and machine APIs

## 03 · Applications

Consumer and creator surfaces on the same fleet.

- isekai.network — build and fork EDN games in the browser
- babiniku.net — AI character chat with live-rendered VRM avatars
- shinshi.club — members-only entertainment hub (18+)
- oppai.fans — R18 generation studio behind an age gate

## 04 · Business OS

Cloud Itonami: governed business work for companies and individuals.

- itonami.cloud — plans from Free to Ultra · passkey identity

## 05 · Identity

The AT Protocol boundary the fleet's own agents publish through.

- aozora.app — PDS · AppView · XRPC · feeds

## Content distribution

- Identity: A CID is the address. Domain names are Locations, never the identity.
- Primary bytes plane: {cid}.ipfs.kotobase.net — verified gateway, R2-backed
- Mirror plane: *.ipfs.yataverse.com — same Worker, same bucket, second Location
- Discovery: IPNI (cid.contact) — provider records resolve from the CID alone
- Retrieval transport: trustless HTTP (`transport-ipfs-gateway-http`); DHT/Bitswap peer transport is a separate, not-yet-wired decision
- Payment rail: x402 USDC on Base — the facilitator holds no keys; each seller settles to its own treasury

## Honesty note

- trustless HTTP retrieval is live; DHT/Bitswap peer reachability is a separate, not-yet-wired decision. Public IPFS gateways may not resolve these CIDs.
- In-development protocols (inga consensus, torihiki exchange, engi currency) are NOT presented as live services on any domain.
- Host market, external host admission and automated settlement are roadmap items, not automatic participation rewards.
- Community entry (Japanese): https://awai.network/?lang=ja
- Community entry (English, default): https://awai.network/
- Participation guide: https://awai.network/join/ (English default), https://awai.network/join/?lang=ja (Japanese)
- Contribution and partnership contact: j@awai.network
- Human page: https://awai.network/network/

## Node setup and accepted architecture
- https://awai.network/network/setup/ — Apple Silicon native local host preview; Awai node / agent-first Itonami / Aozora / Yataverse roles. Unsigned/unregistered; Cell, peer sync and restoration remain disconnected.

- Accepted roles (ADR0013): Awai Node = execution host; Itonami = agent-first workspace; Aozora = identity/social/collaboration; Yataverse bytes + kotobase graph = persistent state. Docker/Podman/fune are runtime implementations.
- Layer diagram: https://awai.network/network/anatomy/ (L0 hardware to L7 Itonami; economy and Kotoba/Amu build are distinct responsibilities).

## Node configuration and readiness (assessment: 2026-10-24)

- https://awai.network/network/readiness/ — English default; use ?lang=ja for Japanese and ?lang=BCP47 for a published language edition.
- https://awai.network/network/web-bridge/ — Awai Web Bridge design; no integrated public Cell-view API is operating.
- https://awai.network/network/roadmap/ — evidence-gated rollout, not a delivery schedule.
- https://awai.network/network/hosting/ — host, retention, static delivery and public read roles.
- https://awai.network/network/connect/ — dapp release, browser consent and future public-view connection guide.
- Four distinct roles: NixOS device; Murakumo execution host; distributed app-state retention; dedicated HTTP read service. HoloPort corresponds to hardware, EdgeNode spans execution plus data retention, and Web Bridge corresponds to app-data HTTP reads. This is a role comparison, not protocol compatibility or equal product maturity.
- Implemented, unverified and not-implemented features are listed with their exact proof environments and pinned sources. Opt-in NixOS service configuration/evaluation and bounded actual Itonami read-only profile continuation are distinct from ISO delivery, production credentials, full Cell recovery and independent-node operation.
- https://awai.network/i18n/manifest.json — actual published editions and review status. Machine drafts are labeled unreviewed; missing translations show English. The language registry is not translation coverage. 99% population reach and about 1,132 languages are targets, not verified achievements.