Load Frase data to DuckDB
Build a Frase to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Frase API base URL, auth, endpoints, and incremental loading.
Frase is a content intelligence platform providing a REST API to programmatically manage content, briefs, SERP analysis, audits, research, and AI-visibility data. Everything needed to build a working Frase → 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 Frase to DuckDB pipeline
Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.
PromptRunuvx dlthub-init@latestto build a pipeline from Frase 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 Frase 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.
Frase API at a glance
| Base URL | https://next.frase.io/api/v1 |
| Example endpoint | GET api/v1/research/list |
| Records found at | research_sessions |
| Authentication | all requests require an API key in the X-API-KEY header — sent in the X-API-KEY header |
| Pagination | Page-number |
| API reference | https://next.frase.io/api/docs |
These values come from the Frase API reference — the authoritative source if anything here looks out of date.
How do I authenticate with the Frase API?
Authentication is handled by passing an API key in the 'X-API-KEY' HTTP request header. No separate OAuth flow is required.
1. Get your credentials
To obtain your Frase API key, log in to your Frase account, navigate to the Settings menu (often found in the bottom left corner), and select the API or API Keys section. From there, you can view and copy your unique live or test API key.
2. Add them to .dlt/secrets.toml
[sources.frase_source] FRASE_API_KEY = "sk_live_your_api_key_here"
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 Frase data can I load into DuckDB?
These are the Frase endpoints dlt can load into DuckDB:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| list_research | /api/v1/research/list | GET | research_sessions | List all research sessions |
| list_audits | /api/v1/audits/list | GET | audits | List site audits |
| list_prompts | /api/v1/prompts/list | GET | prompts | List all monitored AI prompts |
| list_optimizations | /api/v1/optimizations/list | GET | optimizations | List optimization sessions |
| get_gsc_queries | /api/v1/gsc/queries | GET | queries | Get GSC search queries |
How do I load only new Frase records?
The Frase API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.
{"name": "list_research", "endpoint": { "path": "api/v1/research/list", # Replace with a field that increases on every write. "incremental": {"cursor_path": "REPLACE_ME", "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 Frase pipeline look like?
A standard dlt REST API pipeline — the same code you would write by hand, loading /serp/analyze and /content from the Frase API into DuckDB:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def frase_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://next.frase.io/api/v1", "auth": {"type": "api_key", "api_key": api_key, "name": "X-API-KEY", "location": "header"}, }, "resources": [ {"name": "list_research", "endpoint": {"path": "api/v1/research/list", "data_selector": "research_sessions"}}, {"name": "list_audits", "endpoint": {"path": "api/v1/audits/list", "data_selector": "audits"}} ], } yield from rest_api_resources(config) def load_frase_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="frase_pipeline", destination="duckdb", dataset_name="frase_data", ) load_info = pipeline.run(frase_source()) print(load_info) if __name__ == "__main__": load_frase_to_duckdb()
Run it with python frase_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 Frase 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("frase_pipeline").dataset() df = data.list_research.df() print(df.head())
SQL:
SELECT * FROM frase_data.list_research LIMIT 10;
See querying your data with dataset and exploring it in marimo notebooks.
How do I deploy the Frase 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 Frase 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 Frase 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 Frase to DuckDB?
Request dlt skills, commands, AGENT.md files, and AI-native context.