Skip to main content
Single entry point for data loading. Flat kwargs, local-first by default, scheme routing for cloud and SQL sources.

Signature

Parameters

Source resolution

A scheme in name always wins over source=:

Return types

Missing backends raise CirronDependencyError with an install hint.

match= shapes

map= shapes

Size guardrails

Before downloading anything, ci.load() sums the matched bytes and applies the tier policy configured on the Cirron instance: SQL sources opt out because they can’t estimate size before executing. Use LIMIT to bound result size.

SQL credential resolution

First match wins:
  1. URI inline: postgres://user:pass@host/db
  2. Platform integrations: GET /api/integrations/resolve with a scoped, short-lived token (requires a configured Cirron integration)
  3. ci.secret("<scheme>-<host>"): platform-mounted secret
  4. Driver env var: PGPASSWORD / MYSQL_PWD / SNOWFLAKE_PASSWORD / DATABRICKS_TOKEN

Examples

Errors

Not yet shipped

search= and top_k= (semantic search over a platform vector index) accept input for API stability but raise NotImplementedError until the backend ships.

Data loading guide

Narrative walk-through with more examples.

Errors

Exception hierarchy for the data loader.