Skip to main content
Your application connects to the Agent API, an HTTPS interface exposed by the Neuron that hosts its account. The Neuron coordinates the enabled identity, contract, token, payment, and messaging services.

​
Application responsibilities

Your application manages credentials, requests, user review, returned identifiers, and business logic. The Neuron executes the operations exposed through the API. Its provider controls enabled capabilities and trust relationships. For browser applications, keep privileged credentials in your backend. The application architecture guide and application guide show this arrangement.

​
Objects and their dependencies

A contract signature relates a Legal Identity to a role in an agreement. A token refers to its creation contract and may have a state machine. A payment has its own transaction outcome. These are related objects with distinct lifecycles. Read the object model to decide which identifiers and states to persist. Do not infer completed business activity from HTTP success alone.

​
Trust across domains

Different participants can belong to different Neurons. Cross-domain interactions depend on the configured trust services and permissions. The trust and federation concepts explain what this means for applications. Continue with your first API request or choose a build task.