American Registry for Internet Numbers (ARIN) Python API Docs | dltHub

Build a American Registry for Internet Numbers (ARIN)-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

ARIN's Registration RESTful Service (Reg-RWS) provides a programmatic interface for managing internet resource registrations, including IP network and POC information. The REST API base URL is https://reg.arin.net and All requests require an 'Authorization' header containing an API Key..

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 American Registry for Internet Numbers (ARIN) data in under 10 minutes.


What data can I load from American Registry for Internet Numbers (ARIN)?

Here are some of the endpoints you can load from American Registry for Internet Numbers (ARIN):

ResourceEndpointMethodData selectorDescription
poc/rest/poc/{handle}GETGet POC Information
org/rest/org/{handle}GETGet Org Information
net/rest/net/{handle}GETGet Network Information
asn/rest/asn/{handle}GETGet ASN Information
customer/rest/customer/{handle}GETGet Customer Information
rdns/rest/rdns/{handle}GETGet Delegation Information

How do I authenticate with the American Registry for Internet Numbers (ARIN) API?

ARIN's REST API requires an 'Authorization' header. The value must be formatted as 'ApiKey <your_api_key>', where <your_api_key> is the key generated in ARIN Online.

1. Get your credentials

To obtain an ARIN API key, log in to your ARIN Online account. Navigate to Settings, then go to the Security Info section. From the Actions menu, select Manage API Keys. In the Generate API Key section, select Create API Key. Ensure you copy the key immediately, as it is only displayed once. ARIN recommends storing this key in a secure location, such as a password management tool.

2. Add them to .dlt/secrets.toml

[sources.american_registry_for_internet_numbers_arin_source] arin_api_key = "API-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx-xxxx"

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 American Registry for Internet Numbers (ARIN) 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 american_registry_for_internet_numbers_arin_pipeline.py

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

Pipeline american_registry_for_internet_numbers_arin_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset american_registry_for_internet_numbers_arin_data The duckdb destination used duckdb:/american_registry_for_internet_numbers_arin.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 rest/net and rest/customer from the American Registry for Internet Numbers (ARIN) 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 american_registry_for_internet_numbers_arin_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://reg.arin.net", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "org", "endpoint": {"path": "rest/org/{handle}"}}, {"name": "poc", "endpoint": {"path": "rest/poc/{handle}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="american_registry_for_internet_numbers_arin_pipeline", destination="duckdb", dataset_name="american_registry_for_internet_numbers_arin_data", ) load_info = pipeline.run(american_registry_for_internet_numbers_arin_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("american_registry_for_internet_numbers_arin_pipeline").dataset() sessions_df = data.org.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM american_registry_for_internet_numbers_arin_data.org LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("american_registry_for_internet_numbers_arin_pipeline").dataset() data.org.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 American Registry for Internet Numbers (ARIN) 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 American Registry for Internet Numbers (ARIN)?

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