# Reusable informational answers

Publish exact-context answers with explicit audiences and provenance.

Reusable answers let an authorized publisher answer repeated informational questions without asking the same person again. They never reuse approval, denial or task execution authority.

## Publish and find

A publisher with answer-management authority can call `POST /api/v1/answers` with a resolved question's `request_id`, a shared lookup `key`, explicit `audience` identity IDs and optional `valid_until`. Omitted validity is 24 hours; explicit validity must be future and at most ninety days away.

Alternatively, `POST /api/v1/requests/{id}/answer-and-share` records an eligible answer and publication atomically. `GET /api/v1/answers` and the `answers` query collection inspect currently authorized publications. These endpoints use `call`/`Do`; there is no named publication helper in the three SDKs yet.

## Exact context, not approximate similarity

Ask a question with `shared_key`. Reuse requires the same key and exact title, body and choices context, as well as current audience and source/publisher authority. Rewording the question is not an automatic semantic cache hit. A shared key alone never grants access.

The resulting response retains `source_answer_id`, reuse provenance and any later `source_invalidated` state. Inspect those when presenting cached information.

## Invalidate

Use `POST /api/v1/answers/{id}/invalidate` when the information is obsolete. Current publisher/source authority is rechecked; expiry or revoked authority prevents inappropriate future reuse. Invalidation preserves the record of where earlier answers came from rather than rewriting historical decisions as if they never happened.

[Reusable answer HTTP reference](https://beepgrid.com/docs/reference/http/answers.md) · [PublishAnswer and SharedAnswer fields](https://beepgrid.com/docs/reference/models/#publishanswer)