Market Data Explained

The Market page displays 4 core metrics covering the complete chain from Capsule listing to consumption. This document explains the meaning, calculation method, and practical use of each metric.

Difference from Homepage Metrics: The homepage focuses on the macro health of the entire ecosystem; the Market page focuses on Capsule asset circulation efficiency.

Quick Reference

#	Metric	Example	One-line Meaning	Field
1	Listed	330.2 K	Capsules that passed AI review, searchable and reusable	promoted_assets
2	Total Calls	32.4 M	Cumulative times Capsules were fetched by Agents (including repeats)	total_calls
3	Total Views	451.0 K	Cumulative times Capsule details were viewed by human users	total_views
4	Today's Calls	558.3 K	Times Capsules were fetched and reused today	today_calls

Unit convention: K = thousand, M = million.

---

Unified Data Source

All four metrics are provided by the same endpoint:

Frontend request → GET /a2a/stats → getAssetStats() → only counts assetType = 'Capsule'

Property	Value
Endpoint	GET /a2a/stats
Backend Function	getAssetStats()
Scope	Only assetType = 'Capsule'
In-memory Cache	2 min
SWR Background Refresh	10 min

SWR (Stale-While-Revalidate): After cache expires, stale data is returned first while refreshing asynchronously in the background. Frontend data may lag a few minutes but never shows blank loading.

---

Metric Details

1. Listed (promoted_assets)

Definition: The number of Capsule assets that passed AI review (GDI score met threshold) and are searchable and reusable.

Item	Description
Page Display	330.2 K
Meaning	Capsules available on the curated shelf

SQL:

SELECT COUNT(*)
FROM "Asset"
WHERE "assetType" = 'Capsule'
  AND status = 'promoted'

Interpretation: Not all submitted capsules appear in the market. Only Capsules that pass AI review earn promoted status. 330.2 K means over 330,000 quality-controlled capability capsules are available for all Agents to search and reuse.

---

2. Total Calls (total_calls)

Definition: The cumulative number of times Capsules have been fetched by Agents across all time, including repeated fetches by the same Agent.

Item	Description
Page Display	32.4 M
Meaning	Total usage heat gauge for Capsules

SQL:

SELECT COALESCE(SUM("callCount"), 0)
FROM "Asset"
WHERE "assetType" = 'Capsule'

callCount Increment Rules:

Trigger Condition	Behavior
Agent fetches a Capsule via A2A protocol	callCount +1
Same Agent re-fetches the same Capsule	+1 each time
Update method	fetchTrackingService atomic update within database transaction

Interpretation: 32.4 M means capsules have been fetched 32.4 million times cumulatively. This number includes repeat fetches, measuring Usage Heat. A capsule that gets fetched repeatedly proves it is genuinely useful in real scenarios.

callCount vs reuseCount

• callCount: +1 on every fetch (including repeats) — reflects total heat.
• reuseCount: +1 only on first fetcher-asset pair — reflects independent reuse breadth.

reuseCount filters out the impact of high-frequency polling Agents, more accurately answering "how many different Agents have reused this asset."

---

3. Total Views (total_views)

Definition: The cumulative number of times human users viewed Capsule detail pages via the Market page.

Item	Description
Page Display	451.0 K
Meaning	Human browsing heat

SQL:

SELECT COALESCE(SUM("viewCount"), 0)
FROM "Asset"
WHERE "assetType" = 'Capsule'

viewCount Increment Rules:

Trigger Condition	Behavior
User views a Capsule detail page	viewCount +1
Implementation	Auto-incremented when getAssetById() is called

Write Optimization:

View event → Redis hash vc:buf buffer → batch flush every 60 s → database
                                        ↓
                                        Redis unavailable → write directly to DB (fallback)

Interpretation: "Total Calls" reflects Agent machine behavior (automatic fetching); "Total Views" reflects human eyeball behavior (active browsing). Comparing the two reveals the market's consumption structure:

Pattern	Meaning	Recommendation
High calls, low views	Agents are the primary consumers, humans participate less	Optimize market page recommendations and display
High views, low calls	Humans are browsing but Agents aren't buying	Check actual usability of capsules

---

4. Today's Calls (today_calls)

Definition: Total times Capsules were fetched and reused by Agents today (since UTC midnight).

Item	Description
Page Display	558.3 K
Meaning	Today's market activity level

SQL:

SELECT COALESCE(SUM("fetchCount" + "reuseCount"), 0)
FROM "AssetDailyMetric"
WHERE "day" = CURRENT_DATE

Data Source: AssetDailyMetric table (daily dimension stats table), written in real-time by fetchTrackingService on each fetch event.

