Winston-ai Python API Docs | dltHub
Build a Winston-ai-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Winston AI is a platform that provides AI-powered content and image detection, plagiarism and fact-checking APIs. The REST API base URL is https://api.gowinston.ai/v2 and all requests require a Bearer token for authentication.
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Winston-ai data in under 10 minutes.
What data can I load from Winston-ai?
Here are some of the endpoints you can load from Winston-ai:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| ai_content_detection | /v2/ai-content-detection | POST | (top-level object) | Detect likelihood a text was AI-generated; returns status, score, sentences, input, credits info |
| image_detection | /v2/image-detection | POST | (top-level object) | Detect AI-generated or manipulated images; returns score, metadata and credits info |
| plagiarism | /v2/plagiarism | POST | (top-level object) | Plagiarism detection results and matched sources |
| fact_checker | /v2/fact-checker | POST | (top-level object) | Fact-check results for provided claims/text |
| text_compare | /v2/text-compare | POST | (top-level object) | Compares two texts and returns similarity metrics |
How do I authenticate with the Winston-ai API?
All API endpoints are authenticated using Bearer tokens. Include the token in the Authorization header as: Authorization: Bearer .
1. Get your credentials
- Register or sign in to the Winston AI developer dashboard at https://dev.gowinston.ai. 2) In the dashboard, open the API / Tokens section. 3) Create or copy an API token (Bearer token) to use in requests. 4) Store this token securely for use in your dlt source configuration.
2. Add them to .dlt/secrets.toml
[sources.winston_ai_source] api_token = "your_bearer_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
dlt ai toolkit rest-api-pipeline install
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Winston-ai API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
python winston_ai_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline winston_ai_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset winston_ai_data The duckdb destination used duckdb:/winston_ai.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline winston_ai_pipeline show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads ai_content_detection and image_detection from the Winston-ai API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def winston_ai_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.gowinston.ai/v2", "auth": { "type": "bearer", "api_token": api_token, }, }, "resources": [ {"name": "ai_content_detection", "endpoint": {"path": "v2/ai-content-detection"}}, {"name": "image_detection", "endpoint": {"path": "v2/image-detection"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="winston_ai_pipeline", destination="duckdb", dataset_name="winston_ai_data", ) load_info = pipeline.run(winston_ai_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("winston_ai_pipeline").dataset() sessions_df = data.ai_content_detection.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM winston_ai_data.ai_content_detection LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("winston_ai_pipeline").dataset() data.ai_content_detection.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Winston-ai data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Authentication failures
If you receive 401 Unauthorized, verify your Authorization header is exactly: Authorization: Bearer . Ensure the token is active and has not been rotated or revoked in the developer dashboard (https://dev.gowinston.ai).
Rate limits and credits exhausted
The API returns 429 Too Many Requests for rate limiting and 402 Payment Required when credits are insufficient. Monitor credits_remaining returned in responses and refill/purchase credits in the dashboard.
Request validation and content errors
400 Bad Request indicates malformed payloads. 415 Unsupported Media Type is returned for unsupported file types. Check the endpoint-specific request body and Content-Type header.
Server errors
500/503 can occur for transient server issues; retry with exponential backoff.
Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-runtime— Deploy, schedule, and monitor your pipeline in production.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Winston-ai?
Request dlt skills, commands, AGENT.md files, and AI-native context.