API

Keys, permissions and the endpoints for reading, asking and adding.

Keys

In Settings, API keys, make a key with a name and exactly the permissions it needs. A key can expire, can be limited to addresses, is rate limited, and keeps an activity log. The secret is shown once.

requests

See request titles, statuses, tags, release notes and counts of quotes, people and accounts.

quotes

Also see the exact quotes, and search them by meaning.

ask

Ask questions; answers cite stored quotes.

submit

Add notes and call transcripts to the review queue.

write

Change a request's status (never into or out of shipped) and add tags.

Keys never expose people's names or email addresses. New keys can read but change nothing unless you tick more.

Endpoints

GET  /v1/ext/requests?q=&statusId=&tagId=&limit=   list, most valuable first
GET  /v1/ext/requests/{id}                         one request, with quotes if permitted
GET  /v1/ext/statuses                              the statuses
GET  /v1/ext/tags                                  the tags
GET  /v1/ext/release-notes                         published notes
GET  /v1/ext/quotes/search?q=                      quotes by meaning
POST /v1/ext/ask            {"question": "…"}      a cited answer or "no evidence"
POST /v1/ext/feedback       {"text": "…", …}       a note for the review queue
POST /v1/ext/transcripts    {"transcript": "…", …} a call transcript
PUT  /v1/ext/requests/{id}/status {"statusId": …}  change status
POST /v1/ext/requests/{id}/tags   {"tagId": …}     add a tag

Send the key as Authorization: Bearer …. The full contract is an OpenAPI document. Limits: 120 requests a minute per key; 500 notes a day. Quotes that look like instructions to an AI are flagged in the response so your code can withhold them.