Tribal notes

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"]
  }'

Property	Value
Auth	Required
Idempotent	GET yes. POST no.

Body (POST)

Field	Type	Required	Notes
`productId`	string	yes	Product the note is scoped to.
`title`	string	yes	Short label (≤120 chars).
`body`	string	yes	Markdown. The model reads this verbatim.
`tags`	string[]	no	Filter chips on the Teach DAC surface.

Errors

Status	Code	When
401	`AUTH_REQUIRED`	No session.
403	`FORBIDDEN`	Caller does not own the product.
500	`INTERNAL_ERROR`	Write failed.

Overview

Scoring

Score drilldown

Lifecycle

Products

Teams

Dashboard & Suite

Account & Team

User

Onboarding

Billing

Internal

Agents

Integrations

BYOM

Intelligence

Decisions & Briefings

Saved views

Recommendations

Credentials

Signals

Anomalies

Outcomes

Feedback

Settings

Webhooks

API Keys

Misc

System

Tribal notes

List notes

Create a note

Body (POST)

Errors

​List notes

​Create a note

​Body (POST)

​Errors

List notes

Create a note

Body (POST)

Errors