Entities with provenance
Registry records connect an entity to its publisher and identity. Version information makes the object you discovered distinguishable from a later revision.
MARS is the federated registry for agents, tools, models, datasets, and services. Discover a capability, inspect its publisher, and follow its provenance.
Independent projects, connected around a shared task.
A name alone says little about a tool or model. A registry entry gives it an identity, version, publisher, and supporting attestations. MARS organizes those records so applications can discover and inspect the things they use.
Registry records connect an entity to its publisher and identity. Version information makes the object you discovered distinguishable from a later revision.
MARS-QL provides a query language for registry discovery. Applications can search by entity properties and inspect the surrounding identity and attestation context.
Registry operators exchange information through the federation protocol. An integration should understand its registry’s publishing, resolution, and synchronization behavior.
Registry documents and on-chain commitments serve different purposes. Use the relevant supported Sigil anchor path; a MARS operation is not automatically a transaction the chain accepts.
Find an entry that describes the capability you need.
Check the publisher, version, document, and attestations relevant to your decision.
Use the entry’s interfaces and keep the version and provenance with your application record.