persona_identity_update
Change the agent's persona identity for the whole company. Only an administrator may. Only the fields the call names change, and names replaces the whole list. Every colleague meets the agent by these names, so put it to the requester before calling. The whole identity is answered back. `workspace_write` · approval · v1
Authorization
memberToken The tools internkim uses inside a company, callable from outside it. A token belongs to a person, and every call runs as that person, so a token can never do more than its owner can.
The first token is made signed in, from the settings screen. After that a token makes its own
successors: POST /token for a new one, DELETE /token for the old one, so a script rotates
without a browser. A token can neither mint a rung above its own nor revoke itself.
Send Authorization: Bearer <token> on every request.
In: header
Request Body
application/json
TypeScript Definitions
Use the request body type in TypeScript.
Response Body
application/json
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
text/plain
curl -X POST "https://example.com/tools/persona_identity_update/invoke" \ -H "Content-Type: application/json" \ -d '{ "input": {} }'{ "toolName": "persona_identity_update", "outcome": "succeeded", "selectedBackend": "device", "effects": [ { "objectType": "persona", "effect": "created", "id": "7a93de11-…" } ], "result": { "…": "the tool's own document" }}persona_identity_get POST
Read the agent's persona identity: every name it answers to, the first being the one it introduces itself with, and its handle, role, creature, emoji and introduction. There is one for the whole company, and any member may read it. `read` · v1
persona_profile_get POST
Read the requester's persona profile, which says how they want the agent to work with them: what to call them, what to know about them, their preferences, tone and reply language, and the daily morning briefing's time and whether it is on. It is always the requester's own. `read` · v1