AI Tool Profile

pkg.go.dev API: Endpoints, Limits, Risks, and Evaluation

The pkg.go.dev v1 API provides GET-only JSON access to search, package, module, symbol, version, vulnerability and imported-by metadata for the Go ecosystem.

Before you buy

Best for: Go developers, IDE and coding-assistant builders, dependency tools and researchers that need structured package metadata without scraping rendered pages.

Price: Public API; no separate subscription identified

Included: Documented Go package metadata endpoints.

Main limits: The documented rate limit is 45 requests per second per IP block. Caching, error handling and model costs remain the integrator’s responsibility.

What Kingy showed: Related coverage: Should You Try pkg.go.dev API? A Practical AI Launch Review. This review does not treat that article as a new test of this exact model, plan or current release.

Buying details checked 2026-10-23 with region and currency stated above. Historical demonstrations and the broader fact ledger keep their own dates.

Check official plans · See the demonstration and disclosure · Compare these workflows

Source recheck dueFrameworkProfile source check: 2026-07-28

Coverage describes this profile, not a product score or a current price guarantee.

A mechanical catalog sorts software packages through distinct metadata channels

Kingy AI Product Facts

pkg.go.dev API

Current statusUnknown

Company
Not yet reviewed
Primary job
Not yet reviewed
Audience
Not yet reviewed
Evidence
Source-backed; coverage expanding
Latest source check
October 23, 2026
See all tracked product factsPricing, platforms, dependencies, data claims, regions, and timeline

Sources and checks

Coverage
1 of 87 tracked fields currently verified
Sources
1

Source-check dates apply to the tracked facts. Editorial updates elsewhere on this page may have a different date.

Plans and pricing units

Not yet structured in this Kingy record.

Where it runs

Availability
Not yet reviewed

Stack and integrations

Model / provider dependencies
Not yet reviewed
Integrations
Not yet reviewed

Data and regions

Vendor data-use claim
Not yet reviewed
Vendor retention claim
Not yet reviewed
Regions
Not yet reviewed

Launch and latest material update

Launch
Not yet reviewed
Latest material update
Not yet reviewed
Review history
  1. pkg.go.dev API: Endpoints, Limits, Risks, and Evaluation — Product Facts updated

    Kingy published an approved change to this Product Facts record.

    View published revision
Technical evidence and revision history
Embed “Facts tracked by Kingy”

This label is not a security certification, audit, or product endorsement. It reports the facts Kingy currently supports and when they were last checked.

Who should consider it

Go developers, IDE and coding-assistant builders, dependency tools and researchers that need structured package metadata without scraping rendered pages. The pkg.go.dev v1 API provides GET-only JSON access to search, package, module, symbol, version, vulnerability and imported-by metadata for the Go ecosystem.

Plan, price and billing scope

Public API; no separate subscription identified. Documented Go package metadata endpoints. Prices use the currency and billing term stated here. Where a numeric rate, region or current entitlement could not be verified, it remains explicit; no checkout was completed.

Limits that affect the decision

The documented rate limit is 45 requests per second per IP block. Caching, error handling and model costs remain the integrator’s responsibility.

What the existing evidence shows

Related coverage: Should You Try pkg.go.dev API? A Practical AI Launch Review. This review does not treat that article as a new test of this exact model, plan or current release. Product coverage; original publication date and evidence scope retained. Read the related article.

Sources and buying-review date

Buying review completed October 23, 2026. This is a source-based buying assessment. No paid product test, new generation, checkout or performance benchmark was performed. Vendor descriptions and historical examples remain distinct from independently measured results. The date does not renew the broader canonical fact ledger.

Check the official offer · Compare related options

Earlier profile, sources and dates

This older record retains its original scope. Current buying qualifications above take precedence where terms have changed.

Kingy verdict: The pkg.go.dev API is the official structured route to Go package, module, symbol, version, vulnerability and imported-by metadata. It is a better foundation than scraping rendered pages, especially for coding assistants and dependency tools, and the current reference documents v1 routes. Build around explicit versioning, pagination, caching, rate-limit handling and evidence links to the package record.

What changed

The Go Team announced the public API on June 12, 2026. The reference exposes GET-only JSON endpoints for search and package ecosystem metadata, including package and module records, symbols, versions, known vulnerabilities and imported-by relationships. An official OpenAPI document provides a machine-readable contract. That creates a supported integration surface for tools that previously had to parse HTML or assemble equivalent data from several systems.

The API is deliberately read-only and described as stateless. Responses use pagination tokens where relevant, and the live reference documents a rate limit of 45 queries per second for an IP block. Consumers should honor the published limit, cache stable responses and avoid turning every autocomplete keystroke or agent thought into a new request.

Why it matters for AI tools

A coding assistant can use structured package and symbol metadata to narrow retrieval before it generates an answer. Dependency inventory and security tools can connect versions with vulnerability notices and imported-by context. Those are useful primitives; they do not make the resulting recommendation correct. Package popularity is not a security review, a symbol match is not proof of compatibility and vulnerability data can be incomplete or updated after a response is cached.

Return the package path, version and pkg.go.dev source URL with any assistant answer so a developer can inspect the underlying record. Pin important decisions to a version rather than silently following latest. For security-sensitive workflows, reconcile the API with the Go vulnerability database and the organization’s own build graph.

Pricing, stability and support

The Go Team announcement does not describe a separate paid plan for the public service. That does not imply an unlimited service-level agreement. The published rate limit, versioned API contract and public issue tracker are practical operating constraints. Infrastructure, caching, observability and any model used around the API remain the adopter’s costs.

The June 12 announcement introduced v1beta and described a future move to v1. The current reference now documents /v1 routes, and the old reference URL redirects there. The pkgsite source and reference tooling can still change. Generate clients from a reviewed OpenAPI revision, keep contract tests, tolerate new fields, handle missing fields and error responses, and monitor the official issue tracker and announcement channels.

How Kingy would evaluate it

Build a frozen corpus spanning standard-library packages, modules with many versions, deprecated packages, similarly named paths, private-looking typosquats, packages with known vulnerabilities and entries with large imported-by graphs. Test endpoint completeness, pagination, version selection, response latency, caching behavior, error semantics and freshness against the rendered pkg.go.dev record.

For an AI assistant, measure citation correctness and whether the model preserves exact package paths and versions. Inject ambiguous names and stale cached data, then verify that the system asks for clarification or exposes uncertainty. Kingy reviewed the Go Team announcement, live API reference, OpenAPI specification, pkg.go.dev service pages, source repository and public issue tracker; we did not operate a sustained client or benchmark the service.

Primary sources

Alternatives

View alternatives page

Launch History

AI Coding Tools

pkg.go.dev API

The Go Team launched a public GET-only v1beta pkg.go.dev API for structured search and package ecosystem metadata, including packages, modules, symbols, versions, known vulnerabilities and imported-by relationships, with…

Recheck due Free: Yes API: Yes Open: Yes
Developer-friendlyGitHub tractionTraction signal

The pkg.go.dev API replaces brittle HTML scraping with an official structured interface and gives AI coding tools a cleaner evidence source. It remains v1beta,…