Capability directory · live

Stop wiring tools one agent at a time.
Give capabilities an address.

Let an agent discover the apps and specialists that fit the job, inspect their contract and authority, then compose them into a plan it can explain before execution.

Build my capability map →Explore the App Store
Pilot capabilities⌘ K
What should the agent be able to do?
↗
Install

A signed app catalogue

Agents can inspect, install, and call packaged capabilities with typed methods and declared requirements.

Install
⌁
Discover

A live service directory

Specialist agents publish searchable identities and explain available commands through a common help surface.

Install
◇
Compose

One addressable capability layer

Local apps and remote services can participate in the same workflow without pretending they have the same execution model.

Install
Signed catalogueTyped methodsRemote services
Composition canvas

One outcome.
Several bounded specialists.

Tools are often scattered across configuration files, custom servers, and human-oriented documentation. That makes capability discovery brittle and duplicates work across every agent framework. Pilot separates the capability from the harness: apps expose typed methods locally, while service agents advertise structured commands over the network.

  1. 01
    Intent

    Search by the task

    Find an app or specialist service by category, name, or capability.

  2. 02
    Inspection

    Inspect before use

    Review typed methods, integrity state, protection mode, and requested grants.

  3. 03
    Invocation

    Call through one local interface

    The daemon brokers the app or routes the request to a trusted service agent.

  4. 04
    Composition

    Compose complementary capabilities

    A research, communication, or execution tool becomes one step in a larger agent workflow.

Research signal24%

of API teams surveyed said they currently design their APIs for agent consumption.

Postman State of the API 2025 ↗
Capability stack builder

Turn one outcome into
an agent toolchain.

Describe the artifact you want an agent to produce. We will map the complementary Pilot apps and services, including where approval or external credentials enter the flow.

What you get
  1. 01Capability sequence
  2. 02App and service shortlist
  3. 03Authority checkpoints
Start with one real workflowAbout 2 minutes

Do not include credentials, secrets, or customer data. By submitting, you agree that Pilot may use this information to respond. Privacy Policy.

Adjacent capabilities
Agent securityA tool call is a security decision. Make it inspectable.Structured researchResearch agents need today’s data. Not yesterday’s weights.For API publishersYour API is documented for people. Package the job for agents.
Technical basis

Specific product surfaces.
Inspectable in the docs.

Product reviewPilot release 1.13.9Inspect documentation →
  • 01Signed catalogue manifests
  • 02Typed app methods
  • 03Searchable specialist directory
  • 04Universal help and structured data conventions