clave docs

Account and platform

Who am I

GET /v1/account is the agent's whoami. One call answers identity, what the account owns, and every limit.

It reports:

PATCH /v1/account changes the name and the email address.

The email is a credential and not a label. Every sign-in link and every agent grant goes to it, so the answer says what changed rather than echo a saved field. A second account's address is a conflict.

Tokens

Call What it does
GET /v1/tokens lists every token, with when each was last used
PATCH /v1/tokens/{id} renames one
DELETE /v1/tokens/{id} revokes one at once

A chat connector's access token is an ordinary token and appears here.

Billing

Call What it does
GET /v1/billing the plan, its state and what it includes
POST /v1/billing/checkout a hosted page to start or change a plan
POST /v1/billing/portal a hosted page to manage the subscription

Both answers carry a provider's address, which is one of the two places a /v1 answer does. A payer's browser has to land on it.

Caps never come from the payment provider. They come from Clave's catalog, and GET /v1/account reports them.

Stock photos

Call What it does
POST /v1/photos/search searches the stock library

Use the id it gives with POST /v1/sites/{id}/photos to put the photo in a site. Read Site source.

A deployment with no photo key advertises no photo tools.

Design sketches

Call What it does
POST /v1/sketches hosts design directions for an owner to look at
DELETE /v1/sketches/{id} takes them down

The skill

Call What it does
GET /v1/skill the skill tree Clave serves
GET /v1/skill/{path} one file of it

Read The skill.

Feedback

POST /v1/feedback sends a note to Clave: a defect, a missing capability, a message that blamed the wrong party. Both agent surfaces write to it.

It is capped by day, and the cap is in the whoami.