> Source: https://vitna.ai/docs/api/v1/prices/terms
> Raw Markdown: https://vitna.ai/docs/api/v1/prices/terms.md
> Corpus index: https://vitna.ai/llms.txt
# Provider terms
What providers have published on their own domains about how they handle customer work: retention, training use, processing regions, and bring-your-own-key support. The read surface for [provider terms](../../../concepts/provider-term.md).
```
GET /api/v1/terms
GET /api/v1/providers/{id}/terms
```
```bash
curl https://vitna.ai/api/v1/terms
curl "https://vitna.ai/api/v1/terms?provider=anthropic&kind=zero_retention"
curl https://vitna.ai/api/v1/providers/openai/terms
```
## Response
```json
{
"standing": [
{
"id": 5,
"providerId": "openai",
"provider": "OpenAI",
"kind": "zero_retention",
"value": "no",
"observedOn": "2026-08-01",
"sourceUrl": "https://openai.com/enterprise-privacy",
"sourceVerifiedOn": "2026-08-01",
"note": null,
"summary": "retains prompts or responses, as read on 2026-08-01"
}
],
"terms": [
{
"id": 5,
"providerId": "openai",
"provider": "OpenAI",
"kind": "zero_retention",
"value": "no",
"observedOn": "2026-08-01",
"sourceUrl": "https://openai.com/enterprise-privacy",
"sourceVerifiedOn": "2026-08-01",
"note": null,
"summary": "retains prompts or responses, as read on 2026-08-01"
}
],
"kinds": {
"zero_retention": "whether the provider retains prompts or responses after answering",
"no_training": "whether the provider trains on customer data",
"regions": "which regions the work is processed in",
"byok": "whether the provider accepts a key the customer holds"
},
"meta": {
"generatedAt": "2026-09-12T09:14:02.881Z",
"source": "database",
"count": 4,
"standingCount": 3
}
}
```
## Standing vs history
`witness.provider_term` is append-only: when a provider changes its retention or training policy, a new row is recorded and the earlier row remains so older decisions still resolve against what stood on the day they were made.
- `standing` holds the newest reading (`observedOn`) for each `(providerId, kind)` pair, which is what the engine's eligibility check reads today.
- `terms` holds every recorded reading matching the filter, newest first.
When served from the committed snapshot with no database connection, `standing` and `terms` are `null` with an explanatory `note` rather than `[]`, so an offline checkout never implies that the record holds zero terms.
## Parameters
| Parameter | Values | Default |
|---|---|---|
| `provider` | Any registered provider id (for `/api/v1/terms`) | All providers |
| `kind` | `zero_retention`, `no_training`, `regions`, `byok` | All four kinds |
An unknown provider answers `404 unknown_provider`; an unknown kind answers `400 bad_term_kind`. Both are validated before touching the database.
## Caching
`public, max-age=60, stale-while-revalidate=3600`.