The Pkg.go.dev API
The pkg.go.dev API has been launched to provide programmatic access to Go module metadata. This development addresses the community's need for a stable and efficient way to access package information without relying on web scraping. The API is designed for precision and offers various endpoints for retrieving specific data about packages and modules.
- ▪The pkg.go.dev API allows developers to query metadata about published Go modules.
- ▪It features a stateless, GET-only architecture with primary endpoints hosted under the /v1beta path.
- ▪The API requires unambiguous specification of modules to avoid errors in ambiguous package paths.
2 outlets in our directory ran this story, first to last over 10 hours. All of the coverage we found sits in one bucket: centre. That one-sidedness is itself worth noticing.
Hacker News (Newest) files mainly under programming. We currently carry 5,306 of its stories.
Story provenance
Source · retrieval · rights · ranking — open for full record
inspect →
Story provenance
Attribution is not the same as permission. This drawer separates discovery metadata, excerpts, WeSearch-generated summaries, reuse status, and whether the publisher receives the visit. Nothing here claims a legal grant the publisher has not made.
Record
| Original publisher | Go |
| Canonical URL | https://go.dev/blog/pkgsite-api |
| Publication time | Fri, 22 May 2026 20:57:32 +0000 |
| Retrieval time | 2026-05-22T21:02:03.031Z |
| Last seen | 2026-05-22T21:02:03.031Z |
| Headline source | Publisher (no WeSearch rewrite) |
| Excerpt source | publisher body |
| Excerpt method | First ~120 words (~800 chars) of extracted publisher body, fair-use limited. |
| Summary | WeSearch · cerebras-chat (WeSearch summarizer) |
| Summary source text | contentText |
| Citation coverage | Summary is a WeSearch-generated derivative; primary citation is the original publisher URL. |
| Cluster | eGHShqDx73_0 · 2 stories |
| Cluster logic | Grouped by semantic title/content similarity across sources within a rolling window. Same-publisher template collisions are excluded from coverage comparison. |
| Ranking reason | Story pages are not engagement-ranked. Hub feeds use recency, with optional source-diversified chronological ordering (cap consecutive stories per source). No personalized ranking. |
| Publisher visit | Yes — open original |
| Substitutes article? | No — link-out required for full text |
Rights status (four layers)
WeSearch handling by dimension
| Indexing | May the item be indexed (stored, ranked, made findable)? | Allowed |
| Snippet | May a short excerpt of the publisher's text be shown? | Allowed |
| AI summary | May WeSearch generate its own short summary of the article? | Limited |
| Retrieval / RAG | May the content be exposed for third-party retrieval-augmented generation? | Not asserted |
| Model training | May the content be used to train AI models? | Not asserted |
| Commercial reuse | May the content be reused commercially? | Not permitted |
Basis: Derived from the published RSS/Atom feed. Contact: [email protected]. Reviewed: 2026-07-24.
Opening excerpt (first ~120 words) tap to expand
The Go Blog Introducing the pkg.go.dev API Ethan Lee, Hana Kim, and Jonathan Amsterdam 21 May 2026 Since its inception, pkg.go.dev has established itself as the Go community’s primary resource for package documentation and discovery. While we initially prioritized creating a comprehensive and highly accessible web interface for users, the need for programmatic access has become increasingly clear. Developers building tools, IDE integrations, and automated workflows have historically relied on fragile workarounds like web scraping to access this data. To better address these evolving requirements, we are now expanding our platform to provide robust, direct access to the information our community needs.
…
Excerpt limited to ~120 words for fair-use compliance. The full article is at Go.
Discussion
0 commentsMore from Go
