Vertex Protocol Python API Docs | dltHub

Build a Vertex Protocol-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Vertex Protocol is a decentralized exchange protocol that provides APIs for trading and market data access across multiple blockchain networks. The REST API base URL is https://gateway.prod.vertexprotocol.com/v1 and Authentication relies on EIP-712 signing rather than a bearer or API token..

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 add "dlt[hub]" and start loading Vertex Protocol data in under 10 minutes.


What data can I load from Vertex Protocol?

Here are some of the endpoints you can load from Vertex Protocol:

ResourceEndpointMethodData selectorDescription
subaccountssubaccountsGETList vertex subaccounts via the indexer.
interest_and_fundinginterest_and_funding_paymentsGETList interests and funding payments for a subaccount.
candlestickscandlesticksGETFetch market candlesticks.
marketsall_productsGETRetrieve information about all available products.
open_orderssubaccount_open_ordersGETRetrieve open orders for a subaccount.

How do I authenticate with the Vertex Protocol API?

Vertex Protocol API interactions typically require EIP-712 cryptographic signatures rather than traditional token-based authentication. The SDK manages these signatures internally when a signer (such as a private key or LocalAccount) is provided.

1. Get your credentials

Vertex Protocol does not use traditional API keys or a dashboard for API key generation. Instead, access is authenticated via blockchain-based cryptographic signatures. To obtain credentials, you must possess a private key (for an Ethereum or compatible EVM wallet) that holds an account on the protocol. Your private key acts as your identity and credential for signing requests. Keep this private key highly secure and never share it. In a development environment, you typically store your private key securely as an environment variable (e.g., SIGNER_PRIVATE_KEY) to be accessed by your application.

2. Add them to .dlt/secrets.toml

[sources.vertex_protocol_source] SIGNER_PRIVATE_KEY = "0x..."

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 init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Vertex Protocol 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:

uv run python vertex_protocol_pipeline.py

If everything is configured correctly, you'll see output like this:

Pipeline vertex_protocol_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset vertex_protocol_data The duckdb destination used duckdb:/vertex_protocol.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

uv run dlthub 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 /query and /execute (implied through client interaction) from the Vertex Protocol 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 vertex_protocol_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://gateway.prod.vertexprotocol.com/v1", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "subaccounts", "endpoint": {"path": "subaccounts"}}, {"name": "interest_and_funding", "endpoint": {"path": "interest_and_funding_payments"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="vertex_protocol_pipeline", destination="duckdb", dataset_name="vertex_protocol_data", ) load_info = pipeline.run(vertex_protocol_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("vertex_protocol_pipeline").dataset() sessions_df = data.subaccounts.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM vertex_protocol_data.subaccounts LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("vertex_protocol_pipeline").dataset() data.subaccounts.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 Vertex Protocol data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

DestinationExample 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.


Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI harness:

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Vertex Protocol?

Request dlt skills, commands, AGENT.md files, and AI-native context.

Available Pipelines