← Receivers

rag:connect

rag family

Register a knowledge source (e.g. a Google Drive folder) to sync into a workspace brain. Records the source in workspace_settings.sources; ingest-tick pulls changes on a schedule. Provision the brain (brain:provision) first.

Effect
ask
Awaits an outcome — the call returns the response below.
Caller
write_corpus
The class of authority the caller must already hold, decided from the attested context with no round trip.
Cost
1 credits
What one call costs, so you can budget before acting.
Reversible
yes
The effect can be undone by a later call.
Idempotent
yes
Safe to retry as-is.

Send it with your agent

One click hands your coding agent a prompt that registers the substrate, reads this contract, and makes the call. Launch opens the app; the others copy the prompt.

Claude Code
Codex
Cursor
Gemini CLI
Claude Desktop
ChatGPT
curl -X POST https://one.ie/api/ask/rag:connect \
  -H "Authorization: Bearer $ONE_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"data": { "folder_id": <string> }}'

The key is never in a link. npx -y @oneie/cli login writes it to ~/.config/oneie/key on your machine.

Request

Validated before dispatch — an invalid payload is refused with the fix, never half-applied.

  • provider google-drive optional
  • folder_id string required Drive folder id to sync (read-only).
  • corpus string optional Target brain @-pointer; defaults to your workspace brain @<slug>-brain. Authority-walked (write_corpus).

Response

What comes back from the call.

  • ok boolean
  • corpus string
  • provider string
  • folder_id string
  • sources number Count of registered sources after this connect.
  • reason string

Traffic

Every call to rag:connect, counted where it is dispatched — over HTTP or in-process alike. Aggregate only — no actor, no payload, no workspace.

Counting…

Wiring

Every place in the open source that names rag:connect, and the file that answers it. Read from the tree at build time — a receiver is reached by NAME through one door, so there is no import edge to follow and a grep is the honest shape of the question. Structure, not volume — the count is in Traffic above.

Called from

No caller in this repo. It is reached from outside — an agent, your code, or an MCP client.

Answered by

rag:connect one.ie/web/src/lib/resolvers/rag.ts:490 Dispatched through POST /api/ask/rag:connect, after the envelope validates the payload.
JSON Schema
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "provider": {
      "default": "google-drive",
      "type": "string",
      "enum": [
        "google-drive"
      ]
    },
    "folder_id": {
      "type": "string",
      "description": "Drive folder id to sync (read-only)."
    },
    "corpus": {
      "description": "Target brain @-pointer; defaults to your workspace brain @<slug>-brain. Authority-walked (write_corpus).",
      "type": "string"
    }
  },
  "required": [
    "folder_id"
  ]
}
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "type": "object",
  "properties": {
    "ok": {
      "type": "boolean"
    },
    "corpus": {
      "type": "string"
    },
    "provider": {
      "type": "string"
    },
    "folder_id": {
      "type": "string"
    },
    "sources": {
      "description": "Count of registered sources after this connect.",
      "type": "number"
    },
    "reason": {
      "type": "string"
    }
  },
  "required": [
    "ok"
  ]
}