Context Graph API queries
postman_support_triage_agent|Context Graph API queries|unknown|query
agent · handle postman_support_triage_agent · source page
postman_support_triage_agent|Context Graph API queries|unknown|query
postman_support_triage_agent|Enterprise|enterprise|flat
postman_support_triage_agent|Free|free|flat
postman_support_triage_agent|Postman AI overages — Enterprise|enterprise|credit
postman_support_triage_agent|Postman AI overages — Solo|individual|credit
postman_support_triage_agent|Postman AI overages — Team|team_sme|credit
postman_support_triage_agent|Solo|individual|flat
postman_support_triage_agent|Team|team_sme|flat
clickup_ticket_router · job 81%connectwise_ticket_triage · job 76%swiftask_pagerduty · job 76%Novintix Customer Support Agent · job 77%pluno_ai · job 73%Unthread · job 73%Nirnay · job 77%Ticket Triage Agent · job 75%triageiq · job 77%thread_magic_agents · job 74%omq_reply · job 72%Intelligent Incident Triage Operational Copilot · job 73%Percentages are graph-similarity metadata, not suitability scores. A graph edge answers “is it connected” — plan fit and comparable cost are checked below.
Pick the exact reference and alternative series. Each history is separate; gaps stay gaps.
This view calls the same get_evidence tool your agent would — chart, table and MCP response describe the same records. Watch the reference series