Load Pacifica data to DuckDB

Pacifica is a decentralized exchange platform providing REST API access for trading and account management operations. Everything needed to build a working Pacifica → 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 Pacifica to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Pacifica 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 Pacifica 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.

---

Pacifica API at a glance

These values come from the Pacifica API reference — the authoritative source if anything here looks out of date.

---

How do I authenticate with the Pacifica API?

POST requests require Ed25519 signature authentication. Required headers include 'account' (public key), 'signature' (Base58 encoded Ed25519), 'timestamp', and 'expiry_window', with an optional 'agent_wallet' for agent keys.

1. Get your credentials

To obtain API credentials for Pacifica, navigate to the official API Agent Keys portal at https://app.pacifica.fi/apikey. You can generate an "API Agent Key" (also known as an Agent Wallet) directly in your browser. This process involves signing a binding transaction with your main wallet, ensuring your primary private key remains secure. For higher-level rate limiting, you can also generate "API Config Keys" programmatically via the /api/v1/account/api_keys/create REST endpoint, which requires your wallet address and a cryptographic signature.

2. Add them to .dlt/secrets.toml

Copy
[sources.pacifica_source]
# To use for authentication in dlt (e.g., in .dlt/secrets.toml):\nPACIFICA_ADDRESS = \"your_wallet_address\"\nPACIFICA_AGENT_PRIVATE_KEY = \"your_base58_agent_wallet_secret_key\"\nPACIFICA_RATE_LIMIT_KEY = \"your_optional_pf_api_key_for_rate_limiting\"

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 Pacifica data can I load into DuckDB?

These are the Pacifica endpoints dlt can load into DuckDB:

---

How do I load only new Pacifica records?

Pacifica exposes next_cursor on api/v1/orders/history, 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.

Copy
{"name": "orders", "endpoint": {
    "path": "api/v1/orders/history",
    "incremental": {"cursor_path": "next_cursor", "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 Pacifica pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /api/v1/account/api_keys and /api/v1/account/api_keys/create from the Pacifica API into DuckDB:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def pacifica_source(private_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.pacifica.fi/api/v1",
            "auth": {"type": "api_key", "api_key": private_key, "name": "private_key"},
        },
        "resources": [
            {"name": "orders", "endpoint": {"path": "api/v1/orders/history"}},
            {"name": "funding_rates", "endpoint": {"path": "api/v1/funding_rate/history"}}
        ],
    }
    yield from rest_api_resources(config)


def load_pacifica_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="pacifica_pipeline",
        destination="duckdb",
        dataset_name="pacifica_data",
    )
    load_info = pipeline.run(pacifica_source())
    print(load_info)


if __name__ == "__main__":
    load_pacifica_to_duckdb()

Run it with python pacifica_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 Pacifica 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):

Copy
import dlt

data = dlt.pipeline("pacifica_pipeline").dataset()
df = data.orders.df()
print(df.head())

SQL:

Copy
SELECT * FROM pacifica_data.orders LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.

---

How do I deploy the Pacifica 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 Pacifica loads into governed, documented models.
• Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →

---

What other destinations can I load Pacifica data to?

dlt loads into any of these — only the destination argument changes:

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack