Typed methods and schemas
Define what the capability does, which arguments it accepts, and how the result is returned.
input → outputTurn 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.
domain: stringAccountProfile01 {
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 }Share public documentation and the job agents should accomplish. We will sketch the method, inputs, result, grants, and best Pilot distribution model.
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.
Define what the capability does, which arguments it accepts, and how the result is returned.
input → outputShip a signed local app or operate a specialist service with a searchable Pilot identity.
grant[]The publisher retains the existing API, commercial model, and service operations behind the agent-facing adapter.
catalogue.publish()Use an app for brokered local access or a service agent for an addressable network capability.
Expose task-oriented methods rather than mirroring every raw upstream endpoint.
Make credentials, files, network domains, and process requirements inspectable.
Distribute through the catalogue or directory and improve the contract from real agent calls.