Load Stripe - Crypto Onramp Quotes data to DuckDB
Build a Stripe - Crypto Onramp Quotes to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Stripe - Crypto Onramp Quotes API base URL, auth, endpoints, and incremental loading.
Stripe Crypto Onramp Quotes API allows you to retrieve estimated quotes for onramp conversions into various cryptocurrencies on different networks before directing users to the onramp widget. Everything needed to build a working Stripe - Crypto Onramp Quotes → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.
Build your Stripe - Crypto Onramp Quotes to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Stripe - Crypto Onramp Quotes to DuckDB and run it on dltHub
That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Stripe - Crypto Onramp Quotes API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →
Prefer to write it yourself? Every fact the agent uses is below.
Stripe - Crypto Onramp Quotes API at a glance
| Base URL | https://api.stripe.com |
| Example endpoint | GET v1/crypto/onramp/quotes |
| Records found at | destination_network_quotes |
| Authentication | all requests require either HTTP Basic Auth or Bearer token authentication — sent in the Authorization header, prefixed Bearer |
| Pagination | Cursor-based via starting_after, page size via limit (default 10, max 100). For v1 list endpoints, pagination is cursor-based via starting_after (next page) and ending_before (previous page). starting_after and ending_before are mutually exclusive. The Crypto Onramp Quotes endpoint described in the provided sources is a retrieve endpoint (GET /v1/crypto/onramp/quotes), not a list endpoint, so the provided pagination parameters are for Stripe list/search APIs generally, as documented in Stripe Pagination docs. |
| Incremental field | created |
| Record id | id |
| API reference | https://docs.stripe.com/api/authentication |
These values come from the Stripe - Crypto Onramp Quotes API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Stripe - Crypto Onramp Quotes API?
The API uses HTTP Basic Authentication, where the API key is provided as the username (with no password). Alternatively, it supports Bearer token authentication using the 'Authorization: Bearer ' header.
1. Get your credentials
- Navigate to the Stripe Dashboard at https://dashboard.stripe.com/apikeys. 2. Sign in to your account. 3. If you have not already, complete the crypto onramp application process at https://dashboard.stripe.com/crypto-onramp/onboarding. 4. Once approved, use the 'API keys' tab in the dashboard to reveal and copy your 'Secret key' (starts with sk_test_ or sk_live_) and 'Publishable key' (starts with pk_test_ or pk_live_). For local development, use the test mode keys.
2. Add them to .dlt/secrets.toml
[sources.stripe_crypto_onramp_quotes_source] stripe_api_key = "sk_test_..." stripe_publishable_key = "pk_test_..."
dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.
What Stripe - Crypto Onramp Quotes data can I load into DuckDB?
These are the Stripe - Crypto Onramp Quotes endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| crypto_onramp_quotes | /v1/crypto/onramp/quotes | GET | Retrieve a quote for a crypto onramp |
How do I load only new Stripe - Crypto Onramp Quotes records?
Stripe - Crypto Onramp Quotes exposes created on v1/crypto/onramp/quotes, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.
{"name": "crypto_onramp_quotes", "endpoint": { "path": "v1/crypto/onramp/quotes", "data_selector": "destination_network_quotes", "incremental": {"cursor_path": "created", "initial_value": "2024-01-01T00:00:00Z"}, }}
On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.
What does the generated Stripe - Crypto Onramp Quotes pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading POST /v1/crypto/onramp_sessions and GET /v1/crypto/onramp_sessions/:id from the Stripe - Crypto Onramp Quotes API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def stripe_crypto_onramp_quotes_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.stripe.com", "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": api_key}, }, "resources": [ {"name": "crypto_onramp_quotes", "endpoint": {"path": "v1/crypto/onramp/quotes", "data_selector": "destination_network_quotes"}} ], } yield from rest_api_resources(config) def load_stripe_crypto_onramp_quotes_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="stripe_crypto_onramp_quotes_pipeline", destination="duckdb", dataset_name="stripe_crypto_onramp_quotes_data", ) load_info = pipeline.run(stripe_crypto_onramp_quotes_source()) print(load_info) if __name__ == "__main__": load_stripe_crypto_onramp_quotes_to_duckdb()
Run it with python stripe_crypto_onramp_quotes_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.
How do I query Stripe - Crypto Onramp Quotes data in DuckDB?
dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("stripe_crypto_onramp_quotes_pipeline").dataset() df = data.crypto_onramp_quotes.df() print(df.head())
SQL:
SELECT * FROM stripe_crypto_onramp_quotes_data.crypto_onramp_quotes LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Stripe - Crypto Onramp Quotes to DuckDB pipeline in production?
The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.
- Deploy & schedule — run the pipeline as a managed job with automatic retries.
- Monitor — observable job queues, alerting, and load metrics for every run.
- Transform — promote raw Stripe - Crypto Onramp Quotes loads into governed, documented models.
- Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.
What other destinations can I load Stripe - Crypto Onramp Quotes data to?
dlt loads into any of these — only the destination argument changes:
| Destination | Example value |
|---|---|
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.
Next steps
Was this page helpful?
Community Hub
Need more dlt context for Stripe - Crypto Onramp Quotes to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.