trade-show-fit-score

Lensmor Event Fit Score

Score a specific trade show against your company's profile using the Lensmor API to get a data-backed recommendation on whether to exhibit, attend, or skip.

When this skill triggers:

• Run the API key check (Step 1) before any API call
• Resolve the event_id for the named show if not already provided
• Call the fit-score endpoint and return a structured score card with decision band
• Pair with trade-show-finder for manual scoring or when Lensmor API access is unavailable

Use Cases

• Exhibit vs. skip decision: Get a quantified answer before committing budget
• Annual planning triage: Run multiple shows through fit-score to rank investment priorities
• Internal justification: Produce a data-backed score card to share with leadership

Example Requests

• Should we exhibit at this show?
• 这个展会值得参加吗
• Lohnt sich diese Messe?
• この展示会は合っている?
• ¿Vale la pena esta feria?

Request Handling

• Every Lensmor request, including event lookup and pagination, must send Authorization: Bearer $LENSMOR_API_KEY. Send the key only to https://platform.lensmor.com; never include it in URLs, output, or requests to company/event websites.
• Use a 10-second connection timeout and 30-second request timeout. Inspect the HTTP status before interpreting JSON; a non-2xx response, malformed JSON, or missing required response fields is a failed request, not an empty result or a zero score.
• Start with one page (page=1, pageSize at most 100). Preserve filters across pages and disclose partial coverage. Do not fetch every page automatically.
• For a read-only GET, allow at most one retry after a 429 or temporary 5xx, respecting Retry-After; if the delay is unavailable or impractical, report the failure and stop. Do not retry a POST automatically. A timeout may leave its outcome unknown, especially for a charged search.
• If event lookup returns multiple editions, ask for the intended year/edition before continuing. Use the resolved event ID, never a sample ID from this document.