Protocols and platform services

Neuron is a multi-protocol server. The Agent API is one integration surface, not the whole platform.

Need	Interface	Default resource/transport
Server-side account, identity, contract, wallet, or token workflow	Agent API	`/Agent/...` over HTTPS
Give an AI agent tools and resources	MCP	`/MCP...` over HTTPS + OAuth
Real-time federated messaging and IoT	XMPP	C2S/S2S, WebSocket, or BOSH bindings
Standards-based authorization	OAuth 2	`/oauth/...`
Decouple producers and consumers	Queue API	`/Queues/{queue}`
Query semantic data	SPARQL	`/sparql`
Read/write RDF graphs	Graph Store Protocol	`/rdf-graph-store`
Generate and serve rich content	Markdown/Script/content pipeline	Hosted resources and packages
Controlled outbound HTTP access	HTTP Proxy or Content MCP	`/HttpProxy` or `/MCP/Content`
Publish an open XMPP node to web readers	Public PubSub	`/PubSub/{nodeId}` RSS/XML
Exchange scannable platform actions	QR and URI services	`/QR/...` plus typed URI schemes

Choose a protocol

Use XMPP when the interaction is real-time, federated, presence-aware, or device-oriented.
Use Agent API when a trusted back end wants Neuron domain operations without maintaining XMPP state.
Use MCP when an AI client needs discoverable, individually authorized tools.
Use queues when a producer should not wait for a consumer.
Use SPARQL/RDF when data semantics and graph relationships are the interface.
Use packages and native modules for code that must run inside the Neuron.

All public interfaces require an explicit authentication, authorization, data-protection, retry, and audit design.