Skip to main content
Capture team context DAC wouldn’t otherwise know: decisions, constraints, why-we-did-X notes. Notes are pulled into every chat as a Tribal Knowledge section and cited back in DAC’s responses. Notes you actively use stay fresh; unused notes decay.

​
List notes

curl -X GET https://app.dacard.ai/api/tribal-notes \
  -H "Authorization: Bearer $DACARD_API_KEY"

​
Create a note

curl -X POST https://app.dacard.ai/api/tribal-notes \
  -H "Authorization: Bearer $DACARD_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "productId": "prod_abc",
    "title": "We deferred SSO until Q3",
    "body": "Pushed off because two enterprise prospects explicitly said it wasn'\''t a blocker, and Onboarding ROI was higher.",
    "tags": ["security", "roadmap"]
  }'
PropertyValue
AuthRequired
IdempotentGET yes. POST no.

​
Body (POST)

FieldTypeRequiredNotes
productIdstringyesProduct the note is scoped to.
titlestringyesShort label (≤120 chars).
bodystringyesMarkdown. The model reads this verbatim.
tagsstring[]noFilter chips on the Teach DAC surface.

​
Errors

StatusCodeWhen
401AUTH_REQUIREDNo session.
403FORBIDDENCaller does not own the product.
500INTERNAL_ERRORWrite failed.