macOS Homebrew command
$ brew tap createitv/tap && brew install agc-cli && agc version AppGallery Connect, mapped for the terminal
Move every release through one red line.
A Go command center for discovering, dry-running, and invoking AppGallery Connect APIs—with stable JSON for people, CI, and coding agents.
13 API families156 registered interfaces3 output formats
agc / productionreference mode
AUTHPS256 / OAuth
PROFILEproject-bound
PACKAGEupload + status
RELEASEinvoke by choice
$ agc auth check --pretty
{
"data": {
"name": "production",
"mode": "service-account",
"active": true
},
"affordances": {
"next": "agc publishing endpoints"
}
}project profile resolved · dry-run on
Dry-run firstNothing is sent until you opt in.
Agent-readableJSON envelopes include next actions.
One surfaceCLI, local REST, and web share a registry.
Install agc CLI
Use the package manager for your system.
macOS installs through the Createitv Homebrew tap with brew tap createitv/tap && brew install agc-cli. Windows installs through Scoop from the Createitv bucket.
Windows Scoop command
PS> if (!(Get-Command scoop -ErrorAction SilentlyContinue)) { Set-ExecutionPolicy RemoteSigned -Scope CurrentUser -Force; irm get.scoop.sh | iex }; scoop bucket add createitv https://github.com/Createitv/scoop-bucket; scoop install agc-cli; agc version Homebrew formula: agc-cli Versioned GitHub Release binary Winget PR submitted for Microsoft review
The release rail
Context flows forward. Secrets do not.
Each stage owns one job. Credentials remain local, project context remains portable, and destructive API calls require an explicit switch.
AUTH
PS256 / OAuth
PROFILE
project-bound
PACKAGE
upload + status
RELEASE
invoke by choice
Automatic profile binding
Choose once per project. Override only when you mean it.
Bind production in .agc/project.json. Commands resolve the profile in a predictable order, while --profile staging remains available for one-off work.
- 1CLI override
--profile staging - 2Project default
.agc/project.json - 3Active account
~/.agc/credentials.json
.agc/project.json project safe
{
"appId": "123456789",
"projectId": "987654321",
"packageName": "com.example.app",
"profile": "production"
} No client keys or private keys are stored here.
Interface registry
Discover the API before writing the request.
Every entry carries its method, path, parameter locations, CLI command, REST route, and dry-run path.
Selected family / game-items
Game Item Mall
Inbound role query and order callbacks configured in AGC.
DISCOVER
agc game-items endpoints --output tableSTATUS
agc game-items status --prettyLOCAL REST
/api/v1/game-itemsAll endpoints 2
Expand an endpoint for registered parameters and commands. Consult its reference for full schemas, responses, and permissions.
POST查询玩家区服角色propapi-getroleinfo{callbackUrl}
此接口用于查询玩家区服角色信息。
Inbound callback to your service
| Parameter | Location | Required | Type | Description |
|---|---|---|---|---|
callbackUrl | path | Yes | — | callbackUrl parameter |
callbackUrl | path | Yes | — | callbackUrl parameter |
Request body: json
Inspect definition
agc game-items propapi-getroleinfo --pretty
Local REST definition
/api/v1/game-items/endpoints/propapi-getroleinfoRead endpoint reference ↗
POST下单propapi-order{callbackUrl}
下单
Inbound callback to your service
| Parameter | Location | Required | Type | Description |
|---|---|---|---|---|
callbackUrl | path | Yes | — | callbackUrl parameter |
callbackUrl | path | Yes | — | callbackUrl parameter |
Request body: json
Inspect definition
agc game-items propapi-order --pretty
Local REST definition
/api/v1/game-items/endpoints/propapi-orderRead endpoint reference ↗
What is agc-cli, and who is it for?
agc-cli is an open-source Go command-line tool for Huawei AppGallery Connect, maintained by Createitv. Its installed command is agc. It organizes API discovery, credential profiles, request previews, and API invocation into reusable commands for HarmonyOS and Huawei app developers who manage app metadata, testers, products, and reports.
Project and guides: GitHub · Usage guide · Issues
Frequently asked questions
Is agc-cli an official Huawei tool?
No. agc-cli is an independent open-source project maintained by Createitv under the MIT license. It organizes endpoints using Huawei AppGallery Connect API references and is not an official Huawei product or support service.
How do I install agc-cli on macOS, Windows, or Linux?
On macOS, run brew tap createitv/tap, then brew install agc-cli. On Windows, run scoop bucket add createitv https://github.com/Createitv/scoop-bucket, then scoop install agc-cli. On Linux, download a binary for your architecture from GitHub Releases. Run agc version to verify installation.
Is agc-cli free, and do I need an account?
agc-cli is free to use and modify under the MIT license. Calling Huawei APIs requires your own AppGallery Connect account, credentials, and permissions. Huawei service pricing and limits remain subject to Huawei terms. Browsing the endpoint reference or inspecting CLI definitions does not require login.
How do I query app information for the first time?
Save credentials with agc auth login --service-account-file ~/.agc/service-account.json --name production, then bind the project with agc init --app-id YOUR_APP_ID --default-profile production. Preview with agc publishing app-info-query --invoke --query appId=YOUR_APP_ID --query lang=en-US. Add --dry-run=false after checking the request. Supply a client_id header explicitly when required.
Are all 156 endpoints production-verified?
No. The registry contains 156 entries across 13 API families; this is registry coverage, not production verification of every endpoint. Registered parameters and command surfaces are shown here. Consult each endpoint reference for full request and response schemas, permissions, and business prerequisites.
Does the default dry run change my app?
No. Endpoint commands with --invoke preview the request without sending it by default. Real invocation requires --dry-run=false. Check the target app, credential profile, and parameters before executing.
Can I use agc-cli with scripts or AI agents?
Yes. JSON output supports script processing. agc capabilities and agc endpoints expose discovery; agc web-server provides local REST routes, and agc openapi exports the contract. Command templates support navigation but do not replace business-state checks or review decisions.
Does a project profile fill all endpoint parameters automatically?
A project configuration can select its default credential profile, with --profile for explicit overrides. App IDs, languages, headers, and request bodies still need to be supplied according to each endpoint. Keep Service Account private keys and credential files out of Git.
Browse the complete API reference by family
Content updated:
Quick start
Three commands to a bound, inspectable workspace.
Use placeholders for your AppGallery Connect values. The second command is what makes the profile automatic for this project.
01
Save a credential profile
Service Account is the preferred route. Secrets stay in ~/.agc/credentials.json with restricted permissions.
$ agc auth login --service-account-file ~/.agc/service-account.json --name production02
Bind it to the project
Save project metadata and choose a default credential profile. Supply endpoint parameters explicitly when invoking APIs.
$ agc init --app-id <app-id> --project-id <project-id> --package-name com.example.app --default-profile production03
Inspect before invoking
Endpoint commands are dry-run first. Review the exact method and URL, then opt into the real request.
$ agc publishing app-info-query --invoke --query appId=<app-id> --dry-run=falseLocal command center
The browser is a window into the same registry.
Start the local REST server when you want live capability data. Without it, this site stays useful as a complete reference surface.
agc web-server --addr :8421GET
/api/v1/capabilitiesfamilies + affordancesGET
/api/v1/endpointsall interface entriesGET
/api/v1/openapi.jsonmachine-readable contractPOST
/api/v1/:family/endpoints/:id/invokedry-run by default