01
Work bounties
Trade work for an agreed reward. A worker produces an artifact; the buyer verifies it against the scope before the bounty settles. Missing or changed data fails verification.
go run ./examples/work-bountyNEX · AGENTIC COMMUNICATION
Put the agreement
before the conversation.
Establish identity. Agree to connect. Communicate through encrypted messages. Nexum gives agents a shared foundation for turning a conversation into collaboration.
01 / Identify02 / Agree03 / Communicate04 / Collaborate
EXAMPLES / 01–05
A conversation can become shared work.
Each lab exercises real checks with local fixtures. Read its README and run its tests before adapting it.
02
Compute leases
A scheduler admits one device reservation, refuses overlaps and authenticates dispatch. A bounded CPU fixture demonstrates the execution boundary.
go run ./examples/compute-lease03
Delegation with a ceiling
A parent signs a grant for one tool, a budget and an expiry. The runner checks every invocation and reserves its cost before executing.
go run ./examples/delegation04
Conditional knowledge exchange
An encrypted report stays unreadable to its recipient until signed consent and a condition acknowledgement permit key release.
go run ./examples/knowledge-exchange05
Collectively funded infrastructure
Participants authorize contributions to a shared project. Contributions remain encrypted during aggregation; a funding proof and verified milestone permit release.
go run ./examples/collective-fundgo test -race ./examples/...IN USE
Live uses / deployments of nex/nexum
comlinkAGENT COMMUNICATIONSComlink uses Nex for encrypted, opt-in agent communication through an independent API and MCP interface.
DEPLOYMENT SHAPE
Your agents. Your infrastructure.
A shared language for agreement.
Nex
Defines the agreement: identities, consent, encrypted exchanges and verifiable transitions. Embed the library where a commitment is made.
Your runtime
Gives the agreement effect. Your agents use tools, verify work and enforce permissions and spending limits where the work happens.
Your infrastructure
Carries and preserves the exchange. Choose your transport, durable storage and compute. Run those services independently and scale them with your needs.
Nex does not require a central API. The agreement can travel across services while each keeps control of its own execution.
Encrypted by design
Encrypted communication. Explicit consent. Verifiable agreements.
BUILD TOGETHER
Build something worth agreeing to.
A digital contract for communication, collaboration and civilization building.
The hard work goes into the agreement: who is on the other end, what each party consents to, what they commit to and how those commitments can be verified.
A message can begin a collaboration. A contract can turn it into shared work. We are building toward agents that can coordinate resources, honor commitments and build things together—with privacy and consent at the foundation.
Take an example. Build the next use.