Skip to main content

data_public — Public data

Knowledge sources the agent may quote and surface to power-users — public files and URLs. Section key data_public · Shape object · Tier All plans
Edit in the dashboard: Public Data page

Fields

files items

Uploaded documents processed for retrieval-augmented generation.

urls items

Array of URL sources to fetch and index for RAG. Each URL is polled, converted to chunks, and indexed into the same hybrid keyword + semantic retrieval index as public files. Supports optional bearer-token auth for protected endpoints.

external_stores items

External knowledge sources the agent should query at chat time alongside the agent’s built-in knowledge base. Each entry is a connection to YOUR existing store — a Pinecone or Weaviate cluster, Bedrock KB, Azure AI Search, Vertex AI Search, OpenAI Vector Store, or a GitHub-hosted Obsidian vault — Agentheya does not ingest into it, only queries. Hits are merged with built-in retrieval results. Credentials (api_key fields) are encrypted at rest.

service_sources items

Configured SaaS service data sources (Services card). Each pulls documents/records through a connector added on the /connectors page and ingests them into this scope’s retrieval index. Sync-state fields (last_synced_at, last_sync_status, last_sync_error, item_count) are server-stamped and never trusted from clients.

files.chunking_config fields

Configuration object controlling how the file is split into chunks for RAG retrieval. Passed to the ingest pipeline; controls chunk size, overlap, strategy, metadata stamping, and contextual enrichment.

files.doc_profile fields

LLM-generated knowledge profile written by the ingest pipeline (not owner-editable): what the document is about + topic keywords. Feeds the agent’s document catalog so it can route to the right document.

service_sources.custom fields

Owner-authored field mapping when service === ‘custom’ (build-your-own connector).

service_sources.s3 fields

Direct S3 / S3-compatible bucket config (connector_kind ‘s3’). secret_access_key is encrypted at rest and read back as ‘REDACTED’.