# bbradar Docs — Programs, History, Alerts & API
> Explore the bug bounty catalog, review program History with Pro, set up alerts and API access, and understand program and target data.
Source: [https://bbradar.io/docs](https://bbradar.io/docs)
## [Choose your workflow](https://bbradar.io/docs.md#free-and-pro)
Use the public catalog to discover programs and compare their published details. Pro adds the target data, personal alerts, and developer tools used by the guides below.
| Task | Free access | With Pro |
| --- | --- | --- |
| Find programs | Browse platform listings, rewards, tags, program pages, and official policy links. | Add target-aware search, opportunity signals, report counts, and submission costs. |
| Plan audit contests | Compare public contest schedules, rewards and languages, and download available calendar events. | Inspect full program scope, target inventory and program intelligence. |
| Understand scope activity | See aggregate target counts and redacted examples of recent changes. | Read full target identities, eligibility, target changes, and supported repository events. |
| Review a program’s changes | See a compact History feature preview. | Open History beside Targets for recorded scope, reward, supported policy and repository changes, including Self-Hosted structured changes. |
| Find direct programs | Read the Self-Hosted guide and feature explanation. | Browse verified Self-Hosted paid programs and optional VDPs. |
| Receive alerts or use data in tools | Review the public setup guides and API reference. | Connect personal Telegram alerts, shared Discord access, the Pro API, and local MCP. |
[Explore the free catalogStart with programs and their official policies.](https://bbradar.io/)[Compare Pro plansReview features, billing options, and setup before subscribing.](https://bbradar.io/pro.md)
## [Your first 10 minutes](https://bbradar.io/docs.md#quick-start)
Start with the account checklist. It takes you from active Pro access to a working alert channel and, if you need automation, a Pro API key.
1. ### Open your account
Sign in with Google and confirm the Pro badge appears in [Account & Billing](https://bbradar.io/account).
2. ### Choose an alert channel
Connect Telegram for personal filtered alerts, Discord for shared Pro server access, or both.
3. ### Review notification rules
Select the events you want. Repository changes are opt-in, so enable that stream explicitly.
4. ### Create an API key if needed
Use one key for the Pro API and the local `@bbradar/mcp` server.
Sanitized product view
Account & Billing
Set up your Pro workspace
Pro
Subscription
Pro active
Telegram
Connect
Notification rules
Review
API & MCP
Create key
Account setup checklist with Pro access active. Example data and credentials are fictional or redacted; named product controls match the interface.
[Follow the full setupActivate Pro and verify each part of your account.](https://bbradar.io/docs/getting-started.md)[Fix a setup issueWork through quick checks for every integration.](https://bbradar.io/docs/troubleshooting.md)
## [Choose what to set up](https://bbradar.io/docs.md#choose-a-path)
[Audit contest calendarFind Web3 competitions, compare deadlines and export audit schedules.](https://bbradar.io/docs/contests.md)[Telegram alertsPrivate 1:1 alerts with your own filters.](https://bbradar.io/docs/notifications/telegram.md)[Notification rulesFilter by opportunity, target score, dupe risk, and saved exceptions.](https://bbradar.io/docs/notifications/rules.md)[MCP for AI toolsUse live Pro data from a compatible local MCP client.](https://bbradar.io/docs/mcp.md)[Pro APICall programs, opportunities, targets, target changes, and repository changes.](https://bbradar.io/docs/api.md)[Target intelligenceInvestigate and export active bounty scope.](https://bbradar.io/docs/pro/program-targets.md)[Program HistoryCompare recorded scope, rewards and supported policy changes in each program.](https://bbradar.io/docs/pro/program-history.md)[Repository changesReview repository updates connected to program scope.](https://bbradar.io/docs/pro/repository-changes.md)[Self-Hosted catalogFind direct programs, compare rewards and scope, and configure alerts.](https://bbradar.io/docs/pro/self-hosted.md)[Frequently asked questionsGet quick answers about the catalog, Pro, alerts, integrations, and billing.](https://bbradar.io/docs/faq.md)
## [What Pro unlocks](https://bbradar.io/docs.md#what-pro-unlocks)
- Target-aware catalog search
- Verified Self-Hosted paid programs and VDPs
- Full active target identities
- Per-program History with before and after details
- Program and target opportunity signals
- Latest target-change feed
- Multi-provider repository-change feed
- Personal Telegram rules
- Discord Pro role
- Pro API and local MCP access
Public docs, private data
These guides are public so you can evaluate setup before subscribing. Pro data, credentials, notification preferences, and billing controls remain behind your authenticated account.
## [Understand the terms](https://bbradar.io/docs.md#glossary)
| Term | Meaning |
| --- | --- |
| Bug bounty and VDP | A paid program advertises a monetary reward, which may have no published amount. A vulnerability disclosure policy (VDP) has no confirmed monetary reward. |
| Self-Hosted | A security program run directly by an organization. Admission uses first-party program evidence; the linked current policy controls scope and permission. |
| Program opportunity | A comparative program tier based on available freshness, public report activity, rewards, and scope evidence. |
| Target Intelligence | A target score, label, factor breakdown, and dupe-risk context, when the source supports those signals. |
| Dupe risk | An estimate of visible crowding, not a measured probability of a duplicate report. Unknown means evidence is insufficient. |
| Paused program | A confirmed paused platform listing remains browsable. Retained scope and rewards describe previously published information; current bounty eligibility is disabled. |
| Latest changes | Retained observations of material target changes. The feed is not a complete immutable history, and its first observation is distinct from a new upstream launch. |
| Program History | A timeline beside Targets on each program page. It compares accepted changes since tracking began, with coverage that varies by provider and field. |
| Repository baseline | The first observed ref/SHA is a silent starting point. Later supported branch updates can appear in the Commits feed. |
[How the signals are producedRead the evidence, freshness, and coverage limits behind the labels.](https://bbradar.io/docs/pro/discovery.md#methodology)
## [Documentation updates](https://bbradar.io/docs.md#documentation-updates)
19 September 2026: the [Program History guide](https://bbradar.io/docs/pro/program-history.md) explains the per-program timeline, Pro access, supported changes, UTC detection times and silent starting points. Self-Hosted, FAQ and tool guidance distinguish browser History from the existing API and MCP feeds.
13 September 2026: the contest calendar guide explains public access, filters, UTC deadlines, unconfirmed dates, calendar exports and reward types. The FAQs now cover audit competitions and schedule freshness.
8 September 2026: the API reference now describes paused programs, optional inventory queries, stable snapshots, expiry recovery, and current field types. The MCP guide confirms repository-feed support in version 0.2.3 and identifies remaining HTTP API capabilities.
These are documentation review notes, not program discovery dates or promises of source freshness. Check the authenticated capabilities response and the installed MCP guide for the contract your client uses.