Attribution
Intelligence flow
Inspect account-scoped feed contributions by transport, agent, and self-reported skill.
GET
Account-scoped feed contribution paths with transport and self-reported skills
Requires
read:intel. The account comes from your authenticated credentials.
window_days defaults to 30 and accepts 1–90. Optional feed_id restricts both
contributions and unique recorded answers to that feed. since is inclusive;
until is exclusive.
Counts and coverage
Eachpaths entry describes a feed, transport, agent identity, and optional skill.
contributions counts one response once per contributing feed. A response supported
by two feeds contributes twice across the full flow. unique_answers counts recorded
response IDs; it is not a count of investigations, agent-written reports, or confirmed
detections. Responses without recorded feeds appear in answers_without_feeds.
These records cover captured attribution, not necessarily all account activity.
transport is mcp, rest, or unknown. Historical missing metadata and unverified
transport both appear as unknown; the dashboard labels this combined category
API/MCP, without claiming which transport was used. Skill IDs and versions are
self-reported. Missing skill metadata stays null.
Agent identity and API-key fallback
Explicit agent IDs, connection identities, and caller-reported agent names take precedence. When a record only identifies a principal or has no agent identity, the flow can recover the API key from the matching account-scoped usage request:agent_key_type: "api_key"meansagent_keyis the immutable API key ID.api_key_nameis the key’s current display name, or null when unavailable.api_key_revokedis true when the recovered key ID has no matching key row, false when the row exists, and null for identities that are not API-key fallbacks.- Renaming a key changes the name displayed for historical activity. This field is not a snapshot of its name at request time.
- Duplicate names remain separate because grouping uses key IDs. A shared key identifies a credential, not necessarily one agent.
- Missing usage records or null key IDs cannot be used to recover a key. Raw principal IDs can remain in the API response; the dashboard displays Agent not identified instead.
api_key_revoked is
true, display Revoked API key and reveal the key ID on hover. Missing key names
alone do not establish revocation. Keep IDs accessible to disambiguate duplicate
labels. Both key metadata fields are additive; tolerate them being absent on
earlier API versions without treating an absent revocation flag as proof of revocation.
Partial results
At most 5,000 paths are returned. Ifcomplete is false, use
displayed_contributions for rendered path totals and report omitted_contributions.
total_contributions covers the complete selection. A feed filter recomputes the
selection rather than merely hiding other paths.
unknown_transport_contributions and unreported_skill_contributions describe
metadata coverage. Database failures return unavailable responses rather than
successful zero counts.Query Parameters
Response
Successful Response
Account-scoped feed contribution paths with transport and self-reported skills
.png?fit=max&auto=format&n=u7saXgSwhIjXsY7P&q=85&s=66da6f97e851defcb12af05b800a8a27)
.png?fit=max&auto=format&n=u7saXgSwhIjXsY7P&q=85&s=37df025ce7a3cc54dd90f8edad1cf54f)