{"name":"Mort","description":"Mort is an organization's analyst over its company brain — a knowledge graph continuously synced from the org's connected apps — plus live read/act access through those apps' tools. Ask it questions the way you'd ask a colleague who has read everything.","supportedInterfaces":[{"url":"https://mort-dev.noetic.net/a2a","protocolBinding":"JSONRPC","tenant":"","protocolVersion":"1.0"}],"provider":{"organization":"Noetic","url":"https://noetic.net"},"version":"0.1.0","documentationUrl":"","capabilities":{"streaming":false,"pushNotifications":false,"extensions":[],"extendedAgentCard":false},"securitySchemes":{"mort-api-key":{"scheme":{"$case":"apiKeySecurityScheme","value":{"description":"A Mort API key, minted by an operator for an existing Mort user (`pnpm --filter @mort/auth create-api-key <email>`). The agent answers AS that user, scoped to their organization.","location":"header","name":"x-api-key"}}}},"securityRequirements":[{"schemes":{"mort-api-key":{"list":[]}}}],"defaultInputModes":["text/plain"],"defaultOutputModes":["text/plain"],"skills":[{"id":"company-brain-chat","name":"Company-brain chat","description":"Answer questions about the organization by querying its knowledge graph (people, repos, issues, documents, activity and how they relate) and, where needed, reading live data through the org's connected apps. Send a message and poll the task: the answer arrives as the completed task's `response.md` text artifact. That artifact's `metadata` carries the turn's accounting — `usage` (token totals: inputTokens, outputTokens, totalTokens, cacheReadTokens, cacheWriteTokens, reasoningTokens) and `timing` (modelTimeMs, modelCalls, plus a per-call breakdown with responseTimeMs and timeToFirstOutputMs). Optionally set `metadata.mode` on the request to choose how far Mort reaches: \"quick\" answers from the knowledge graph alone and is the fastest, \"research\" also reads live through the connected apps and digs deeper (the default). It is a PER-REQUEST parameter — send it with every message, and a follow-up may switch mode mid-conversation. (`metadata` on the message itself is also accepted, but the request's own top-level `metadata` is the documented place for a parameter like this, and it wins when both are set.) Both modes are strictly read-only — this endpoint never writes to the organization's apps, so a request for Mort's write-capable \"agent\" mode is declined.","tags":["chat","knowledge-graph","analyst"],"examples":["Which repos are in the company brain?","What changed across the org this week?","Who has been working on the auth service?"],"inputModes":[],"outputModes":[],"securityRequirements":[]}],"signatures":[],"iconUrl":""}