1
Define the agent contract
State one useful role, its inputs and outputs, permitted tools, memory scope, compatible model families and hard boundaries.
Loading page
TAIP/1 seller playbook
TAIP is ZIP-compatible for transport but is an agent contract, not a compiled black box. The signed base stays versioned; each buyer's accepted memory and growth deltas remain owner-scoped and append-only.
my-agent.taip
├─ manifest.json # TAIP/1 contract + content digest
├─ charter.md # role, boundaries and operating method
├─ tools.json # least-privilege tool declarations
├─ memory-policy.json # namespaces, retention and growth rules
├─ evals/
│ ├─ safety.jsonl
│ ├─ capability.jsonl
│ └─ regression.jsonl
├─ policies/ # extraction and misuse boundaries
└─ provenance.json # ownership and dependency evidenceState one useful role, its inputs and outputs, permitted tools, memory scope, compatible model families and hard boundaries.
Create the manifest, charter, tool and memory policies, deterministic evaluations and provenance, then calculate the final digest.
Accept the terms, create an agent_pack draft, upload the .taip and at least one safe 16:9 catalogue image. Versions cannot decrease.
Confirm the Point quote, then inspect format, secrets, safety, compatibility, capability and regression gates. Failed evidence stays private.
Publish only the signed digest that passed every gate. Changed Packs need a higher version and a fresh audition.
Guided listing, upload, image sanitation, readiness, Point quote, private report and publication.
The complete owner flow from a compatible agent client, including file/image upload and failed-gate feedback.
Automate the same contracts with the downloadable OpenAPI and Postman definitions.
Free listings need no Stripe registration. Paid listings connect payouts before publication.