ae_bilibili_huahuo_upper_base_info
### Purpose:
- Retrieve a creator's basic identity and supported collaboration formats.
### Parameters:
- `mid`: Required creator UID.
### Returns:
- UID, nickname, avatar, MCN organization, and supported collaboration
types in `state_types`.
AE input example:
{"mid":3546381696371423}
ae_bilibili_huahuo_upper_busy_time
### Purpose:
- Check a creator's unavailable dates when planning a collaboration schedule.
### Parameters:
- `mid`: Required creator UID.
### Returns:
- Occupied or unavailable dates and related schedule information.
AE input example:
{"mid":3546381696371423}
ae_bilibili_huahuo_upper_detail
### Purpose:
- Retrieve a complete commercial profile for creator evaluation, campaign
selection, and collaboration pricing analysis.
### Parameters:
- `upper_mid`: Required creator UID.
### Returns:
- Basic profile, collaboration prices in `upper_prices`, overview metrics
in `overview_v3`, and content/persona labels.
- Video category and duration distributions, follower demographics in
`*_distributions`, and viewer demographics in `*_distributions_audience`.
AE input example:
{"upper_mid":3546381696371423}
ae_bilibili_huahuo_upper_draft_performance
### Purpose:
- Summarize a creator's content mix and traffic performance over a selected period.
### Parameters:
- `upper_mid`: Required creator UID.
- `day_range`: Period: `1` last 30 days, `2` last 90 days, or `3` last
180 days. Defaults to `3`.
### Returns:
- Video-category distribution, duration distribution, traffic-source
distribution, and related aggregate metrics.
AE input example:
{"day_range":3,"upper_mid":3546381696371423}
ae_bilibili_huahuo_upper_draft_trend
### Purpose:
- Analyze changes in a creator's video views, engagement, or watch-time metrics.
### Parameters:
- `upper_mid`: Required creator UID.
- `trend_type`: Metric type: `3` views, `4` likes, `5` comments,
`6` danmaku comments, or `7` watch time. Defaults to `3`.
### Returns:
- Metric trend series, median, minimum and maximum values, plus per-video details.
AE input example:
{"trend_type":3,"upper_mid":3546381696371423}
ae_bilibili_huahuo_upper_fans_trend
### Purpose:
- Review follower size and growth velocity to evaluate account momentum and stability.
### Parameters:
- `upper_mid`: Required creator UID.
- `query_type`: Data mode: `1` total followers or `2` follower growth.
Defaults to `1`.
### Returns:
- Daily follower trend data and growth amount/rate for the last 7, 30, 90,
180, and 365 days.
AE input example:
{"query_type":1,"upper_mid":3546381696371423}
ae_bilibili_huahuo_upper_label_tree
### Purpose:
- Retrieve the creator-filter configuration for a selected industry strategy panel.
### Parameters:
- `panel_type`: Strategy panel: `0` general, `1` gaming, `2` beauty,
`3` digital products, `4` automotive, `5` performance, `6` food and
beverage, or `8` internet services.
### Returns:
- A configuration tree containing filter groups, fields, labels, option values,
and display order.
- `search_upper.label_array` uses only node `value`s from the “Content type”
group, with every selected content type in one inner array. A single Outdoor
adventure selection is `[[794]]`; Outdoor adventure, AI short film, and AI
entertainment together are `[[794,747,748]]`.
- `label_array` is only for content types. Cooperation-pricing options are
returned at `data.price_info_options` by `square_static_info`.
This is a supporting configuration, filter-value, or label lookup for related Huahuo queries.
AE input example:
{"panel_type":0}
ae_bilibili_huahuo_upper_representative
### Purpose:
- Retrieve a creator's representative personal or sponsored videos to
assess content quality and commercial experience.
### Parameters:
- `upper_mid`: Required creator UID.
- `type`: Video type: `1` personal work or `2` commercial work. Defaults to `2`.
### Returns:
- Representative videos with identifiers, titles, covers, duration, view
counts, and highlight labels.
AE input example:
{"type":2,"upper_mid":3546381696371423}
ae_bilibili_huahuo_upper_seek_info
### Purpose:
- Query the collaboration inquiry types and capability settings available
for a creator.
### Parameters:
- `mid`: Required creator UID.
### Returns:
- Inquiry status, supported collaboration types, and related settings.
AE input example:
{"mid":3546381696371423}
ae_bilibili_huahuo_x_huo_date_options
### Purpose:
- Get valid monthly or quarterly X-Huo periods for `popular_up_x_huo` requests.
### Parameters:
- `rank_date_type`: Ranking period type: `1` monthly or `2` quarterly.
### Returns:
- An ascending list of `YYYY-MM` periods. The final item is the latest
completed period; the current incomplete period is excluded.
This is a supporting configuration, filter-value, or label lookup for related Huahuo queries.
AE input example:
{"rank_date_type":1}
ae_bilibili_huahuo_x_huo_industry_drop
### Purpose:
- Retrieve the two-level X-Huo industry tree used by creator and product rankings.
### Parameters:
- `scene`: Ranking scene: `1` creator ranking or `2` product ranking. The
industry ID sets are different between scenes.
### Returns:
- A two-level industry list whose node `id` values can be passed as
`x_huo_industry_id` to the matching ranking endpoints.
This is a supporting configuration, filter-value, or label lookup for related Huahuo queries.
AE input example:
{"scene":2}
ae_bilibili_fetch_dynamic_comments
### Purpose:
- Get comments on image and text dynamics.
### Parameters:
- Provide exactly one of dynamic_id and oid.
- dynamic_id: ID from the dynamic URL; identifies the comment section and type automatically.
- oid: Comment-section ID from data.data.item.basic.rid_str (comment_id_str in older responses); not the dynamic ID.
- comment_type: Only with oid; 11 for image posts (default), 17 for text. Omit when using dynamic_id.
- mode: 3 for hot, 2 for time.
- pagination_str: Leave empty for page one; then pass {"offset":"previous next_offset value"}.
### Response and pagination:
- data.data.replies: Comments; data.data.top_replies: Pinned comments.
- data.data.cursor.pagination_reply.next_offset: Use this string unchanged as the next offset.
- Stop pagination when data.data.cursor.is_end is true.
# [示例/Example]
dynamic_id = "DYNAMIC_ID"
mode = 3
pagination_str = ""
AE input example:
{"mode":3,"dynamic_id":"1172584638000922630"}
ae_telegram_batch_channel_info
### Purpose:
- Fetch basic info (title/description/avatar/subscribers/verified) for multiple public channels concurrently.
### Parameters:
- channels: Comma-separated channel usernames, up to 20 per request.
### Return:
- `data.results`: one `{channel, ok, info|error}` entry per channel.
# [示例/Example]
channels = "durov,telegram"
AE input example:
{"channels":"durov,telegram"}
ae_telegram_fetch_channel_search
### Purpose:
- Search posts in a channel by keyword (case-insensitive).
- Uses Telegram's server-side search over the full channel history when the MTProto backend
is enabled (`data.backend = "mtproto"`); otherwise falls back to best-effort local filtering
over recent history (`data.backend = "web"`).
### Parameters:
- channel: Channel username (required).
- query: Keyword (required).
- limit: Number of hits (1-100, default 20).
# [示例/Example]
channel = "durov"; query = "TON"
AE input example:
{"channel":"durov","query":"TON","limit":20}
ae_telegram_fetch_post_detail
### Purpose:
- Get a single public-channel post (parsed from the t.me embed view).
### Parameters:
- channel: Channel username (required).
- post_id: Post ID (required, auto-incremented integer within the channel).
### Return:
- A single post object (same structure as a `messages` element in fetch_channel_posts).
# [示例/Example]
channel = "durov"; post_id = 510
AE input example:
{"channel":"durov","post_id":510}
ae_bilibili_huahuo_search_live_upper
### Purpose:
- Search live creators for branded-content or live-commerce collaborations.
- Filter by creator attributes, audience demographics, live categories,
performance, guild, primary commerce category, and GMV.
### Parameters:
- `is_brand_live`: Live mode. Use `1` for branded-content live streams and
`0` for commerce live streams.
- Branded-content mode supports popularity peak, hourly viewers, hourly
comments, guild, and onboarding-status filters.
- Commerce mode supports primary category and 90-day GMV filters.
- `page`: One-based page number. Each page contains 20 records.
### Returns:
- `total_count`: Total number of matching creators.
- `data`: Creator records containing profile, audience, live performance,
and collaboration-capability metrics.
AE input example:
{"request_body":{"page":1}}