Load ASIC Company Lookup data to DuckDB

ASIC provides various machine-to-machine (M2M) web services to support business, company, and financial registry searches and lodgements for registered intermediaries and software developers. Everything needed to build a working ASIC Company Lookup → 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 ASIC Company Lookup 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 ASIC Company Lookup 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 ASIC Company Lookup 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.

---

ASIC Company Lookup API at a glance

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

---

How do I authenticate with the ASIC Company Lookup API?

ASIC M2M web services typically require HTTP Basic Authentication using a username and password issued by ASIC upon registration. The authorization information is often embedded within the message payload (e.g., senderId) as specified in the relevant technical Message Implementation Guides.

1. Get your credentials

To obtain access to ASIC's official web services, you must apply to become an ASIC digital service provider. Contact webservices@asic.gov.au to request the application information, specifying which API you require and your purpose for access. Upon approval and registration, ASIC will issue you the necessary credentials (typically a unique username and password or a senderId) and provide access to the required technical specifications, WSDLs, and schema files. Note that ASIC does not provide a self-service dashboard for API key generation; credential management is handled via this formal application process.

2. Add them to .dlt/secrets.toml

Copy
[sources.asic_company_lookup_source]
asic_username = "your_username_here"
asic_password = "your_password_here"
asic_sender_id = "your_sender_id_here"

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 ASIC Company Lookup data can I load into DuckDB?

These are the ASIC Company Lookup endpoints dlt can load into DuckDB:

---

How do I load only new ASIC Company Lookup records?

The ASIC Company Lookup API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "nni_details", "endpoint": {
    "path": "getNni",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "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 ASIC Company Lookup pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading getNni and searchNniName from the ASIC Company Lookup API into DuckDB:

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

@dlt.source
def asic_company_lookup_source(username=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://www.gateway.asic.gov.au/gateway/",
            "auth": {"type": "http_basic", "username": "REPLACE_ME", "password": username},
        },
        "resources": [
            {"name": "nni_details", "endpoint": {"path": "getNni"}},
            {"name": "nni_search", "endpoint": {"path": "searchNniName"}}
        ],
    }
    yield from rest_api_resources(config)


def load_asic_company_lookup_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="asic_company_lookup_pipeline",
        destination="duckdb",
        dataset_name="asic_company_lookup_data",
    )
    load_info = pipeline.run(asic_company_lookup_source())
    print(load_info)


if __name__ == "__main__":
    load_asic_company_lookup_to_duckdb()

Run it with python asic_company_lookup_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 ASIC Company Lookup 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("asic_company_lookup_pipeline").dataset()
df = data.getNni.df()
print(df.head())

SQL:

Copy
SELECT * FROM asic_company_lookup_data.getNni LIMIT 10;

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

---

How do I deploy the ASIC Company Lookup 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 ASIC Company Lookup 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 ASIC Company Lookup 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