← Back to Skills Marketplace
nomadcalendar

Belong Events - Discover and Organize

by Belong · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ✓ Security Clean
755
Downloads
2
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install belong-events
Description
Discover events and hubs, manage branding, CheckIn venues, bracelets, wallets, and NFT tickets on the Belong platform
README (SKILL.md)

Belong Events

Discover events and hubs, buy tickets, create events and communities, manage hub branding, and handle venue check-ins, bracelets, and referral flows on Belong.

How to call tools

Run {baseDir}/invoke.sh \x3Cmethod> '\x3Cparams-json>' via system.run. The script calls the Belong skill API and returns JSON.

Example:

system.run {baseDir}/invoke.sh discover_events '{"city":"Miami","limit":5}'

All tool calls use this pattern. The invoke.sh script handles endpoint URL, authentication headers, validates method names, and streams the JSON-RPC body over stdin instead of interpolating user params into curl arguments.

Default endpoint: https://join.belong.net/functions/v1/openclaw-skill-proxy

Network disclosure:

  • All JSON-RPC calls are sent to the endpoint above (or BELONG_EVENTS_ENDPOINT if overridden).
  • If BELONG_EVENTS_API_KEY is set, it is sent to that endpoint as X-OpenClaw-Key.

Account linking (required for protected tools)

Most tools require a linked Belong account. If any tool returns "Belong account not linked" or "BELONG_LINK_REQUIRED", run the OTP flow:

  1. Ask the user for their email address.
  2. Send OTP:
    system.run {baseDir}/invoke.sh belong_email_otp_send '{"email":"USER_EMAIL"}'
    
  3. Ask for the 6-digit code from their email.
  4. Verify OTP:
    system.run {baseDir}/invoke.sh belong_email_otp_verify '{"email":"USER_EMAIL","otp":"CODE"}'
    
  5. The response includes apiKey. Store it — set it as BELONG_EVENTS_API_KEY env var or update skills.entries.belong-events.apiKey in openclaw.json so subsequent calls are authenticated.

Never ask end users for an API key. Always use the OTP flow.

Available tools

Public (no auth needed)

Public tools are rate-limited. If you hit a 429, wait and retry.

  • list_tools — List available tools (no params)
  • discover_events — Search events. Params: city, category, startDate, endDate, limit, latitude, longitude (all optional)
  • discover_hubs — Search public hubs. Params: search, hubType, limit, cursor
  • get_event_details — Get event details. Params: eventId (required), source, city, latitude, longitude (optional)
  • get_hub_details — Get hub details. Params: hubId (required), includeEvents, includeBranding
  • get_hub_branding — Get hub branding. Params: hubId (required)
  • buy_ticket — Get checkout/event URL. Params: eventId (required), tierId, quantity
  • get_checkin_leaderboards — Load public venue and attendee leaderboards. Params: limit, timeframe (all, today, week, month)
  • belong_email_otp_send — Send OTP. Params: email (required)
  • belong_email_otp_verify — Verify OTP. Params: email (required), otp (required)

Account status (auth required)

  • whoami — Check link status (no params)
  • get_profile — Get the linked Belong profile
  • list_wallets — List linked crypto wallets
  • sync_wallets — Sync wallets from the configured provider
  • get_referral_code — Get or create the linked wallet referral code. Params: chainId (required), walletAddress, createIfMissing

Attendee (auth required)

  • my_tickets — List purchased tickets. Params: status (upcoming/past/all). Returns ticketCheckinUrl for each ticket.
  • my_checkins — List the linked user’s check-in history and stats. Params: limit, offset