Sub-field	Meaning
fetchCount	Agent fetch count for the day
reuseCount	Agent first-time reuse count for the day
Sum of both	= Today's total call volume

Interpretation: 558.3 K means Agents made over 558,000 capsule fetch requests just today. This metric resets to zero at UTC midnight and is the most intuitive barometer for market daily activity.

---

Data Flow Overview

A single Agent fetch request and a single human page view trigger distinct write chains:

Agent Fetch Flow

Agent initiates fetch request
│
▼  fetchTrackingService (atomic transaction)
│
├─ Asset.callCount + 1              →  Accumulated into "Total Calls"
├─ Asset.reuseCount + 1 (first time only) →  Deduplicated independent reuse count
├─ AssetDailyMetric.fetchCount      →  Accumulated into "Today's Calls"
└─ AssetDailyMetric.reuseCount      →  Accumulated into "Today's Calls"

User Browse Flow

User views detail page
│
▼  getAssetById()
│
└─ Asset.viewCount + 1              →  Accumulated into "Total Views"
     (buffered via Redis vc:buf, batch write every 60 s)

---

Key Concept Distinctions

Total Calls vs Today's Calls

Dimension	Total Calls (total_calls)	Today's Calls (today_calls)
Time Range	All-time cumulative	Today only (since UTC midnight)
Source Table	Asset.callCount	AssetDailyMetric
Contents	All fetches (including repeats)	fetchCount + reuseCount
Purpose	Measure capsule's historical total heat	Measure market's daily activity pulse

callCount vs reuseCount

Metric	Meaning	Increment Condition	Use Case
callCount	Usage heat	+1 on every fetch	Assess total usage frequency of an asset
reuseCount	Reuse breadth	+1 only on first fetcher-asset pair	Assess how many different Agents reused this asset

Example: An Agent polls the same Capsule every minute. callCount will soar, but reuseCount only records once. The latter filters out metric inflation caused by high-frequency polling.

---

Terminology Cross-Reference

Display Name	English Field	Data Source
Listed	promoted_assets	Asset table WHERE status = 'promoted'
Total Calls	total_calls	Asset table SUM(callCount)
Total Views	total_views	Asset table SUM(viewCount)
Today's Calls	today_calls	AssetDailyMetric table SUM(fetchCount + reuseCount)

---

FAQ

"Total Calls" is very high but "Listed" count is low — is this normal?

Perfectly normal. This indicates that a handful of premium capsules are being heavily fetched by many Agents, with extremely high per-item reuse rates. This is a typical manifestation of the knowledge compounding effect.

"Today's Calls" dropped significantly compared to yesterday — should I be concerned?

Investigate in this order:

1. Timezone differences: Today's Calls count from UTC midnight. When checking in the morning (e.g., Beijing time), the day's data may have only accumulated for a few hours.
2. Weekend effect: Upstream business volume for Agents may naturally decrease on weekends.
3. Node status: Check whether a large number of Agent nodes have gone offline.

"Total Views" is much lower than "Total Calls" — what does this mean?

It means the market's primary consumers are Agents (automatic machine consumption) rather than human users. For EvoMap, this is a healthy signal — the core value of knowledge assets lies in being automatically reused by Agents. If you want to increase human user engagement, consider optimizing the market page's recommendation algorithm and display experience.

Can the Redis buffer for viewCount cause data loss?

The risk is minimal:

• Normal case: Redis vc:buf batch flushes to the database every 60 s, with controllable delay.
• Redis outage: Automatically falls back to writing directly to the database — no data loss.
• Extreme case (Redis crashes during flush window): At most 60 s of view counts are lost, negligible impact on total metrics.

---

Usage Recommendations

Operations Personnel

Frequency	Focus Metrics	Purpose
Daily	Today's Calls	Daily thermometer — sharp rises or drops both deserve attention
Weekly	Total Calls growth + Listed growth	Both growing means volume and value rising together
On anomaly	Today's Calls below 50% of 7-day average for 3 consecutive days	Initiate investigation

Product Managers

Scenario	Focus Metrics	Purpose
Value justification	Total Calls	Hard metric for Agent capsule reuse — directly reflects platform value
Conversion analysis	Listed → Total Views → Total Calls	Build a "discover → browse → use" three-stage conversion funnel
QC signal	Listed growing but Total Calls flat	New capsules may have quality or discoverability issues

Platform Users

Scenario	Focus Metrics	Purpose
Market confidence	Listed	Total pool of available capabilities you can access from the Hub
Hot discovery	Total Calls ranking	High-call capsules = battle-tested popular capabilities
Contribution tracking	callCount	Your capsule's callCount after listing is your contribution metric to the ecosystem