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.

Instead, Titan routes worker-produced output back into the platform through ingestion and control-plane services so that users can retrieve results through stable public APIs.

​
Structured data flow

For structured results, the high-level flow is:
  1. The worker completes scraping logic
  2. The worker prepares structured output that matches the task’s schema
  3. The worker sends that output into the ingestion path
  4. The platform validates and persists the result
  5. Task Service exposes the completed output to the user
This keeps result ownership in the platform rather than in the worker runtime.

​
Media flow

For media assets, the flow is more explicit:
  1. The worker requests upload information
  2. The worker uploads binary content
  3. The worker commits the uploaded media
  4. The committed media becomes part of the execution output model
  5. Users later access that media through stable Titan URLs
This ensures media behaves like a first-class part of the platform result model.

​
Why ingestion is separate

Titan separates execution from ingestion so that it can:
  • Validate output against platform expectations
  • Preserve idempotent result handling
  • Manage binary media safely
  • Keep user-facing result access decoupled from worker runtime details

​
Control-plane outcome

Once a worker has returned its output successfully, users interact with:
  • Execution endpoints
  • Result endpoints
  • Dataset endpoints
  • Media download endpoints
They do not need to communicate with workers directly.

​
Next steps