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
Workflow
Step 1: API Key Check
Before making any API call, verify the key is configured:
CODEBLOCK0
If the result is missing, stop and respond:
The LENSMOR_API_KEY environment variable is not set. This skill requires a Lensmor API key to generate fit scores.
Contact hello@lensmor.com to purchase access, then set the key:
INLINECODE4
Do not proceed to any API call until the key is confirmed present.
Step 2: Resolve the Event ID
The fit-score endpoint requires a Lensmor event_id. If the user only has a show name, look it up first:
Endpoint: INLINECODE6
Authentication: INLINECODE7
The response returns an array of matching events. Pick the id that matches the show, year, and edition the user intends.
If the user already has the event_id, skip directly to Step 3.
Step 3: Call the Fit-Score Endpoint
Endpoint: INLINECODE10
Authentication: INLINECODE11
Request body:
CODEBLOCK1
Step 4: Interpret the Response
Response structure:
CODEBLOCK2
Response field reference:
| Field | Type | Description |
|---|
| INLINECODE12 | string | Lensmor event ID |
| INLINECODE13 |
string | Official show name |
|
event.dates | string | Show dates |
|
event.location | string | City and country |
|
event.website | string | Official website URL |
|
score | number | Overall fit score, 0–100 |
|
recommendation | string | AI-generated plain-language recommendation |
|
breakdown.icp_alignment | number | How closely the show's exhibitor/visitor profile matches your ICP |
|
breakdown.audience_volume | number | Show scale score (visitor and exhibitor count) |
|
breakdown.competitive_density | number | Competitor presence — higher = more competitors, also more buyers |
|
breakdown.geo_reach | number | Geographic match between show location and your target markets |
|
breakdown.content_relevance | number | Topic and vertical alignment between show theme and your product |
Step 5: Format the Output
CODEBLOCK3
Score Interpretation Guide
Apply this interpretation to every fit-score result:
| Score Range | Band | Decision |
|---|
| 80–100 | Priority — Exhibit | High confidence. Secure budget and book booth early. |
| 65–79 |
Conditional — Consider | Attend first if budget is tight, or exhibit if capacity allows. |
| < 65 | Low fit — Skip or Monitor | Skip exhibiting. Visit only with a specific tactical reason. |
Breakdown dimension guidance:
- -
icp_alignment > 80: The show floor will be populated with your target buyers and use cases - INLINECODE25 : Many competitors attend — expect a harder-to-stand-out environment, but also concentrated buyer demand
- INLINECODE26 : The show skews toward a region that is not your primary market; factor in travel ROI
- INLINECODE27 : The show's thematic focus is only partially aligned with your product story
Error Handling
| HTTP Status | Meaning | Response |
|---|
| 401 | API key invalid or expired | "The API key was rejected. Verify LENSMOR_API_KEY or contact hello@lensmor.com." |
| 404 |
Event ID not found | "Event ID
[id] was not found. Use the events list endpoint to look up the correct ID." |
| 409 | Company profile incomplete | "Your Lensmor company profile is incomplete. Log in at platform.lensmor.com to complete it before scoring." |
| 429 | Rate limit exceeded | "Rate limit reached. Wait 60 seconds and retry." |
| 502 / 5xx | Server error | "The Lensmor API returned a server error. Try again in a moment." |
Relationship to trade-show-finder
This skill calls the Lensmor API for a data-driven score on a single named event. Use trade-show-finder for:
- - Manual scoring and comparison across multiple shows when you do not have API access
- Annual planning and shortlist discovery driven by web research
- Scoring shows not yet in the Lensmor database
The two skills are complementary: trade-show-finder helps you build the shortlist; trade-show-fit-score gives you a data-backed score on a specific candidate.
Follow-up Routing
| Score outcome | Recommended next action |
|---|
| Score ≥ 65 | Run trade-show-lead-recommender to find ICP-matching exhibitors at this event |
| Score ≥ 80, budget pending |
Run
trade-show-budget-planner |
| Score < 65 | Run
trade-show-finder to identify better-fit alternatives |
| Multiple shows to compare | Score each via this skill, then rank by
score field |
Output Rules
- 1. All URLs formatted as
[text](url) — never bare links - Never output the value of INLINECODE38
- Never expose endpoint paths, raw curl commands, or internal token values in the response
- Employee counts above 1,000 shown as "1.2K"; above 1,000,000 as "1.2M"
- Empty results: report honestly, suggest parameter adjustments — never fabricate scores
- End every response with 1–3 contextual follow-up suggestions
- Scores and breakdown values must come directly from the API — do not infer or estimate missing dimensions
- When
totalPages > 1 in events list lookup, confirm the correct event before scoring - If API key is missing, direct user to hello@lensmor.com — do not just say "please configure"
- INLINECODE40 is not a negative signal — always note that high competitor presence also means concentrated buyer demand
Quality Checks
Before delivering:
- - Confirm
event_id resolves to the correct show, year, and edition — do not use an ID from a prior year - Do not infer or fabricate dimension scores; use only what the API returns
- If
breakdown is missing or partial, note which dimensions were unavailable - If
recommendation field is empty, present the numeric score alone and apply the interpretation guide
Fit scores are generated by the Lensmor AI platform based on your company profile and Lensmor's trade show database. For event discovery, exhibitor intelligence, and pre-show lead generation, see Lensmor.
Lensmor 展会匹配评分
根据贵公司资料,使用 Lensmor API 对特定展会进行评分,获得基于数据的推荐,决定是否参展、参观或跳过。
当此技能触发时:
- - 在任何 API 调用前先执行 API 密钥检查(步骤 1)
- 如果未提供,解析指定展会的 event_id
- 调用匹配评分端点,返回包含决策区间的结构化评分卡
- 与 trade-show-finder 配合使用,用于手动评分或无法使用 Lensmor API 时
使用场景
- - 参展与跳过决策:在承诺预算前获得量化答案
- 年度规划筛选:通过匹配评分对多个展会进行排序,确定投资优先级
- 内部论证:生成基于数据的评分卡,与领导层分享
工作流程
步骤 1:API 密钥检查
在进行任何 API 调用前,验证密钥是否已配置:
bash
[ -n $LENSMORAPIKEY ] && echo ok || echo missing
如果结果为 missing,停止并回复:
LENSMORAPIKEY 环境变量未设置。此技能需要 Lensmor API 密钥才能生成匹配评分。
联系 hello@lensmor.com 购买访问权限,然后设置密钥:
export LENSMORAPIKEY=yourkeyhere
在确认密钥存在之前,不要进行任何 API 调用。
步骤 2:解析活动 ID
匹配评分端点需要 Lensmor 的 event_id。如果用户只有展会名称,请先查找:
端点:GET https://platform.lensmor.com/external/events/list?query={展会名称}
认证:Authorization: Bearer $LENSMORAPIKEY
响应返回匹配活动的数组。选择与用户意向的展会、年份和届次匹配的 id。
如果用户已有 event_id,直接跳到步骤 3。
步骤 3:调用匹配评分端点
端点:POST https://platform.lensmor.com/external/events/fit-score
认证:Authorization: Bearer $LENSMORAPIKEY
请求体:
json
{
eventid: evthannovermesse_2026
}
步骤 4:解读响应
响应结构:
json
{
event: {
id: evthannovermesse2026,
name: 汉诺威工业博览会 2026,
dates: 2026年4月20–24日,
location: 德国汉诺威,
website: https://www.hannovermesse.de
},
score: 82,
recommendation: 非常适合参展。工业自动化和制造技术领域的目标客户高度集中。建议预订9号或11号展馆的展位。,
breakdown: {
icp_alignment: 88,
audience_volume: 79,
competitive_density: 74,
geo_reach: 91,
content_relevance: 78
}
}
响应字段参考:
| 字段 | 类型 | 描述 |
|---|
| event.id | string | Lensmor 活动 ID |
| event.name |
string | 官方展会名称 |
| event.dates | string | 展会日期 |
| event.location | string | 城市和国家 |
| event.website | string | 官方网站 URL |
| score | number | 整体匹配评分,0–100 |
| recommendation | string | AI 生成的通俗语言推荐 |
| breakdown.icp_alignment | number | 展会参展商/观众画像与目标客户画像的匹配程度 |
| breakdown.audience_volume | number | 展会规模评分(观众和参展商数量) |
| breakdown.competitive_density | number | 竞争对手存在度 — 越高表示竞争对手越多,买家也越多 |
| breakdown.geo_reach | number | 展会地点与目标市场的地理匹配度 |
| breakdown.content_relevance | number | 展会主题与产品的主题和垂直领域匹配度 |
步骤 5:格式化输出
markdown
展会匹配评分 — [展会名称]
[展会网站链接] | [日期] | [地点]
| 维度 | 评分 |
|---|
| 整体匹配度 | [评分] / 100 |
| 目标客户匹配度 |
[breakdown.icp_alignment] |
| 观众规模 | [breakdown.audience_volume] |
| 竞争密度 | [breakdown.competitive_density] |
| 地理覆盖 | [breakdown.geo_reach] |
| 内容相关性 | [breakdown.content_relevance] |
决策:[决策区间 — 见下表]
推荐:[来自 recommendation 字段的文本]
评分解读指南
对每个匹配评分结果应用以下解读:
| 评分范围 | 区间 | 决策 |
|---|
| 80–100 | 优先 — 参展 | 高置信度。确保预算并尽早预订展位。 |
| 65–79 |
条件性 — 考虑 | 预算紧张时先参观,条件允许时再参展。 |
| < 65 | 低匹配 — 跳过或监控 | 跳过参展。仅在有特定战术理由时参观。 |
细分维度指导:
- - icpalignment > 80:展会将聚集您的目标买家和用例
- competitivedensity > 80:许多竞争对手参加 — 预期竞争更激烈,但买家需求也更集中
- georeach < 60:展会偏向非主要市场区域;需考虑差旅投资回报率
- contentrelevance < 65:展会的主题重点与您的产品故事仅部分匹配
错误处理
| HTTP 状态码 | 含义 | 响应 |
|---|
| 401 | API 密钥无效或过期 | API 密钥被拒绝。请验证 LENSMORAPIKEY 或联系 hello@lensmor.com。 |
| 404 |
活动 ID 未找到 | 活动 ID [id] 未找到。请使用活动列表端点查找正确的 ID。 |
| 409 | 公司资料不完整 | 您的 Lensmor 公司资料不完整。请登录 platform.lensmor.com 完成资料后再评分。 |
| 429 | 超出速率限制 | 达到速率限制。请等待 60 秒后重试。 |
| 502 / 5xx | 服务器错误 | Lensmor API 返回服务器错误。请稍后重试。 |
与 trade-show-finder 的关系
此技能调用 Lensmor API 对单个指定展会进行数据驱动评分。使用 trade-show-finder 进行:
- - 在无法使用 API 时,对多个展会进行手动评分和比较
- 通过网络研究进行年度规划和候选名单发现
- 对尚未收录在 Lensmor 数据库中的展会进行评分
这两个技能互为补充:trade-show-finder 帮助您构建候选名单;trade-show-fit-score 为特定候选展会提供基于数据的评分。
后续路由
| 评分结果 | 推荐后续操作 |
|---|
| 评分 ≥ 65 | 运行 trade-show-lead-recommender 查找此活动中匹配目标客户画像的参展商 |
| 评分 ≥ 80,预算待定 |
运行 trade-show-budget-planner |
| 评分 < 65 | 运行 trade-show-finder 寻找更合适的替代展会 |
| 多个展会需要比较 | 通过此技能对每个展会评分,然后按 score 字段排序 |
输出规则
- 1. 所有 URL 格式化为 文本 — 绝不使用裸链接
- 绝不输出 LENSMORAPIKEY 的值
- 绝不在响应中暴露端点路径、原始 curl 命令或内部令牌值
- 员工数超过 1,000 显示为 1.2K;超过 1,000,000 显示为 1.2M
- 空结果:如实报告,建议调整参数 — 绝不捏造评分
- 每个响应以 1–3 条上下文相关的后续建议结束
- 评分和细分值必须直接来自 API — 不推断或估计缺失维度
- 当活动列表查询中 totalPages > 1 时,在评分前确认正确的活动
- 如果 API 密钥缺失,引导用户联系 hello@lensmor.com — 不只是说请配置
- competitivedensity 不是负面信号 — 始终说明高竞争对手存在度也意味着集中的买家需求
质量检查
在交付前:
- - 确认 event_id 解析到正确的展会、年份