Skip to content

docs: Building custom reporting flows without ChainPatrol bots#89

Open
NikitaVr wants to merge 3 commits into
mainfrom
knowledge-update/building-custom-reporting-flows-without-chainpatrol-bots-1779830654706
Open

docs: Building custom reporting flows without ChainPatrol bots#89
NikitaVr wants to merge 3 commits into
mainfrom
knowledge-update/building-custom-reporting-flows-without-chainpatrol-bots-1779830654706

Conversation

@NikitaVr
Copy link
Copy Markdown
Contributor

@NikitaVr NikitaVr commented May 26, 2026

Knowledge Update: Building custom reporting flows without ChainPatrol bots

This PR was automatically generated from a knowledge base update.

Changes

  • API Overview (external-api/overview.mdx): Added information about building custom reporting flows for unsupported platforms using the Asset Check and Report Create APIs
  • Asset Check (external-api/asset-check.mdx): Added use case information for building custom reporting flows on unsupported platforms
  • Report Create (external-api/report-create.mdx): Added use case information for building custom reporting flows on unsupported platforms

Knowledge Entry

Topic: Building custom reporting flows without ChainPatrol bots
Added by: nikita@chainpatrol.io
Date: 2026-05-26

Content:

If a customer wants to build their own reporting flow — for a chat app we don't support yet, for their internal systems, or any case where they can't use our Discord/Telegram/Slack bots — they can use ChainPatrol's public APIs to replicate the functionality:

  • Asset Check API (/external-api/asset-check) to check the status of domains/URLs/addresses against ChainPatrol's blocklist (e.g., to warn users about malicious links in their chat or platform).
  • Report Create API (/external-api/report-create) to submit reports into ChainPatrol from their own system, so reports still land in the ChainPatrol review queue and benefit from the full detection/review/takedown pipeline.

This is the recommended path for any "we want bot-like reporting but on a platform/system you don't support" question.

Original Message

update your knowledge. If a customer wants to build their own reporting flow, say in a chat app we don't support yet, or in their internal systems, or for some reason they can't use our bots, they can use our Asset Check API to check the status of domains in our report API for creating reports from their system


Auto-generated by the ChainPatrol Knowledge Agent


Note

Low Risk
Documentation-only changes to external API MDX; no runtime, auth, or data-handling code.

Overview
Documents how to replicate Discord/Telegram/Slack bot–style reporting on unsupported platforms using public APIs.

external-api/overview.mdx adds a Custom Reporting Flows section: use Asset Check to warn users about blocklisted links and Report Create to file reports into ChainPatrol’s review pipeline when bots aren’t an option.

asset-check.mdx and report-create.mdx each add a <Note> with the same custom-flow use case. Asset Check also fixes the Quick Start auth example’s closing ``` fence.

Reviewed by Cursor Bugbot for commit efefb1d. Bugbot is set up for automated code reviews on this repo. Configure here.

@mintlify
Copy link
Copy Markdown
Contributor

mintlify Bot commented May 26, 2026

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
chainpatrol 🔴 Failed May 26, 2026, 9:26 PM

💡 Tip: Enable Workflows to automatically generate PRs for you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant