Community-contributed tools, reference implementations, integrations, and apps built on the DACS agent-commerce standard.
DACS specifies the agent commerce lifecycle — Identify → Vet → Negotiate → Settle → Verify — as one standard per stage. This repo is where the ecosystem around the standard lives: implementations that exercise it, tools that make building against it easier, and integrations that connect it to other stacks.
Nothing in this repository is normative. The specification, conformance vectors, and CHANGELOG live in DACS-Standard; conformance is defined there and only there.
This repo operates under the model described in the standard's ROADMAP, Part 2: contributor prototypes, steward owns the standard. Community work is welcomed without ceremony, never changes the spec, and may be designated canonical by the steward if it proves solid — at which point it is marked as such in the INDEX.
| Directory | Contents |
|---|---|
reference-implementations/ |
Implementations of one or more DACS stages — full lifecycle, a single phase handler, or an application/product built on the standard |
tools/ |
Developer tooling: validators, vector runners, bundle inspectors, codegen, debugging aids |
integrations/ |
Bridges to other stacks: payment-rail adapters (x402, AP2, ERC-20/SPL), identity/vetting method providers, substrate bindings |
examples/ |
Worked end-to-end sessions, sample artifacts, tutorial material |
Projects can live in-tree (small, self-contained — vendored here under MIT) or externally (your own repo, any OSI license, listed in the INDEX). Both routes go through the same submission process.
The catalogue of all accepted submissions — in-tree and external — is INDEX.md, including each project's DACS surface (which modules/§ it touches) and its self-declared conformance status.
- Spec defects, proposals, RFCs → DACS-Standard issues / discussions
- Conformance vectors → DACS-Standard
conformance/(vectors are normative artifacts) - Security reports → see SECURITY.md
See CONTRIBUTING.md. The short version: open a PR that adds your project (in-tree) or its INDEX entry (external), with an honest declaration of what it implements and how far its conformance has been verified. Inclusion means curation, not endorsement or audit.
The repository structure and in-tree contributions are MIT. Externally-indexed projects carry their own licenses, declared in their INDEX entries.