engman bronze
app.engmanapp.com
“engman keeps 1:1s, feedback and career plans for the people a tech leader manages. Agents read people and teams by name and id, and propose changes that the leader confirms in the web app. The demo workspace is marked "Demo workspace: invented data, reset periodically".
https://app.engmanapp.com/.well-known/agent-card.json its cardwe checked this the operator says this
Verified by agenttru.st
Everything here is a check agenttru.st performed itself. Assurance, protocol, hosting and freshness are in the card above and are not repeated.
- Certificate
-
Issued by Google Trust Services
domain-validated
Valid until 13 Jan 2027 as of our check on 14 Nov 2026.Control of the hostname was checked; nothing about who operates it.Key RSA 2048, signed SHA256-RSA, issued via WR3 under GTS Root R1 — classical, as every publicly trusted certificate is today.
Names on this certificate (1)
app.engmanapp.com. - Connection
- TLS 1.3 · X25519MLKEM768 — post-quantum hybrid key exchange, agreed with our checker on 14 Nov 2026. What this means
- DANE / TLSA
- Not verified (TLSA query returned RCodeNameError)
- Discovery
- Well-known document
- First seen
- 14 Nov 2026
View verification details
- Assurance
- bronze Bronze — agent card fetched over HTTPS with a valid certificate
- Protocols
- A2A verified by handshake or card fetch, not merely advertised
- Hosted in
- 🇺🇸 US · Google LLC (AS15169)
- Last checked
- 8h ago
What this agent says it can do
Declared in the agent's own card. agenttru.st has not tested whether it completes any of these tasks — the operator of app.engmanapp.com controls every word below.
Today's items
What waits on you today: the planned 1:1s you hold today (regular and skip-level), and for each person the open action items of the 1:1s you hold with them that were due before today, with their count and oldest due date; each direct report who joined or moved to you and has had no held regular 1:1 with you since, and each other direct report with no held regular 1:1 for more than your reminder weeks, with the date that clock started; each improvement feedback entry you own, private ones included, open or improving with no follow-up mark in your reminder weeks; and each active career plan you own, private ones included, to close or update after the person's promotion, or with no progress in your reminder weeks. Names, teams, dates and counts only; never what was said, an action item's text, feedback or a plan's content.
Get history link status
See whether a person's history page link exists, was opened (the day only) or was revoked; for their direct manager and the owner.
Get an import
Check one of your imports: its status (queued, extracting, ready or failed), how many proposals, skipped items and warnings it made, and once ready or failed the link to review its batch. Never the text.
Get the career ladder
Get the workspace's career ladder: every level with its track (shared, individual contributor or manager), position and whether it is switched on, and every discipline. Names only, in the user's language, and the success threshold: the progress at which a career plan counts as reached.
Overview of your people
A manager's Overview: yours, or that of a manager among your people (managerPersonId) exactly as they see it, with the path from you down to them. Each of the manager's direct reports who leads a team, with how many people they have, how many of them have had no 1:1 in that lead's own reminder weeks, the open and overdue action items of their 1:1s, their improvement feedback with no follow-up in those weeks, and their active career plans with how many have had no progress in those weeks; then each of the manager's direct reports by name and team, with the date of their last 1:1 held, since when they have had none once past the manager's reminder weeks, the action items of the manager's 1:1s with them, the manager's feedback about them with no follow-up, and whether the manager's career plan for them is active, stalled since a date, or missing. Never what was said, and never a plan's progress.
Get my context
Get who you are working for: the signed-in user, their workspace, the agent access level the workspace owner set, the scopes this connection was granted, after how many weeks without a 1:1 with someone the user wants to be reminded, whether they get the daily digest email, whether notes can be imported, and whether 1:1 items can be shared.
Get person
Get one person's name, work email, start date, email language, archived state, team, chain of command, pending invitation, discipline, level, track, whether they are a Tech Lead, and whether a claim about their data is in progress with its reasons (the rights it invokes).
Get proposal status
Check whether your proposals were confirmed or discarded, and the id of what each confirmed one became.
Get workspace
Get the workspace's id and name, the caller's own person and whether they own the workspace.
Import notes
Import notes the user pasted about one of their people (up to 100,000 characters): engman extracts proposed 1:1s, feedback and career plans about that person only. Nothing is saved until the user confirms them in engman; poll get_import with the returned id, then open its batch link to review them.
List career plans
List a person's career plans, newest first: type, status, target discipline and level, start, target and closed dates, progress, when progress last changed, the manager who owns it, where it came from (the app, or the agent whose proposal it was) and whether it is private (only ever for the user's own plans). Never the objectives or key results.
List connected agents
List the AI agents connected to engman: the client, who connected it, when, its last use and its reads and proposals over the last 30 days. The owner sees every one in the workspace; anyone else sees their own.
List feedback
List the feedback given to a person, newest first: date, kind (recognition or improvement), status, the manager who owns it, the 1:1 it was given in and whether it is private (only ever for the user's own entries). Never what was said.
1:1 overview of your people
For each of your people with a regular 1:1: the date of the last one held, the next one planned and how many of their action items are open. Never what was said.
List 1:1s
List a person's 1:1s, newest first: date, status, kind, who held them and how many of their action items are open and overdue. Never what was said.
List people
List the people the caller sees (themselves and everyone below them; the owner sees everyone) by name, with each one's team, direct manager, discipline, level, track, whether they are a Tech Lead, whether they have left, and whether a claim about their data is in progress with its reasons (the rights it invokes).
List teams
List the teams the caller sees (the ones they lead and every team below them) by name, each with its manager.
List a person's timeline
List everything you may see about a person, newest first, 50 at a time; types keeps only those record types, and person_change the person changes. A record entry gives its id, type, a feedback entry's kind (recognition or improvement), date, the manager who owns it and the one it last moved from, its source, whether you may read its content, whether it is private, who reads it by name and, for a departed manager's private entry, when it is deleted; a person change gives its kind, date, the teams and managers it moved between by name and, for a career change, the levels or disciplines by the names they had then, or the new Tech Lead role. While a claim about the person's data is in progress, every page says so with its reasons (the rights it invokes). Never a title, a note or what was written. For the next page, pass the nextCursor of the last one as cursor.
Propose a career plan
Propose a whole career plan for one of the user's direct reports: traditional, toward their next level, or liquid, toward the discipline and level you name (ids from get_ladder); an optional target date; objectives with key results (type, title, an optional http(s) link and due date); and prefillFromLevel to add the target level's stretch milestones, courses and suggested time when the user confirms. Nothing is saved until the user confirms it in engman, and only once any active plan they own for that person is closed; open the returned link to review it.
Propose feedback
Propose a feedback entry the user gave one of their people, dated today or earlier: recognition or a point to improve, what they said, optionally the situation, behavior and impact, the change expected (improvement only) and a 1:1 the user held with the person. Nothing is saved until the user confirms it in engman, where they may also mark it private; open the returned link to review it.
Propose a 1:1
Propose a 1:1 with one of the user's people: planned with topics, or held (dated today or earlier) with the person's answers, notes and action items. Nothing is saved until the user confirms it in engman; open the returned link to review it. A planned 1:1 starts with a template's questions, chosen by engman unless you pass templateKey: first (Get to know each other and agree on how you will work together.); regular (A weekly check-in led by what is on the person's mind.); career (Step back from the week and talk about where the person wants to grow.); skip_level (Hear first-hand from someone further down the line about their work and their team.); leader (For someone who leads a team: their team, their decisions and the support they need.); onboarding (Check in around day 30, 60 and 90 on how the person is settling in.)
Propose people
Propose 1 to 100 people to add, each by full name with an optional work email, start date, email language, and the team or manager they go under in plain words. Nothing is saved until the user confirms them in engman; open the returned links to review them.
Technical agent card
Copied from the agent's card. The operator controls these values; agenttru.st has not verified them.
- Provider
- engman — what this agent says about itself; other agents claiming the same provider are not thereby related
- Protocol
- a2a
- Version
- 1.0.0
- Auth schemes
- engman
- Extensions
-
https://engmanapp.com/a2a/extensions/skill-input-schemas/v1The JSON Schema of each skill's input, keyed by skill id. Send it as the `input` of the data part { skill, input }.A2A protocol extensions the card declares. A declared payment extension (AP2, x402) means the operator says the agent can transact, not that agenttru.st has seen it do so. - Card completeness
- complete all eight fields required by a2a.proto v1.0
View all card details
- Capabilities
- extendedAgentCard extensions pushNotifications streaming
- Agent card
- https://app.engmanapp.com/.well-known/agent-card.json
Operate this agent and would rather not be listed? Request removal.