Organizer (auth required)

  • create_event — Create event. Params: name (required), startDate (required), endDate (required), description, city, venue, category, hubId, coverImage
  • update_event — Update event. Params: eventId (required), name, description, startDate, endDate, city, venue, category, hubId, coverImage
  • add_event_media — Upload event media. Params: eventId (required), files (required base64 file array)
  • update_event_media — Replace/reorder event media. Params: eventId (required), media (required)
  • delete_event_media — Delete event media. Params: eventId (required), mediaId (required)
  • deploy_tickets — Deploy NFT tickets. Params: eventId (required), tierName (required), price (required), maxSupply, chainId, transferable, gasless. Two-phase: first call returns tx params, second call with collectionId+txHash completes deployment.
  • my_events — List owned events. Params: status (upcoming/past/draft/all)
  • event_analytics — Event stats. Params: eventId (required)
  • create_hub — Create hub/community. Params: name (required), slug, description, location, private, hubType, startDate, endDate, coverImage, communitySkinConfig, customDomains
  • update_hub — Update hub/community. Params: hubId (required), name, slug, description, location, private, hubType, startDate, endDate, coverImage, connectEventIds, categorySubEventIDs, communitySkinConfig, customDomains
  • my_hubs — List owned or joined hubs. Params: search, hubType
  • configure_hub_branding — Save hub branding and custom domains. Params: hubId (required), communitySkinConfig, customDomains

Venue (auth required)

  • check_in — Process check-ins, quoted venue payments, or owner approvals. Params: hubId (required), accessMode, amount/paymentAmount, paymentCurrency, paymentTxHash/paymentTransactionHash, paymentChainId, latitude, longitude, promoterCode, promoterAddress, promoterWallet, pendingCheckinId, nftTokenId, nftContractAddress, linkedEventId, customerWallet, listPending, checkinId, action, description
  • list_pending_checkins — List pending venue approvals. Params: hubId (required), limit, checkinId
  • approve_checkin — Approve, reject, or quote. Params: checkinId (required), action, amount, currency, description
  • get_venue_info — Load venue settings, stats, and on-chain venue info. Params: hubId (required), venueAddress, chainId, includeStats. chainId must come from the explicit param or persisted venue settings.
  • configure_venue — Update venue rules and sync to MCP. Params: hubId (required), venueWallet, ownerAddress, chainId, verificationMethod, requireVenueApproval, venueLatitude, venueLongitude, checkinRadius, primaryAccessMode, accessModeFree, accessModeVenuePayment, accessModeNftTicket, accessModeNftMembership, venuePaymentFlow, minCheckAmount, fixedPaymentAmount, acceptUSDC, acceptLONG, longSettlement, enableVisitorRewards, visitorVisitBountyUsd, visitorSpendPercentage, enablePromoterRewards, promoterVisitBountyUsd, promoterSpendPercentage, dailyCheckinLimit, requiredNftCollections, braceletEnabled, braceletDisplayCurrency, braceletAcceptedTokens, braceletMinTopup, braceletMaxTopup, braceletAllowRefunds, braceletChargeCategories, braceletPoolWallet
  • get_venue_checkin_history — Load owner-scoped row-level venue history. Params: hubId (required), limit, offset
  • get_owner_checkin_stats — Load owner dashboard stats. Params: days
  • deposit_venue_funds — Prepare a venue deposit transaction. Params: hubId (required), amount (required), venueWallet, ownerAddress, chainId, promoterAddress
  • pay_to_venue — Prepare a customer venue payment transaction. Params: hubId (required), amount (required), venueAddress, walletAddress, promoterAddress, chainId
  • setup_venue_rewards — Configure rewards. Params: hubId (required), visitBounty, visitorSpendPercentage, cashbackPercent (legacy alias)
  • get_bracelet_balance — Load bracelet balance and recent transactions. Params: braceletUid, eventHubId
  • link_bracelet — Link a bracelet to the authenticated attendee. Params: braceletUid, eventHubId, displayName
  • topup_bracelet — Credit a bracelet after a verified payment. Params: braceletUid, eventHubId, amount, currency, txHash, chainId, displayAmount, displayCurrency, conversionRate
  • charge_bracelet — Charge a bracelet with staff PIN authorization. Params: braceletUid, eventHubId, amount, currency, staffPin, displayAmount, displayCurrency, conversionRate, description, chargeCategory, idempotencyKey
  • refund_bracelet — Refund bracelet balance. Params: braceletUid, eventHubId, currency, amount, refundToAddress, idempotencyKey
  • get_bracelet_event_summary — Load organizer cashless summary. Params: eventHubId
  • withdraw_earnings — Withdrawal link. Params: hubId (required), currency (USDC/LONG)
