Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.tumban.com/llms.txt

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

Every triage report includes a coverage object that reports which analysis steps ran successfully. Use it to interpret partial results honestly.

​
Fields

​
profile_scraped
boolean
required
true if Tumban successfully loaded the profile page and extracted bio, images, and links.
​
external_search_completed
boolean
required
true if the web search for external mentions of the profile completed.
​
social_links_checked
integer
required
Number of linked social profiles whose data Tumban fetched.
​
blocked_by_login
string[]
URLs Tumban could not analyze because they required login. Treated as neutral; not used to inflate the risk score.
​
referrer_domains_received
integer
Number of referrer domains read from the profile’s analytics, when available.
​
referrer_domains_after_filter
integer
Referrer domains remaining after Tumban filters out search engines and analytics platforms.
​
referrer_matches_found
integer
Referrer domains that matched a known prohibited platform.

​
When you’ll see partial coverage

If status is completed_with_partial, at least one step in the pipeline failed but the scan still produced a usable triage report. Common causes:
  • A scraper timed out on a slow page.
  • A linked URL required login and could not be analyzed.
  • A model call hit a transient infrastructure error.
The recommendation and score remain meaningful; check coverage for which inputs were missing before drawing conclusions about edge cases.