Starters
Lane-aware examples for agent cards, approved media metadata, static skills, external endpoint metadata, downloadable packages, tool listings, workflows, and bundles.
Creator preparation
Public repository URL
The kit is useful before upload and after publication: creators can prepare package shape, run local checks, use CI validation, and display public status without turning those signals into platform approval.
Lane-aware examples for agent cards, approved media metadata, static skills, external endpoint metadata, downloadable packages, tool listings, workflows, and bundles.
Public JSON Schema contracts for manifests, public agent card summaries, approved media readback, package inventory, distribution lanes, evidence bundles, and readback. Agent-native schema contracts remain source-preview until package release is accepted.
Published as `@agentique.io/validator` for no-execution local checks covering manifest shape, hashes, unsafe paths, executable payloads, and secret-like content.
Contracted as `@agentique.io/uploader` for review-only uploader planning with scoped CLI token auth, upload session verification, server-side completion verification, and status readback. Agent-native uploader dry-run planning is source-preview; public package release remains gated.
Approved action usage reference for least-privilege workflow validation so creators can check resource packages before platform submission; Marketplace-style promotion remains separate.
Published as `@agentique.io/readback` for read-only public status helpers after agentique.io publishes a resource; badge/readback documentation is available while media fields, card hierarchy, compatibility labels, agent-native readback, and status claims stay governed by release guidance.
Users choose whether to prepare outside the site first or continue directly into Agentique's account-bound upload flow.
Start from a lane-aware starter and fill in public manifest, agent-card, approved media, endpoint, or package metadata before creating a website draft.
Run the validator against package files and fix local readiness findings before upload.
Use the website upload flow for account-bound draft creation, lane selection, platform scan, review, moderation, and publication.
Check release governance docs for package manifest review, URL inventory, support routing, and no-overclaim boundaries before sharing public tooling output.
Use readback helpers only after agentique.io exposes public status, media fields, card labels, compatibility context, and match explanations for a published resource.
The Creator Kit is optional. The website upload path remains available either way.
Open the repository first when you want schema examples, available validator/readback packages, source-preview agent-native contracts, local validation, uploader contract guidance, action release notes, or readback helper baselines before website upload.
Review the Creator Kit pathCreate a website-owned draft directly and let Agentique handle scan, review, moderation, and publication.
Continue with website uploadPreparation tools help creators produce cleaner inputs, while Agentique keeps authority over platform processing and public distribution state.
The upload flow owns account binding, scan handoff, review, moderation, publication, and readback. Use it directly when you do not need offline preparation first.