Fireworks AI Python API Docs | dltHub
Build a Fireworks AI-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Fireworks AI is a cloud platform and REST API for running and managing language, image, embedding and other ML models, plus model, deployment, and dataset management. The REST API base URL is https://api.fireworks.ai 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 Fireworks AI data in under 10 minutes.
What data can I load from Fireworks AI?
Here are some of the endpoints you can load from Fireworks AI:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| models | v1/accounts/{account_id}/models | GET | models | List models available to the account (includes pagination fields nextPageToken, totalSize). |
| deployments | v1/accounts/{account_id}/deployments | GET | deployments | List deployments for an account (paginated). |
| datasets | v1/accounts/{account_id}/datasets | GET | datasets | List datasets for an account (returns nextPageToken, totalSize). |
| responses | inference/v1/responses | GET | data | List inference responses (object=list, data array, has_more, first_id, last_id). |
| accounts | v1/accounts | GET | accounts | List accounts (returns accounts array, nextPageToken). |
| secrets | v1/accounts/{account_id}/secrets | GET | secrets | List secrets for an account (value field omitted for security). |
How do I authenticate with the Fireworks AI API?
All requests must include an Authorization header with a Bearer token (your API key) and a Content-Type: application/json header.
1. Get your credentials
- Sign in to the Fireworks dashboard at https://app.fireworks.ai.
- Navigate to Settings → Users → API Keys.
- Click "Create API key", give it a name, and confirm.
- Copy the generated key and store it securely; it will be used as the Bearer token for API calls.
2. Add them to .dlt/secrets.toml
[sources.fireworks_ai_source] api_key = "your_fireworks_api_key_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 Fireworks 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 fireworks_ai_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fireworks_ai_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fireworks_ai_data The duckdb destination used duckdb:/fireworks_ai.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline fireworks_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 models and deployments from the Fireworks 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 fireworks_ai_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.fireworks.ai", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "models", "endpoint": {"path": "v1/accounts/{account_id}/models", "data_selector": "models"}}, {"name": "deployments", "endpoint": {"path": "v1/accounts/{account_id}/deployments", "data_selector": "deployments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fireworks_ai_pipeline", destination="duckdb", dataset_name="fireworks_ai_data", ) load_info = pipeline.run(fireworks_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("fireworks_ai_pipeline").dataset() sessions_df = data.models.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fireworks_ai_data.models LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fireworks_ai_pipeline").dataset() data.models.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 Fireworks 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 a 401 response, ensure the Authorization: Bearer <API_KEY> header is present and that the API key is correct and active. Regenerate the key from the dashboard if needed.
Rate limits and 429 errors
Serverless endpoints enforce soft rate limits. When a 429 is returned, back off exponentially and retry. For on‑demand deployments, consider increasing capacity via the dashboard.
Pagination
List endpoints return nextPageToken (or first_id/last_id for inference responses). Include pageSize (or page_size) and the token in subsequent requests to retrieve additional pages.
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 Fireworks AI?
Request dlt skills, commands, AGENT.md files, and AI-native context.