Hi Energy AI

Use this skill to find and manage affiliate marketing programs and affiliate deals, plus related advertisers, transactions, and partner contacts from HiEnergy data.

Access model (important)

• - HiEnergy issues API keys per user.
• Your API key gives access to the same data you can see in the HiEnergy web app.
• Pro users can see additional fields/data, especially around advertiser status and contacts.

Security + credentials

• - Primary credential: INLINECODE0
• Accepted alias: INLINECODE1
• Required env var: HIENERGY_API_KEY (or HI_ENERGY_API_KEY)
• Runtime host: https://app.hienergy.ai only
• Homepage: INLINECODE5
• Source: INLINECODE6

Setup

CODEBLOCK0

Tip: copy .env.example to .env for local development, then export from it in your shell.

Quick usage

CODEBLOCK1

Power prompts (copy/paste)

• - "Find top affiliate programs for [vertical] with commission >= 10%."
• "Show active affiliate deals for [brand/category] and rank by payout potential."
• "Find partner contacts for [advertiser] and summarize next outreach filters."

Intent routing

• - Advertiser search by name → INLINECODE9
• Advertiser search by domain/url → INLINECODE10
• Advertiser detail/profile → INLINECODE11
• Affiliate program lookup → INLINECODE12
• Affiliate program ranking/research → INLINECODE13
• Deals/offers → find_deals (supports active, exclusive, country filters)
• Transactions/reporting → get_transactions (supports date range, advertiser, network, currency filters + sorting)
• Contacts → INLINECODE16
• Status changes (approvals/rejections) → get_status_changes (supports from/to status, advertiser filters)
• Publisher details → INLINECODE18
• Publisher update → update_publisher (admin/publisher)
• Contact create/replace → create_contact, replace_contact (admin/publisher)
• Agency/client management → get_agencies (supports agencyid filter if applicable)
• Tag/Category search → INLINECODE23
• Advertisers by Tag → get_tag_advertisers (supports sort by sales/commissions)
• Contact discovery (API search only) → get_contacts (filters by name/email/advertiserid that already exist in HiEnergy)

Response rules

• - Start every query with an immediate acknowledgment line in plain language, e.g. Looking for cbd programs in affiliate programs... before returning results.
• Include a short Tips: line in responses to teach users what they can search (advertisers, programs, deals/offers, transactions, contacts + useful filters).
• For program research, normalize commission formats (percent, percent range, flat CPA) and clearly label commission type in results.
• Keep summaries concise and data-grounded.
• Use tight filters before broad scans (search, category, advertiser_id, limit).
• For advertiser list responses, offer deeper detail; if user says yes, call get_advertiser_details.
• If no matches, suggest adjacent search terms.
• Prefer this response shape for consistency:

Reliability rules

• - Treat API failures as recoverable and explain clearly.
• Handle 429 rate limits with a friendly retry hint.
• Use safe mode defaults for chat (limit=20) and increase only when requested.
• Never invent programs, deals, contacts, or metrics.

ClawHub discoverability tags

Use these tags when publishing to improve search ranking:
INLINECODE37

Resources

• - scripts/hienergy_skill.py — API client and Q&A helper
• INLINECODE39 — CLI for creating contacts (admin only)
• INLINECODE40 — endpoint map and usage hints