Pkg Go Dev
Use pkg.go.dev data APIs through OpenAny to retrieve the package specification or manifest for the selected release. For go.mod, provide Go package path (path); refine the result with release version (version). Other available operations include imported by, module, symbols. The manifest retains the package's source-declared configuration and requirements, enabling dependency declarations and release settings to be inspected as structured metadata rather than executing the package or installation process. Read the selected package manifest, inspect declared requirements and compare configuration before changing a dependency. Each API page provides supported parameters, request and response examples, and usage pricing.
- Endpoints
- 4In this collection
- Providers
- 1Unique providers
- Requests
- —Loading...
- Success rate
- —Loading...
- Response P50
- —Loading...
Available APIs
pkg.go.dev imported by API
Use the pkg.go.dev imported by API to retrieve packages or modules that depend on the selected resource. Provide Go package path (path); refine the result with release version (version), Go module path (module). Reverse-dependency results identify the packages or projects that use the selected resource, rather than its own requirements, and retain the source's version relationships or usage ordering when those are provided. Identify projects or packages that depend on a resource, compare usage relationships and estimate the reach of a proposed package change. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
pkg.go.dev go.mod API
Use the pkg.go.dev go.mod API to retrieve the package specification or manifest for the selected release. Provide Go package path (path); refine the result with release version (version). The manifest retains the package's source-declared configuration and requirements, enabling dependency declarations and release settings to be inspected as structured metadata rather than executing the package or installation process. Read the selected package manifest, inspect declared requirements and compare configuration before changing a dependency. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
pkg.go.dev symbols API
Use the pkg.go.dev symbols API to retrieve exported Go symbols and their available API documentation. Provide Go package path (path); refine the result with release version (version), Go module path (module). Symbol records identify exported constants, variables, functions, types and their associated members, retaining signatures and parent relationships so the package's public API can be examined without fetching an entire source tree. Inspect exported Go declarations, compare signatures and parent types and locate the API surface needed by an integration. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
pkg.go.dev module API
Use the pkg.go.dev module API to retrieve package metadata and the source's published package details. Provide Go package path (path); refine the result with release version (version), README inclusion option (readme). Package details identify the chosen release and its published licence or project references, providing the metadata needed to distinguish the library, application or module before inspecting its ecosystem-specific details. Identify a package release, inspect its licence and distribution metadata and select the version to examine for integration. The detail page provides the supported parameters, request examples, available response examples and usage pricing for this operation.
Common questions
How are Pkg Go Dev APIs priced?
Each endpoint publishes its own rate and billing unit. Compare the selected implementation and request-specific conditions; a collection starting price is not a quote for every request.
How do I authenticate Pkg Go Dev requests?
Use your OpenAny API key from a secure environment variable for supported account-based calls. Never paste secrets into prompts, documentation examples or public logs.
Are all implementations interchangeable?
No. Read each endpoint request schema, response examples and limitations before execution. Different suppliers may expose different fields and behavior; approve the budget before a paid call.
Use Pkg Go Dev with your agent
Inspect endpoint contracts and confirm availability and pricing before a paid call.