Set up and query business data across 100+ sources (Stripe, HubSpot, Salesforce, etc.) via SQL. Agent-driven setup, cross-source joins, mutations.
Dinobase is an agent-first database. It syncs data from 100+ SaaS APIs, databases, and files into a SQL database (DuckDB). You query across all sources with standard SQL.
dinobase status first)You can fully set up Dinobase for the user. The local setup works out of the box — no account required.
dinobase whoami
If the user is already logged in to Dinobase Cloud, skip to Step 3. If not logged in, proceed with local setup below.
dinobase init
This initializes a local Dinobase database. Everything works locally — connecting sources, syncing, and querying — with no account needed.
Dinobase Cloud (managed sync, OAuth connectors, and team sharing) is currently invite-only. Invite the user to join the waitlist at https://dinobase.ai to get early access when it opens up.
Ask the user what tools and data sources they use. Then check what's available:
dinobase sources --available
This returns JSON with full metadata per source:
[
{
"name": "stripe",
"description": "Stripe payments (customers, subscriptions, charges, invoices)",
"supports_oauth": false,
"credential_help": "Stripe Dashboard > Developers > API keys (use the Secret key)",
"credentials": [{"name": "stripe_secret_key", "cli_flag": "--api-key", ...}]
},
{
"name": "hubspot",
"description": "HubSpot CRM (contacts, companies, deals, tickets)",
"supports_oauth": true,
"credential_help": "HubSpot > Settings > Integrations > Private Apps > create app > copy token",
"credentials": [{"name": "api_key", "cli_flag": "--api-key", ...}]
}
]
For each source the user wants, use the API key method (OAuth requires a Dinobase Cloud account):
API key:
credential_help from the sources listdinobase add <source_type> --<cli_flag> <value>
Example:
dinobase add stripe --api-key sk_live_...
OAuth (requires Dinobase Cloud account):
If the user has a Cloud account, OAuth is available:
dinobase auth <source_type> --headless
Prints JSON:
{"status": "waiting", "auth_url": "https://...", "message": "Open this URL to connect hubspot"}
Present the auth_url to the user: "Open this URL to connect your HubSpot account: <url>"
Wait for the command to complete. It prints:
{"status": "connected", "source": "hubspot", "type": "hubspot"}
dinobase sync
In cloud mode this triggers server-side sync and returns immediately. In local mode it runs the sync directly. Check status:
dinobase status
dinobase info
Confirm that sources appear with non-zero table and row counts.
Dinobase Cloud adds managed sync, OAuth connectors, and team sharing on top of local mode. It is currently invite-only. To get early access, join the waitlist at https://dinobase.ai.
Once a user has a Cloud account they can sign in with:
dinobase login --headless
This prints JSON to stdout:
{"status": "waiting", "login_url": "https://...", "message": "Open this URL to sign in to Dinobase Cloud"}
Present the login_url to the user: "Open this URL to sign in to your Dinobase Cloud account: <url>"
The command blocks until the user completes sign-in. When done, it prints:
{"status": "connected", "email": "[email protected]", "storage_url": "s3://..."}
Always follow this sequence when answering data questions:
dinobase info to see what sources and tables existdinobase describe <schema>.<table> on relevant tables to see columns, types, and sample datadinobase query "<sql>"dinobase confirm <mutation_id>All commands output JSON by default (machine-readable). Add --pretty for human-readable output.
dinobase login # sign in to Dinobase Cloud (opens browser)
dinobase login --headless # agent-friendly: prints login URL as JSON
dinobase logout # sign out
dinobase whoami # show current account info
dinobase sources --available # list all 100+ source types with auth info
dinobase auth hubspot --headless # OAuth connect (requires Cloud account)
dinobase add stripe --api-key sk_test_... # API key connect (works locally)
dinobase info # overview of all sources, tables, freshness
dinobase status # source status with freshness indicators
dinobase describe stripe.customers # table schema: columns, types, sample rows
# Run SQL (DuckDB dialect). Tables are schema.table
dinobase query "SELECT c.email, s.status FROM stripe.customers c JOIN stripe.subscriptions s ON c.id = s.customer_id WHERE s.status = 'past_due'"
# Limit rows returned (default 200, max 10000)
dinobase query "SELECT * FROM hubspot.contacts" --max-rows 500
Join across sources using shared columns (email, company name, IDs):
dinobase query "
SELECT c.email, c.name, i.amount_due, t.subject as ticket_subject
FROM stripe.customers c
JOIN stripe.invoices i ON c.id = i.customer_id
JOIN zendesk.tickets t ON c.email = t.requester_email
WHERE i.status = 'past_due' AND t.status = 'open'
"
UPDATE and INSERT queries return a preview first. Nothing executes until confirmed.
# Step 1: Query returns preview with mutation_id
dinobase query "UPDATE hubspot.contacts SET lifecycle_stage = 'customer' WHERE email = '[email protected]'"
# Step 2: Confirm to execute (writes back to API + updates data)
dinobase confirm <mutation_id>
# Or cancel
dinobase cancel <mutation_id>
dinobase refresh stripe # re-sync a specific source
dinobase refresh --stale # re-sync only stale sources
dinobase sync # sync all sources
schema.table (e.g., stripe.customers, hubspot.contacts)describe before writing queries to find correct column names and typesILIKE, LIST, STRUCT, regexp_matches(), date functions--pretty when showing results directly to the userdinobase status for freshness info and run dinobase refresh <source>describe on both tables to find join keysdinobase init and API key auth. Dinobase Cloud (OAuth, managed sync) is invite-only — send users to https://dinobase.ai to join the waitlist