TAC API governed beta

Inspect the OpenAPI contract before an AI workflow reads voice memory.

TAC's REST API exposes recordings, transcripts, summaries, collections, search, and governance decision receipts behind the same approval boundaries used by the MCP and CLI beta.

Copy API commands Review governance flow

Remote OAuth MCP is not enabled yet. Use approved TAC tokens and signed-in session headers only; do not send school, student, or private user data to unapproved clients.

Talk and Comment voice feedback interface preview

$ curl https://talkandcomment.com/api/v1/openapi.json
{
  "openapi": "3.1.0",
  "paths": {
    "/api/v1/recordings/search": {},
    "/api/v1/governance/evaluate_intent": {}
  }
}

Contract first

Start with the live OpenAPI shape.

The contract documents the governed REST paths, auth transports, request schemas, and decision receipt objects. Use it to generate clients or validate an agent plan before touching live TAC data.

1. Inspect

Fetch the JSON contract

This request is public contract inspection only. Staging may challenge unauthenticated page fetches, so local specs and deployed health remain the release proof for API shape.

curl -fsS https://talkandcomment.com/api/v1/openapi.json | jq '.paths | keys'

2. Prepare

Use bearer token plus session headers

Recording and collection reads require an approved TAC API token and signed-in user session headers so requests stay scoped to the user's own library.

export TAC_API_TOKEN="approved-token"
export TAC_ACCESS_TOKEN="signed-in-access-token"
export TAC_CLIENT="signed-in-client"
export TAC_UID="[email protected]"
export TAC_USER_HASH="user-hash"

Current paths

Voice-memory reads plus governance receipts.

/api/v1/recordings

List recordings

Owner-scoped recording metadata with session and TAC API token auth.

/api/v1/recordings/search

Search recordings

Search across recording title, transcript, summary, and collection caption.

/api/v1/recordings/:uid/transcript

Read transcripts

Fetch transcript content for an owned recording with governance context in district mode.

/api/v1/collections

List collections

Expose owned collection metadata for MCP, CLI, and approved REST clients.

/api/v1/governance/evaluate_intent

Persist decisions

Evaluate access intent and receive a decision receipt for governed work.

/api/v1/governance/decisions

Audit receipts

Query recent governance decisions by tenant, artifact, agent, or state.

Governance context

District mode fails closed when access intent is missing.

Governed REST reads accept governance_context. In district mode, missing or denied context returns a governance error instead of silently exposing transcripts, summaries, collection recordings, or search results.

Write and export paths use persisted decision_id receipts when district mode is enabled.

Copyable request

Search with explicit access intent

curl -fsS "https://talkandcomment.com/api/v1/recordings/search" \
  -H "Authorization: Bearer $TAC_API_TOKEN" \
  -H "access-token: $TAC_ACCESS_TOKEN" \
  -H "client: $TAC_CLIENT" \
  -H "uid: $TAC_UID" \
  --get \
  --data-urlencode "user_hash=$TAC_USER_HASH" \
  --data-urlencode "q=revision feedback" \
  --data-urlencode "governance_context[resource_id]=api.tac.recordings.search.v1" \
  --data-urlencode "governance_context[agent_id]=ag.openai.codex.local" \
  --data-urlencode "governance_context[sponsoring_human_id]=usr.teacher.demo" \
  --data-urlencode "governance_context[purpose_statement]=Review approved voice notes before drafting teacher feedback." \
  --data-urlencode "governance_context[record_scope]=single" \
  --data-urlencode "governance_context[field_scope]=profile-based" \
  --data-urlencode "governance_context[cadence]=one-time" \
  --data-urlencode "governance_context[effect]=view-only" \
  --data-urlencode "governance_context[autonomy_mode]=human-approved" \
  --data-urlencode "governance_context[retention]=ephemeral" \
  --data-urlencode "governance_context[downstream_sharing]=none" \
  --data-urlencode "governance_context[human_review_point]=teacher_before_send"

Now

Governed local/public REST contract

OpenAPI JSON for governance, recordings, summaries, transcripts, search, and collections.
Session-scoped recording reads with TAC API token compatibility.
Decision receipt persistence and audit queries for governed workflows.

Not yet

Broader productization

No broad OAuth remote MCP claim until the approved auth path is live.
No public API-token creation UI claim until account-level token issuance ships.
No school or student data should enter unapproved AI clients or external providers.

Building an approved voice-memory workflow?

Use REST for governed API clients, MCP for local AI clients, and CLI checks for setup automation.

Open OpenAPI JSON Use MCP setup Use CLI checks