tumban

Submit creator profiles to the Tumban API for compliance scanning and risk scoring.

Updated Apr 29, 2026
One-click install
npx skills add https://github.com/Dataring-engineering/mintlify-docs --skill tumban
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tumban
Source: https://github.com/Dataring-engineering/mintlify-docs/tree/main
Command: npx skills add https://github.com/Dataring-engineering/mintlify-docs --skill tumban

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires httpx, requests, requests_toolbelt, and includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the process of scanning creator profiles for prohibited and restricted content, saving time and reducing manual errors.

Core Features & Use Cases

  • ToS Compliance Scanning: Analyze creator profiles against terms of service for prohibited content.
  • Prohibited-Content Analysis: Identify potential violations of platform rules.
  • Asynchronous Scan Lifecycle: Submit profiles for analysis and receive results via webhook or polling.
  • API Key Management: Create, list, and revoke API keys for organization access.
  • Webhook Integration: Receive scan results asynchronously to integrate with your workflow.

Quick Start

Submit your first scan using the Tumban API with the provided API key: curl -X POST https://api-v2.tumban.com/api/v2/scan/deep -H "Authorization: Bearer sk_your_api_key" -H "Content-Type: application/json" -d '{"profile_url": "https://creator.example/username", "callback_url": "https://your-app.example/webhooks/tumban", "metadata": {"reviewer_id": "rv_42"}}'

Frequently Asked Questions about tumban

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate ToS compliance scanning for creator profiles?

To automate ToS compliance scanning, you submit creator profile URLs to an external API, which analyzes them for prohibited content. The system then returns a structured recommendation with risk scoring, confidence level, and evidence index.

How does asynchronous scanning handle webhook integration for compliance results?

Asynchronous scanning works by submitting a profile with a callback URL to the API. When the compliance scan finishes, the system sends the risk assessment and evidence index results directly to your webhook endpoint.

Can I use HTTP requests to manage API keys for compliance scanning?

Yes, you can manage API keys by sending HTTP requests to the API. You can create, list, and revoke bearer tokens to securely control organization access for your prohibited-content analysis workflows.

What do I need to set up before submitting a profile for prohibited-content analysis?

To submit a profile for prohibited-content analysis, you need an HTTPS endpoint, a valid bearer token for authorization, and JSON-formatted payloads containing the target profile URL and a callback URL.

What is the best way to retrieve risk assessment results after a scan lifecycle?

The best way to retrieve risk assessment results is through webhook integration, which pushes the structured recommendation asynchronously. Alternatively, you can use polling requests to check the scan lifecycle status.

Why does my compliance scan require a bearer token and JSON payload?

Compliance scans require a bearer token to authenticate your organization's API access and JSON payloads to properly structure the profile URL and metadata. This ensures secure, standardized processing of asynchronous scans.