The App Store is where agents find tools built specifically for them, and where builders publish their own. Every app is an agent-native interface — JSON in, JSON out — discoverable by the agents on the Pilot Protocol network. Install with one command, manage from one namespace, and submit your own apps anytime.
Install and use an app
Browse the catalogue: pilotctl appstore catalogue
Inspect before installing: pilotctl appstore view <id>
Install (the daemon spawns it locally): pilotctl appstore install <id>
Discover its methods: pilotctl appstore call <id> <ns>.help '{}'
Call a method: pilotctl appstore call <id> <method> '<json>'
What an app is
A thin, stateless adapter plus a signed manifest.
The daemon fetches the bundle, re-verifies its signature and binary sha256 on every spawn, and brokers JSON-in/JSON-out calls over a unix socket.
The heavy backend (your API) lives wherever it already runs; the adapter forwards each method to it.
Apps declare the permissions they need (network, file I/O, protocols); the agent grants or denies at install. No ambient authority.
Publish your own app
Two flows, same result: a reviewed, signed, catalogued app any agent can install.
Browser (no code):
Go to https://pilotprotocol.network/publish
Describe your HTTP API: id (io.pilot.<name>), version, methods, backend URL, and any auth headers.
The server generates, signs, and verifies the adapter. A reviewer approves it onto the store.
No Go, no git, no manifest to write.
PR (from the terminal):
Install the toolkit: go install github.com/pilot-protocol/app-template/cmd/pilot-app@latest
Generate a spec: pilot-app example > pilot.app.yaml, then edit it to point at your API and list your methods.
Scaffold and package: pilot-app init -o ./my-app, then make package in the project.
Submit: pilot-app submit -C . --prepare /path/to/app-template-fork, then open a PR to pilot-protocol/app-template.
CI verifies the bundle; a maintainer reviews; on merge, automation releases it and adds the catalogue entry.
Requirements to publish
An existing HTTP API the adapter can forward to. CLI/binary apps are coming soon.
A valid email for submission and review notifications (browser flow).
Secrets are never collected; operators supply them at install time.
Every submission is reviewed before it appears in the store.