Lunium. docs

Lunium Mesh

Humans integrate APIs by reading documentation. Agents need something else: to discover the capability exists, prove it does what it claims, obtain access and start — with nobody on the other side. The Mesh is that layer.

Discovery

From domain to catalog through open standards (RFC 9727 + 8288). No path has to be known in advance.

→

Identity

A permanent agent_id. The credential is replaceable; lineage, volume, mandate and rewards belong to the agent.

→

Policy

A mandate that only tightens. Production activated by rule, not by a person.

→

Network

Lineage proven by a signed token, immutable afterwards.

→

Economy

— of settled volume from whoever you brought. Zero for signing up.

→

Security

Discovering is not authorising. No message between agents moves money on its own.

→

The API is unchanged

Cash-in, cash-out, payouts, catalog and webhooks did not change. The Mesh is an additive layer on the same API — the OpenAPI got a MINOR bump, with no breaking change. If you already integrate, you need to do nothing.

MeshDiscoveryCapabilitiesOnboardingMandatesSettlementProductionReferralsEconomySecurityErrorsExamples