Skip to main content

Documentation Index

Fetch the complete documentation index at: https://webscraping.titannet.io/docs/llms.txt

Use this file to discover all available pages before exploring further.

This means an execution can produce regular fields such as names, prices, or status values, while also returning references to images, audio, or video gathered during the run.

Structured result data

Structured result data is the main output of an execution that includes schema-shaped fields. It is shaped by the task’s output schema and then exposed through:
  • Result metadata endpoints
  • Downloadable exports
  • Datasets associated with completed executions or tasks

Datasets

Datasets are the user-facing representation of completed structured output from runs. At a high level, datasets allow users to work with completed results in a form that is easier to:
  • List
  • Export
  • Analyze
  • Consume in downstream systems
Datasets are especially useful when tasks run repeatedly and users want a normalized view of collected output over time.

Media fields

Some tasks return media fields inside the structured output. In Titan, media is not treated as an arbitrary external file link. Instead, the platform stores media through a managed ingestion flow and exposes stable platform URLs for later retrieval.

Why media uses platform URLs

Media URLs are platform-managed so that Titan can:
  • Enforce access control
  • Verify ownership through execution context
  • Support short-lived download resolution
  • Separate public result access from internal object storage details
This is why result payloads may contain stable Titan URLs instead of direct storage links.

Export behavior

When users export results, the platform can preserve media values as plain URL strings or resolve them into more directly consumable forms for frontend use, depending on the export path. The important platform-level idea is that media remains part of the result model without forcing users to manage object storage directly.

Next steps