Describe a source's full live query surface
Return the source’s capability manifest: capabilities, the raw read surface, and guidance — what the caller can compose a query against.
Authorizations
API Key or JWT User Token. If using an API Key, set the X-As-User header to act as a specific user. A JWT User Token is always scoped to a specific user.
Path Parameters
reddit, notion, slack, google_calendar, google_mail, box, dropbox, github, google_drive, vault, web_crawler, trace, microsoft_teams, gmail_actions, granola, fathom, fireflies, linear, hubspot, salesforce, coda, lightfield Query Parameters
Specific connection id.
Response
Successful Response
Everything the caller can ask of a source — read before composing a query.
reddit, notion, slack, google_calendar, google_mail, box, dropbox, github, google_drive, vault, web_crawler, trace, microsoft_teams, gmail_actions, granola, fathom, fireflies, linear, hubspot, salesforce, coda, lightfield nango, unified, whitelabel Live-access capabilities an integration may implement.
Used by LiveSourceAccess (and its LLM/HTTP surfaces) to advertise what a connected source can do on-demand. LIST_RESOURCES / FETCH_RESOURCE / SEARCH_LIVE are detected via method-override introspection (see Integration.supports), so they reflect reality with no per-integration declaration to keep in sync.
PASSTHROUGH is the exception: it is declared (via live_raw_read_ops),
not introspected — see specs/components/live-query-framework.md. A source
supports it when it exposes a non-empty raw read surface (the agent composes
raw provider reads against it).
list_resources, fetch_resource, search_live, passthrough, resolve, query_structured