Usage Guidance
This skill appears coherent with its stated purpose, but you should: (1) confirm you trust Belong (requests go to join.belong.net by default) before providing an email/OTP or allowing the skill to store an apiKey; (2) prefer the OTP flow as documented instead of pasting API keys; (3) be aware that authenticated calls will send any provided params (event details, wallet addresses, etc.) to the Belong endpoint; and (4) note the skill's source/homepage are not provided—if you need stronger assurance, ask the publisher for a canonical source or inspect a signed release before enabling it in production.
Capability Analysis
Type: OpenClaw Skill Name: belong-events Version: 1.0.2 The belong-events skill is a legitimate integration for the Belong platform, providing tools for event management, ticketing, and venue check-ins. It uses a shell script (invoke.sh) to wrap JSON-RPC calls to a specific API endpoint (join.belong.net) and handles authentication through a standard OTP flow described in SKILL.md. The code follows safe practices, such as validating method names and passing request bodies via stdin to curl to avoid shell injection.
Capability Tags
cryptorequires-walletcan-make-purchasesrequires-sensitive-credentials
Capability Assessment
Purpose & Capability
Name/description (discover/manage events, hubs, tickets, check-ins, wallets) align with the provided tooling and methods. Required binary (curl) and primary credential BELONG_EVENTS_API_KEY are appropriate for calling a remote Belong API gateway.
Instruction Scope
SKILL.md confines runtime behavior to calling the included invoke.sh wrapper and performing an OTP account-link flow. It does not instruct reading arbitrary local files or exfiltrating data to unexpected endpoints; all network calls target the Belong gateway (or an override endpoint). It does instruct storing the returned apiKey in an env var or openclaw.json for subsequent authenticated calls, which is expected for account linking.
Install Mechanism
No install spec (instruction-only) and a small, non-obfuscated invoke.sh script that posts JSON-RPC to a Belong domain. No downloads or archive extraction are used.
Credentials
Only the primary credential BELONG_EVENTS_API_KEY (and an optional BELONG_EVENTS_ENDPOINT) are used. There are no unrelated credentials or high-privilege env vars requested. The skill asks for the user's email and OTP during account linking — expected for the described flow — and explicitly instructs never to ask users for manual API keys.
Persistence & Privilege
Skill does not request always:true and does not require elevated system privileges. It suggests storing the apiKey in the agent config or env var for convenience, which is normal for authenticated integrations; it does not modify other skills or system-wide settings.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install belong-events
  3. After installation, invoke the skill by name or use /belong-events
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
Version 1.0.2 - Added CLAWHUB_DEPLOY.md and openclaw.json.example files. - Expanded event management to include hubs, branding, venues, bracelets, wallets, and NFT ticketing. - Added support for discovering hubs, creating/updating hubs, and managing hub branding. - Updated and expanded organizer and venue-related tools, including hub and venue configuration. - Improved tool invocation: method names are now validated, and JSON-RPC bodies are streamed over stdin. - Documentation updated to reflect all new and extended features.
v1.0.1
- Added documentation for the default API endpoint and the option to override it with the BELONG_EVENTS_ENDPOINT environment variable. - Updated metadata to include BELONG_EVENTS_ENDPOINT as an optional environment variable. - Added a clear network disclosure section describing API endpoints and key usage. - No changes to tool methods or functionality.
v1.0.0
Initial release of Belong Events skill. - Create, discover, and manage events with NFT tickets on the Belong platform. - Supports event discovery, purchase, and detailed event management for organizers and venues. - Includes account linking via email OTP for access to protected features. - Offers a full toolset for attendees, organizers, and venue managers, including ticket purchasing, event creation, attendee check-ins, and analytics. - Easy integration with bash via an invoke script; all API authentication and JSON handling are managed internally.
Metadata
Slug belong-events
Version 1.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is Belong Events - Discover and Organize?

Discover events and hubs, manage branding, CheckIn venues, bracelets, wallets, and NFT tickets on the Belong platform. It is an AI Agent Skill for Claude Code / OpenClaw, with 755 downloads so far.

How do I install Belong Events - Discover and Organize?

Run "/install belong-events" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is Belong Events - Discover and Organize free?

Yes, Belong Events - Discover and Organize is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does Belong Events - Discover and Organize support?

Belong Events - Discover and Organize is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created Belong Events - Discover and Organize?

It is built and maintained by Belong (@nomadcalendar); the current version is v1.0.2.

💬 Comments