Agentic Platform
Documentation API reference Tools Skills

Tools

Agentic Catalog Sources

agentic_catalog_sources MCP

List the AgenticCatalog sources of a project

List every source configured on a project's AgenticCatalog, with its name, description, config, and destinations. Call this BEFORE any query about an AgenticCatalog table when the user has not named a source. Those tables (`agentic_catalog_sources_pull`, `agentic_catalog_destinations_push`, `agentic_catalog_source_<source>_v<version>`) hold every source of the project mixed together, so an organization and project alone do not identify what to read -- and picking a source yourself silently answers a different question than the one asked. If this returns more than one source, ASK THE USER which one they mean rather than choosing. If it returns exactly one, use it. `id` is the `source_id` filter; `destinations[].type` is the `destination` filter on the push table. Do not invent a destination that is not listed. This is the authoritative list. Do NOT substitute `SELECT DISTINCT source_id` on a BigQuery table: that only sees sources which have landed a pull, so it omits sources that are configured but never pulled, and sources whose pulls are not reaching BigQuery. Listing is all this tool does. Once you have the source, answer the actual question with the `tables_*` tools, filtering on `source_id`.

Playground

Your organization, project and token stay in this browser's local storage and are sent straight to the API — this page never sees them.

POST
item

No fields.

Billing

Fixed cost per item requested. This tool reads data Botify already holds for your project and calls no outside service, so nothing is added to the per-call price.

These usage SKUs can be charged on a call.

SKU Credits Description
Tool call 1 per request Charged once per successful item.

Schemas

item is what you send, config how the tool behaves, and the response is what you get back.

Item

object
Example
{}

Response

object
Properties
sources array required

Every source configured on the project, pulled or not. `id` is what to filter `source_id` on in the AgenticCatalog BigQuery tables; `destinations[].type` is what to filter `destination` on. Empty means the project has no AgenticCatalog.

Items: AgenticCatalogSource

Example
{
  "sources": [
    {
      "id": "string",
      "name": "string",
      "description": "string",
      "config": {},
      "destinations": [
        {
          "type": "string",
          "name": "string",
          "config": {}
        }
      ]
    }
  ]
}

Type Definitions

2 types

These are the available sub-object types that can be used in the properties above.

AgenticCatalogDestination object
#

One destination configured on an AgenticCatalog source.

type string required

Destination type. Filter `destination` on this value in `agentic_catalog_destinations_push`. `dummy` is a no-op and never appears in that table.

name string required

Human-readable destination name.

config object required

Destination settings (credentials are masked).

AgenticCatalogSource object
#

One AgenticCatalog source configured on the project.

id string required

Source identifier. Filter `source_id` on this value in the AgenticCatalog BigQuery tables.

name string required

Human-readable source name.

description string required

Optional source description.

config object required

Source-level settings (datasource, enrichment, language, ...). Secrets are masked.

destinations array required

Destinations this source is configured to push to.

Items: AgenticCatalogDestination

Endpoints

POST http://agents.botify.com/{organization}/{project}/agentic_catalog_sources/process
POST http://agents.botify.com/{organization}/{project}/agentic_catalog_sources/batch_process
POST http://agents.botify.com/{organization}/{project}/agentic_catalog_sources/async_process
POST http://agents.botify.com/{organization}/{project}/agentic_catalog_sources/async_batch_process

See running a long job in the background for the polling flow.

cURL

curl -X POST "http://agents.botify.com/{organization}/{project}/agentic_catalog_sources/process" \
  -H "Authorization: Bearer $BOTIFY_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
  "item": {}
}'

Over MCP

This tool is exposed as the MCP tool agentic_catalog_sources. An MCP client passes organization, project and item as tool arguments. Set up MCP →

Raw metadata