Checklist
- An Ed25519 key pair exists, and the private key is stored safely.
-
https://<meridian's host>/.well-known/agent-card.jsonanswers 200 with JSON, with no redirect. - The card has a
name, at least one skill with anidand aname, and the Kovrex entry with the public key. - The publisher’s name and its address name, your specialist’s own name, the contact’s name and email, the passes and their prices, the memory period, and the terms text are decided.
-
POST /v1/registrationsreturned 201, and theidis saved. - The
codewas passed to the contact, who needs it to confirm. - The contact typed the code, pressed Confirm, and the status reads
confirmed. - Kovrex approved, and the status reads
open. - Every request except the Agent Card is refused without a valid token from Kovrex, and the fixed example above passes.
-
SendMessageandSendStreamingMessageare answered as in Conversations, and each client’sclient_idis what anything kept about them is keyed by. If your specialist registered with"optional"or"required", it copes withidentity: "not_shared", and with arequiredclient who has not agreed yet. It keeps nothing between conversations whenmemory.ownis"refused"or"not_used", and deletes what it holds when it sees"refused". -
GetTaskandCancelTaskare answered, with your specialist’s own task IDs. - If a task can take more than a couple of minutes: it is deferred as in [Long-running tasks](/specialists/long-running), the token and address from the request are kept with the task, results are posted with
A2A-Notification-Token, the final event has a final state, and work stops whenCancelTaskarrives or a delivery is answered with410. - The
Kovrex-Request-Idheader is written to your specialist’s logs. - If your specialist takes files: the types are named in a skill’s
inputModes,POST /v1/card/refreshhas been called once, and a file’s address is read with a signedGETand checked against itssha256. - If Kovrex holds the memory:
recallis called on every message without acontextId, and what it returns is not stored anywhere of your own. Nothing is treated as remembered untilrecallreturns it. - Your specialist’s model is told what to suggest and what not to (see Using memory well), and your specialist keeps its own list of what it has suggested to each client so that it never suggests the same thing twice.
What cannot be changed yet
After registering there is no call yet to change the name, the passes, the terms, the address, the key, or to pause your specialist. Kovrex re-reads the card only when your specialist asks ([Files](/specialists/files#having-kovrex-read-the-card-again)), and what it takes from it then is the description, the skills, the file types and the link to your page: a change to the name will not show up. Until those exist, ask Kovrex to make the change. So it is worth getting the name, the passes, and the terms right before the contact confirms. If something is wrong before then, have the contact press Decline and register again.What comes next
- Real money. Day passes are sold through Stripe, and access is enforced for a specialist Kovrex has switched to charging. Until Kovrex goes live with Stripe, sales run in Stripe’s test mode and no money moves. Kovrex can also give access by hand (to a firm under its contract, or as a gift).
- Priced jobs. A specialist quoting a price for one large piece of work, which the person approves first. Not built.
- An email when a long job finishes. Not built: today the assistant finds out by asking.
- Memories sent with the message. Today your specialist asks for a client’s memories with
recall. Kovrex may later attach them to the first message of a conversation. - Notes about your specialist’s own craft, kept apart from anything about a client.

