World Creator Python API Docs | dltHub
Build a World Creator-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
World Creator is a terrain and landscape generator that provides a REST API for accessing data and integration with other tools. The REST API base URL is https://docs.world-creator.com/ and all requests require a Bearer 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 World Creator data in under 10 minutes.
What data can I load from World Creator?
Here are some of the endpoints you can load from World Creator:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| terrain_shape_layers | reference/terrain/shape-layers | GET | Retrieves a list of all terrain shape layers. | |
| terrain_shape_layers_path | reference/terrain/shape-layers/path | GET | Retrieves path-specific terrain shape layer details. | |
| terrain_shape_layers_rivers | reference/terrain/shape-layers/rivers | GET | Retrieves river-specific terrain shape layer details. | |
| scene | reference/scene | GET | Retrieves scene configuration data. | |
| application_options | reference/options/application | GET | Retrieves application settings and configuration. |
How do I authenticate with the World Creator API?
Authentication uses a bearer token provided in the Authorization header.
1. Get your credentials
World Creator does not currently expose a direct, public-facing REST API for customer data management that utilizes standard API key authentication. The dltHub integration for World Creator typically leverages specific documentation-based endpoints or structured data exports designed for programmatic access via HTTP GET requests, rather than a traditional API key-based system. For standard World Creator software usage, you must use your email and a seat-specific password (generated via the Customer Portal) to activate the application; these credentials should not be confused with API authentication tokens. If you are developing a data pipeline using dlt, configure your credentials by defining an environment variable or a entry in your secrets.toml file as instructed by your data integration platform's specific loader module.
2. Add them to .dlt/secrets.toml
[sources.world_creator_source] access_token = "your_access_token_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 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 World Creator 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 world_creator_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline world_creator_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset world_creator_data The duckdb destination used duckdb:/world_creator.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 reference/terrain/shape-layers and reference/terrain/shape-layers/path from the World Creator 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 world_creator_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://docs.world-creator.com/", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "terrain_shape_layers", "endpoint": {"path": "reference/terrain/shape-layers"}}, {"name": "scene", "endpoint": {"path": "reference/scene"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="world_creator_pipeline", destination="duckdb", dataset_name="world_creator_data", ) load_info = pipeline.run(world_creator_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("world_creator_pipeline").dataset() sessions_df = data.terrain_shape_layers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM world_creator_data.terrain_shape_layers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("world_creator_pipeline").dataset() data.terrain_shape_layers.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 World Creator 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.
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 World Creator?
Request dlt skills, commands, AGENT.md files, and AI-native context.