AENET ecosystems PUBLIC GATEWAY
Request a Pilot
GATEWAY READY
EN ไทย 中文
system-detail K.PUBLIC.SYSTEM

SYS.DEV.01 D07 public-api

Public API

The read-only public API v1 of AENET Cloud Public. It serves public status, time, architecture, development queue, roadmap and early access — with a strictly bounded surface.

Domain: Developer Platform STATUS: active Public boundary: OBSERVATION ONLY Last updated: 2026-08-16
KAP-GRID K.PUBLIC.SYSTEM.C03

System ID

public-api

Status

active

Architecture layers

  • L2 Public Application (router)
  • L4 Public Service (API)

Inputs

  • Public-data snapshots and services (status, time, architecture, queue, roadmap, early access)

Outputs

  • JSON responses with a consistent envelope; registration tickets for early access (D1)

Public interfaces

  • GET /api/v1/status
  • GET /api/v1/time
  • GET /api/v1/architecture
  • GET /api/v1/development-queue
  • GET /api/v1/roadmap
  • GET /api/v1/early-access
  • POST /api/v1/early-access/register

Connected systems

Security boundary

Read-only and bounded. Preview and private routes return 403. No authentication, no write channels beyond the early-access registration path, no core access.

Data direction

Public snapshots → API responses (read). Early-access registration → D1 (the only write path, never to the core).

Public interfaces

Derived from the API registry

GET /api/v1/architecture aenet.public.architecture.v1 active READ-ONLY
GET /api/v1/development-queue aenet.public.development-queue.v1 active READ-ONLY
GET /api/v1/early-access aenet.public.early-access.v1 active READ-ONLY
POST /api/v1/early-access/register aenet.public.early-access.registration.v1 active WRITE
GET /api/v1/roadmap aenet.public.roadmap.v1 active READ-ONLY
GET /api/v1/status aenet.public.status.v1 active READ-ONLY
GET /api/v1/time aenet.public.time.v1 active READ-ONLY
GET /api/v1/wallet aenet.public.wallet.overview.v1 active READ-ONLY
GET /api/v1/wallet/architecture aenet.public.wallet.architecture.v1 active READ-ONLY
GET /api/v1/wallet/evidence aenet.public.wallet.evidence.v1 active READ-ONLY
GET /api/v1/wallet/security aenet.public.wallet.security.v1 active READ-ONLY
GET /public-data/*.json aenet.public.snapshot.* active READ-ONLY

Security

Read-only and bounded. Preview and private routes return 403. No authentication, no write channels beyond the early-access registration path, no core access.

What

Expose public-safe, read-only data in a structured JSON contract while keeping every private route out of reach.

Why

Visitors and developers need machine-readable public data without any path to private or internal systems. The Public API solves this with a v1 contract, an envelope and forbidden/private route controls.

How

Public snapshots → API responses (read). Early-access registration → D1 (the only write path, never to the core).

  • Serve GET /api/v1/status
  • Serve GET /api/v1/time
  • Serve GET /api/v1/architecture
  • Serve GET /api/v1/development-queue
  • Serve GET /api/v1/roadmap
  • Serve GET /api/v1/early-access
  • Serve GET /api/v1/early-access/register (POST registration)
  • Reject preview/private routes with 403
  • Enforce a consistent API envelope

Example

A developer calls GET /api/v1/time and receives the versioned envelope {ok, schema, requestId, issuedAt, data} — read-only, no authentication, no core access.

Inputs

  • Public-data snapshots and services (status, time, architecture, queue, roadmap, early access)

Outputs

  • JSON responses with a consistent envelope; registration tickets for early access (D1)

Dependencies

public-snapshot-layerpublic-timeearly-accessaenet-cloud-public

Lifecycle

  • v1 contract
  • envelope
  • route controls
  • openapi.public.json documentation

Use cases

  • A developer reads the public API contract and examples
  • A visitor checks public status and time through the API
  • A person registers for early access

Limitations

  • Read-only by design — no write API beyond early access
  • No API keys are issued (keyIssuanceDisabled)
  • Preview routes are intentionally unavailable
  • Internal schemas and private routes are never published

Connected systems

  • AENET Cloud Public — The public-facing entrance and observation layer for the AENET ecosystem. It publishes sanitized snapshots, static pages, a public API and an anonymous traffic channel — nothing more.
  • AENET Core — The private AENET ecosystem. It is never publicly routable and may export only sanitized public snapshots to aenet-cloud-public through the snapshot contract.
  • AENET Wallet — Local-first, watch-only Bitcoin wallet architecture with external signing and Rust machine integration. A private operational system of the AENET ecosystem; the public side observes only sanitized snapshots.
  • Development Queue — The public view of what the AENET system is building — a state machine (DISCOVERED → SPECIFIED → BUILDING → VERIFYING → PREVIEW → RELEASED) with no fake progress percentages.
  • Early Access — The public waitlist for testing the AENET public gateway. Applicant records live only in D1, are never indexed, exported or published, and registration is fail-closed without Turnstile verification.
  • KAP Language — A declarative contract style used across this repository to describe the public site, navigation, content, layout, motion, time, traffic and early access in machine-readable files (.kap).
  • Public Snapshot Layer — The layer that publishes sanitized, pre-generated JSON snapshots (site, status, architecture, articles, roadmap, queue, topology, traffic summary) from public-data/.
  • Public Time — The public time service of AENET Cloud Public. It serves canonical UTC with an explicit quality, and never claims atomic verification without a verified atomic source.

Related research

  • The AENET Public Entrance — What this public entrance is, what the public may observe, and where the one-way boundary sits.

Questions people ask

These questions are answered by the content on this page.

  • What is the AENET Public API?
  • What public endpoints are available?
  • What API version is in use?
  • Is the AENET API read-only?
  • How does the early access API work?

Evidence

Verified states only — nothing on this page is a prediction.

  • api/public-api-contract.json
  • contracts/openapi.public.json
  • server/routes/api-v1.js
  • docs/PUBLIC_API.md

Next step