Skip to content
NEWTry Pilot Cloud

Publish an app. Agents do the rest.

Bring your existing app. Describe it once and we generate, sign and verify an agent-first adapter for it. Then our team reviews it onto the Pilot App Store, one command for any agent to install.

  1. 1

    Describe your appyou

    weather.search · GET /search · fast

  2. 2

    Build, sign and verify the adapterwe

    generatedsha256 pinnedsignedverified
  3. 3

    Review itour team

    pending → approved · emailed to you

  4. 4

    Install it with one commandevery agent

    $ pilotctl appstore install io.pilot.weather

Example: the form’s own placeholder app, io.pilot.weather.

You describe it. We do the packaging.

What you bring

  • A valid email. We use it to reach you about your submission.
  • A description of your app’s methods. You don’t upload any code.
  • Your signature on a short release. You confirm you have the right to publish the app, let us use your name and the app’s name to list it, and agree to the Terms, Acceptable Use Policy and Publisher Release Agreement.

What we handle

  • The adapter. We generate it, sign it and verify it for you.
  • Your keys stay yours. Secrets are never collected here; operators supply them at install time.
  • A review. Every submission is reviewed by our team before it appears in the store.
  • Updates by email. A confirmation when you submit, and again when your app is approved or needs changes.

Start your submission.

Seven short steps. The live preview shows the help agents will read and the commands they’ll run.

Your draft stays in this browser until you submit. Questions first? Read the publishing docs.

7 steps · saved in this browser as you go

Describe your app once.

Email, identity, backend, methods, listing, vendor, review. You can stop at any point and come back.

Prefer the command line?

The form runs the same pipeline on Pilot’s server. To run it on your machine instead, use pilot-app from pilot-protocol/app-template, then open a pull request.

  1. 1Commit submissions/<id>/ in your fork and open a pull request.
  2. 2CI verifies the bundle and a maintainer reviews it.
  3. 3On merge, the bundle is released into the signed catalogue, and install works everywhere.

your machine · pilot-app

# 1. Install the scaffolder and describe your API
$ go install github.com/pilot-protocol/app-template/cmd/pilot-app@latest
$ pilot-app example > pilot.app.yaml
$ pilot-app validate
# 2. Generate the adapter, then build, pin, sign and package it
$ pilot-app init -o ./my-app
$ cd my-app
$ make gen-key
$ make package
$ pilot-app verify io.pilot.<id>-<ver>.tar.gz
# 3. Prepare the submission in your fork of app-template
$ pilot-app submit -C . --prepare /path/to/app-template-fork