Local apps, global network: the ANNE API

For those building on ANNE. Discuss API endpoints, integration patterns, library development, and protocol improvements. Share your projects, ask technical questions, and collaborate with other developers.
Post Reply
User avatar
radanne Verified
Site Admin
Site Admin
Posts: 28
Joined: Wed Feb 11, 2026 1:24 pm
Location: Omnipresent
Referrals: 1
Contact:

Local apps, global network: the ANNE API

Post by radanne Verified »

This board is for developers building applications on ANNE. The ANNODE exposes an HTTP/HTTPS API that local applications use to interact with the network.

The API is organized into functional categories, each accessible via endpoints under the `/anne` path. Applications communicate with the local ANNODE, which handles network interaction. Queries hit the in-memory hypergraph, data submission creates relons that propagate through consensus, and files are retrieved via parallel swarming from multiple peers.

The API documentation is available at http://localhost:9116/api-doc once your ANNODE is up and running. Existing applications can be found at http://localhost:9116/ANNE.html and http://localhost:9116/aon.html, serving a blueprint for building decentralized ecosystem.

Key endpoint categories include:

  • ANNE Hypergraph: Query and traverse the neuromorphic hypergraph. Endpoints like getAllMyStuff, queryForInstChildren, getNeuron, and lookupNid provide access to semantic data.
  • Create Transaction: Build and submit relons and payments. sendSelfRelon, sendChildRelon, makeKeylessNeuron, and sendAnne generate unsigned transactions for local signing.
  • Accounts and Balances: Retrieve account information, balances, and transaction history.
  • Blocks and Transactions: Query blockchain data, including blocks, transactions, and mempool status.
  • ANTOR: Manage file transfers, monitor active transfers, and serve files.
  • ALTDATA: Publish and retrieve application-specific payloads via the Alt Data Network.
  • A2A - Annode to annode encrypted peer-to-peer messaging.
  • Localhost only: Administrative endpoints that require local access and appropriate configuration flags.
  • Debug and Utils: Tools for development and troubleshooting, including signed/unsigned conversion and clock inspection.
The API is designed for direct use from browser-based applications. There are no API keys, rate limits, or service terms.

Topics for discussion:

  • Building applications that query the hypergraph
  • Creating and signing transactions
  • Working with relons and neurons
  • Integrating ANTOR file transfers
  • Using the Alt Data Network for application data
  • Handling encrypted messaging
  • WebSocket subscriptions for real-time updates
  • Debugging and testing against a local node
  • Performance considerations and optimization
  • Application examples and patterns

You can preview the API through our static demo at https://anne.media/anne-node-api-hyperg ... -reference. If you have questions, ask away. If you have code or patterns to share, post here.
Post Reply