Read from a connected REST API
Issue one read request against the caller's own REST API connection. Only GET, HEAD and OPTIONS are available, so no request can change the caller's data, and no request can leave the connection's configured base URL or its allowed path prefixes. Credentials are applied from the connection (bearer, header or query API key, basic, or OAuth client credentials) and never appear in the result. Large responses are truncated with a flag.
Access
This tool reads a data source you connect. Cortexa hosts no dataset behind it and nothing here is publicly queryable — there is no result to show a visitor, only the shape of the call. Add a connection in Settings → Connections, and the agent can use it in your own sessions.
- Works with
- Scope
- One read request under the connection's base URL, size- and time-capped.
Access is read-only and re-authorized on every call against the connection's owner, your active workspace, and any explicit grants. Credentials stay encrypted at rest and are never returned by a tool.
Schema
JSON Schema the agent (or your API call) must match.
View JSON schemaExpandCollapse
Examples (1)
Illustrative only — the ids below are placeholders. Real ids come from list_connections at run time and are scoped to the caller.
Read a report from an owned API
Identifiers
- Catalog ID
- api_request
- Agent tool
- api_request
- Added
- 2026-08-12 23:08Z
- Tags
- connection, private, read-only, api, read