Connection and request security

Owners and admins manage source connections and provider credentials. Members can use configured sources and documents but cannot replace connection keys.

1. Select your project and save the vector-store connection details.
2. Save the credential. The application shows whether a key is configured; it never displays the saved key.
3. Supply a credential again after changing the URL, table, index, namespace, or collection. Then test or initialize the new connection.
4. Start OAuth connections from Sources. Links expire after ten minutes, can be used once, and require the browser that started the connection.

The hosted application blocks connections to private and reserved networks. Website discovery accepts at most 100 pages. Search/chat questions support 8,000 characters, and chat output supports up to 8,192 tokens.

Per-minute organization budgets are 60 searches, 20 chats, 30 sync starts, 5 website discoveries and 10 OAuth starts. A busy organization receives a retry hint; wait before trying again.

If an auto-recharge payment remains pending, contact support for reconciliation before attempting another payment. AppSumo activation is currently unavailable.

Syncs reserve credits before embedding, context generation, and vector writes: the cost leaves your balance when the sync starts and appears as a Sync transaction. If the sync fails, the same amount returns as a Refund transaction, so a retry costs nothing extra. An organization can have five active syncs, with one active sync per document. A failed sync refunds the original startup and purchased credit pools once, including a failure during vector writes; the next sync replaces any partial vectors. A sync interrupted before it settles (for example by a timeout) is refunded automatically about an hour after it started. Documents are limited to 25 MiB of extracted text and 1,000 chunks. Remote document parsing happens before this reservation; its provider-side cost and extraction limits still need separate monitoring.