Skip to main content
get/v2/libs/metrics
Request example
Response
get/v2/libs/metrics

Authorization

Authorizationstringheaderrequired#
Get your API key at context7.com/dashboard. Treat your API key like a password and store it securely. Every key can read the management API (/v2/teamspaces/*), except personal data: member and invitation emails, library requesters, visitor questions, Docs7 reader searches, conversations, feedback and feature requests, and the GitHub account behind a build. To read those or make changes there, the key must be created with Write access ticked; other keys get 403 write_access_required.

Query parameters

libraryIdstringrequired#
Context7-compatible library ID — the URL path of the library on context7.com. Use /owner/repo for GitHub repositories, or /<source>/<id> for other sources (websites, llms.txt, GitLab/Bitbucket, etc.). Optionally suffix with /<version> or @<version> to pin a specific version. See Library ID format.

Length: 1–500Pattern: ^/[^/]+/[^/]+([/@][^/]+)?$

daysinteger#
Number of days of daily history to return (1-365). Defaults to 30.

Default: 30

Range: 1–365

Responses

application/json
Library usage metrics
totalobjectrequired#
Cumulative request counts for a library, broken down by request surface
dailyobject[]required#
Per-day request counts (deltas, not cumulative), ordered from oldest to newest. Days with zero activity are omitted. Up to days points — fewer if the library has less history or had idle days in the window.
mcpClientsobjectrequired#
MCP client usage breakdown by day
topicsobject[]required#
Lifetime topic distribution, ordered by count descending
countriesobject[]required#
Lifetime country distribution (ISO-2 codes), ordered by count descending