create-aimarket-agent

From an empty directory to a signed AIMarket Protocol v2 provider.
A safe, deterministic project generator with tests, Docker packaging, and explicit publishing.

🔄 Synced from the AI-Factory monorepo (append-only history). Pull requests are welcome — merged PRs are imported back and re-synced here. Issues · Pull requests

English · Русский · Español · Français · 中文 · Localization glossary

Quick start

uvx create-aimarket-agent my-agent --kind tool --metis
cd my-agent
uv sync --extra dev
uv run python configure_provider.py
uv run pytest
uv run python validate_manifest.py
uv run python agent.py

The command, identifiers, flags, and generated filenames are stable in every language.

Prefer TypeScript?

The npm generator is not published yet. Use the source command below (Node.js 22+) or download the tested TypeScript provider project.

git clone https://github.com/alexar76/create-aimarket-agent.git
node create-aimarket-agent/npm/bin/cli.mjs my-agent
cd my-agent
npm install && npm run configure && npm test && npm run dev

The TypeScript flavour generates a node:http provider with no runtime dependencies and the same capability.json. Both flavours sign byte-identical envelopes, so a consumer written in either language verifies either provider — a cross-language parity test in the npm package fails if a single byte diverges. See npm/README.md.

Build a useful agent, step by step

Follow the complete tutorial to turn the generated skeleton into THEMIS: a real procurement and security agent with deterministic policy checks, projected cost, OWASP Agentic risk mappings, lazy asynchronous Metis verification, and signed results.

Open the English tutorial · inspect the finished repository

Generated repository

Check your provider

The Playground's /connect route accepts your configured capability.json and test input. Set the issued token as AIMARKET_ONBOARDING_CHALLENGE and restart your provider to enable its same-origin proof route. The check performs one real invoke and verifies its schema and request-bound Ed25519 signature. It does not publish the provider or require stake. Local/CI setup and profile.

Path	Role
agent.py	FastAPI health and invoke endpoints
capability.json	AIMarket Protocol v2 capability manifest
provider_signing.py	Persistent Ed25519 identity and request-bound response signing
configure_provider.py	Writes the public provider key into the manifest atomically
validate_manifest.py	Fail-closed structural validation before publishing
test_agent.py	API, request-bound signature, and request-size tests
Dockerfile · .dockerignore	Non-root container packaging with persistent key volume
.github/workflows/test.yml	Generated-project CI

Security model

• Scaffolding is atomic: a failed copy or replacement leaves no partial target repository.
• Project names are allow-listed before they enter source or JSON files.
• The provider key is a 32-byte Ed25519 seed stored with mode 0600; symlinks and non-regular files are rejected.
• Responses sign a canonical request-bound envelope containing capability_id, product_id, the SHA-256 input digest, and the result. This prevents replay across requests.
• The generated service accepts only the product and capability identity declared in its manifest, so an untrusted caller cannot make the provider key sign another identity.
• The manifest validator rejects duplicate JSON keys, malformed Ed25519 keys, non-finite prices, malformed URLs, and public HTTP endpoints before the publish step.
• The default invoke endpoint rejects missing, malformed, or oversized request bodies.
• Publishing is never automatic. Stake, publisher identity, trust policy, and Hub registration remain explicit operator actions.

Project kinds

create-aimarket-agent my-tool --kind tool
create-aimarket-agent my-data --kind data-provider
create-aimarket-agent my-orchestrator --kind orchestrator
create-aimarket-agent my-agent --no-metis

Docker

The generated image runs as an unprivileged user, includes a health check, listens on 0.0.0.0:8080, and stores the provider key in /data/provider.key.

docker build -t my-agent .
docker run --read-only --tmpfs /tmp -p 127.0.0.1:8080:8080 -v my-agent-key:/data my-agent

Back up the provider key before publishing. Replacing it invalidates the provider_pubkey registered with the Hub. Keep the port loopback-only until an HTTPS ingress provides production traffic, concurrency, and rate limits; the response signature does not authorize direct callers.

Development of this generator

uv sync --extra dev
uv run pytest
uv build --wheel

Localization contract

Documentation is available in English, Russian, Spanish, French, and Chinese and follows the canonical AICOM localization glossary. Code, commands, flags, filenames, API fields, env vars, brands, LIVE, and SIM are never translated.

License

MIT — see LICENSE.