The live dacs-auditor listing artifact carries no publicEndpoint and no structured pricing (price appears as free-text inside description only). An automated client reading the artifact alone cannot locate the RFQ / negotiation channel or determine the price band.
Observed on-chain. The auditor listing (dacs1:listing:did:demos:agent:568b74e67166d27853f29309d6561888d58b4408cca105290c3fe55e2fad5cec:audit-negotiator) exposes top-level keys {name, agentId, serviceId, signature, description, claimRequirements, supportedDelivery, supportedNegotiation, supportedPaymentRails} — there is no publicEndpoint, and pricing appears only as prose in description ("negotiated per job (RFQ)… Deep tier cost basis: 3 DEM base + 2 DEM per tool + 0.5 DEM per KLOC").
Contrast (current-profile). A current DACS-1 listing exposes a structured shape — e.g. dacs1:listing:lst-practice-dacs-0001 carries offering, pricing, pipeline, acceptedRails, buyerRequirement, validity — from which a client can extract the RFQ channel and price band directly.
Ask: populate publicEndpoint and structured pricing on the auditor listing (or document why free-text is intended), so automated discovery / quoting works from the artifact alone.
The live
dacs-auditorlisting artifact carries nopublicEndpointand no structured pricing (price appears as free-text insidedescriptiononly). An automated client reading the artifact alone cannot locate the RFQ / negotiation channel or determine the price band.Observed on-chain. The auditor listing (
dacs1:listing:did:demos:agent:568b74e67166d27853f29309d6561888d58b4408cca105290c3fe55e2fad5cec:audit-negotiator) exposes top-level keys{name, agentId, serviceId, signature, description, claimRequirements, supportedDelivery, supportedNegotiation, supportedPaymentRails}— there is nopublicEndpoint, and pricing appears only as prose indescription("negotiated per job (RFQ)… Deep tier cost basis: 3 DEM base + 2 DEM per tool + 0.5 DEM per KLOC").Contrast (current-profile). A current DACS-1 listing exposes a structured shape — e.g.
dacs1:listing:lst-practice-dacs-0001carriesoffering,pricing,pipeline,acceptedRails,buyerRequirement,validity— from which a client can extract the RFQ channel and price band directly.Ask: populate
publicEndpointand structuredpricingon the auditor listing (or document why free-text is intended), so automated discovery / quoting works from the artifact alone.