API → AGENT METHOD11 / 12
Distribution for agent-ready services

Your API is documented for people.
Package the job for agents.

Turn raw endpoints into narrow, typed capabilities an agent can discover, inspect, and invoke—without giving up the API, commercial model, or operations you already own.

Method contractcrm.account_enrichLook up a company and return normalized firmographic context.
Inputdomain: string
OutputAccountProfile
manifest.jsonhandler.ts● signed
01  {
02    "id": "com.acme.crm",
03    "version": "1.2.0",
04    "methods": [{
05      "name": "account_enrich",
06      "description": "Enrich a company",
07      "input": {
08        "domain": "string"
09      },
10      "grants": ["network:api.acme.com"]
11    }],
12    "integrity": "sha256:9ac…"
13  }
Schema validSignature validReady to publish
Agent method draft

Turn one API job into
a typed agent method.

Share public documentation and the job agents should accomplish. We will sketch the method, inputs, result, grants, and best Pilot distribution model.

What you get
  1. 01Task-shaped method
  2. 02Input/output sketch
  3. 03App or service recommendation
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.

Packaging surface

Document the job.
Declare the boundary.

Human-oriented reference pages leave the agent to infer authentication, method intent, parameter shape, and safe operating limits. A Pilot app can broker an existing API behind typed methods and declared grants. A network service can publish its own address and structured command surface. Both approaches give the publisher a clearer agent-facing contract.

01Describe

Typed methods and schemas

Define what the capability does, which arguments it accepts, and how the result is returned.

input → output
02Distribute

Catalogue or network discovery

Ship a signed local app or operate a specialist service with a searchable Pilot identity.

grant[]
03Operate

Keep control of the upstream

The publisher retains the existing API, commercial model, and service operations behind the agent-facing adapter.

catalogue.publish()
Publish flow

From endpoint to discoverable capability.

  1. 01

    Choose local app or hosted service

    Use an app for brokered local access or a service agent for an addressable network capability.

  2. 02

    Define a narrow agent contract

    Expose task-oriented methods rather than mirroring every raw upstream endpoint.

  3. 03

    Declare authority and dependencies

    Make credentials, files, network domains, and process requirements inspectable.

  4. 04

    Publish and iterate

    Distribute through the catalogue or directory and improve the contract from real agent calls.

Technical basis

Specific product surfaces.
Inspectable in the docs.

Product reviewPilot release 1.13.9Inspect documentation
  • 01Typed manifest schema
  • 02Signed catalogue distribution
  • 03Searchable service identity
  • 04Structured help and data responses